Basic, Standard and Premium customers can contact us at firstname.lastname@example.org. In addition, all support customers can reach us through our public forum and community Slack channel. VoltDB business hours are 8am-6pm, Monday through Friday Eastern Time Zone. Premium customers also will receive a phone number they can call 24×7 for Severity 1 incidents.
When contacting VoltDB Support, include the following information, if applicable:
At VoltDB, we want to make sure you’re successful building, testing, and deploying your application. We have a variety of plans to support you, when you need it. We offer support for both our Open Source (Community) and Enterprise editions.
Our support engineers are ready, responsive, and skilled in all aspects of VoltDB database design and operation to help give you the extra boost you need.
|Support Services Coverage||Basic & Standard||Premium|
Email Support (business hours)
24x7 (Severity 1 only) Phone Support*
*Includes Non-Severity 1 Enterprise Lab Program Support
|Initial Response||1 business day||4 business hours||1 business hour|
|Technical Response||1 business day||1 business day||1 business hour|
|Coverage||Business Hours||Business Hours||24x7 phone support|
Business hours email support*
|Communication Method||Email, Phone|
|Customer Contacts||1 Named User||Unlimited Users||Unlimited Users|
|Sev. 1 Problem Escalation*|
/After Incident Review
|Software Maintenance / Updates||Basic||Standard||Premium|
Sev. 1 Incident Hot Fix
|Sev 1: Critical Business Impact||Productions VoltDB is inoperable or critical condition which prevent users from performing critical business functions. A workaround is not available.||- System down, hang, or crash situation|
- Data loss or data corruption
- Critical Functionality not available
- Security Vulnerability*
|Sev 2: Significant Business Impact||Important product features are unavailable with no acceptable workaround. Customer’s implementation or production use of VoltDB’s products in a primary business service, major applications or mission critical systems are functioning with limited capabilities or are unstable with periodic interruptions. The software may be operating but is severely restricted. A workaround is not available.||- Error or failure forcing a restart or recovery|
- Severely degraded performance
|Sev 3: Moderate Business Impact||Product features unavailable but a workaround exists and the majority of software functions are still usable. Minor function/feature failure that the customer can easily circumvent or avoid. Customer’s work has minor loss of operational functionality.||- Error but there is a workaround|
- Minimal degraded performance
- Incorrect behavior with minor impact
- Initial Installation or development milestones are at risk
|Sev 4: Minimal Business Impact||Minor problem or question that does not affect the software function such as How To’s, documentation, general questions, or enhancement requests. There is no impact to product usage or customer’s operations.||- General questions for advice|
- General question on functionality
- Clarification on documentations or release notes
- Enhancement request
* Security Vulnerabilities will be handled like an escalation, with oversight by the VP of Engineering to work out an issue resolution.
Starting with VoltDB V8, one point release for each major version will be selected as the Long-Term Support (LTS) release. LTS releases are supported for three years from the initial release, during which time the LTS version receives critical bug and performance patches as necessary. Older versions and non-LTS point releases are maintained and available as is for two years after their initial release.
Extended support periods for individual releases is available under separate contract on a case-by-case basis.
For version 8, V8.4 is the LTS release. See the table below for End-of-Life dates of all releases.
|Feb 2018||Feb 2021|
|v9||Mar 2019||Mar 2020|
|v8||Feb 2018||Feb 2020|
|v7||Jan 2017||Jan 2019|
|v6||Jan 2016||Jan 2018|
|v5||Jan 2015||Jan 2017|
|v4||Jan 2014||Jan 2016|
|v3||Jan 2013||Jan 2015|
|v2||Nov 2011||Nov 2013|
|v1||May 2010||May 2012|
If you have any questions or comments about VoltDB, we encourage you to reach out to the VoltDB team and community.