Last Updated: March 12, 2024
If Customer licensed Redis Enterprise Software prior to March 12, 2024, please see legacy Support Services terms.
Redis provides Support Services for paid versions of the Redis Enterprise Cloud Services. This Redis Enterprise Cloud Support Policy describes the applicable support levels and processes that apply to the Cloud Services Customer has purchased, and is incorporated into the terms of the Cloud Terms of Service available at: https://redis.io/legal/cloud-tos or any other agreement between Customer and Redis governing the use of the Cloud Services and any related Services (the “Agreement”). Any capitalized terms used but not defined in this Support Policy are defined in the Agreement.
Business Hours or BH means the Redis hours of operation (9:00 a.m. – 5:00 p.m.) in the region of Customer’s domicile.
Developer Assistance means prioritized feature requests and bug fixes for Redis Developer Tools projects. This also includes help in configuring and integrating Developer Tools in testing, staging, and UAT environments.
Pricing Plan means the Redis Enterprise Cloud Services pricing plans that are available at: https://redis.io/redis-enterprise-cloud/pricing/.
Priority Level means the priority assigned to a support request, as shown below in this Support Policy.
Redis Clients means the specific open-source Redis client libraries supported by Redis. These include the Redis clients listed in the Documentation at: https://redis.io/docs/latest. Redis may update this list from time to time.
Redis Developer Tools means specific open-source tools as follows: (a) Redis Data Connectors, including RIOT (Redis Input/Output Tools), and Redis Kafka Connect as described here; and (b) Redis Developer Suite, including Redis Smart Cache and Redis OM Spring as described here. Redis may update these lists from time to time.
Redis Observability means specific open-source tools, including Grafana Redis dashboards and configurations, Redis Datasource for Grafana, Datadog integration, and Dynatrace integration, available with the applicable Support Package as described here. Redis may update this list from time to time.
Support Package means the applicable tier of Support Services purchased by Customer.
Support Services means the services described in this Support Policy, and does not include one-time services or other services not specified in this Support Policy (such as training or Consulting Services).
Technical Contacts means the applicable identified individuals within Customer’s organization who are responsible and certified for the administration of the Support Services.
Technical Account Manager means a Redis personnel member assigned to Customer’s account who provides onboarding support, operational assistance, quarterly reviews of Software architecture, and communication on patches and bug fixes to Customer.
2.1 Availability. All Customers with paid versions of the Cloud Services with available Transaction credits receive Support Services. Support Services do not apply to Free Services or Previews.
2.2 Support Package. The availability of a Support Package is determined by Customer’s total annual Cloud Services fees as specified in the applicable Transaction. Customer has the same Support Package for all Cloud Services (i.e., Customer cannot purchase different Support Packages for different Databases). The Support Services provided by Redis to Customer for the Cloud Services and certain of its components depend on the applicable Support Package shown in Table 1 – Support Services Packages as follows:
| Service | Basic | Developer | Business | Enterprise | Premium Enterprise |
|---|---|---|---|---|---|
| Software Releases | Included | Included | Included | Included | Included |
| Support Portal | Included | Included | Included | Included | Included |
| Phone Support | 24×7 | 24×7 | 24×7 | ||
| Root-Cause Analysis | Included | Included | |||
| Technical Support | Business Hours | Business Hours | 24×7 | 24×7 | 24×7 |
| Response Times | P1: 8 BH P2: 8 BH P3: 8 BH P4: 16 BH | P1: 1 hour P2: 4 hours P3: 8 BH P4: 16 BH | P1: 30 minutes P2: 2 hours P3: 8 BH P4: 16 BH | P1: 15 minutes P2: 45 minutes P3: 8 BH P4: 16 BH | |
| Technical Account Manager | Included (1 location) | Included (2 locations) | |||
| Ticket Escalation | Included | Included | Included | ||
| Redis Insight | Included | Included | Included | Included | |
| Redis Clients | Included | Included | Included | Included | |
| Redis Observability | Included | Included | |||
| Redis Developer Tools | Included | Included |
2.3 Developer Tool Support. For Enterprise and Premium Enterprise Support Packages, Redis will provide Developer Assistance for Redis Developer Tools and Redis Observability during Business Hours without Response Times.
2.4 Technical Account Manager. For Enterprise and Premium Enterprise Support Packages, Redis will designate the applicable number of Technical Account Managers and identify them to Customer. Technical Account Managers are different from Redis personnel who provide the Support Services.
3.1 Support Tickets. Technical Contacts may create a support ticket (a “Ticket”) 24 hours a day, 7 days a week through: (a) Redis’ web ticketing system at https://support.redislabs.com (the “Portal”); and/or (b) if Customer’s Support Package is at the Business level and above, through a call to the phone number provided by Redis. Support is provided in the English language only.
3.2 Ticket Resolution. Redis will make commercially reasonable efforts to resolve any Ticket detailing a material and verifiable failure of the Cloud Services to conform to its Documentation. Such efforts may include helping with diagnosis, suggesting workarounds, providing patches, or modifying the Cloud Services. Support Services will not be provided for: (a) use of the Cloud Services in a manner inconsistent with the applicable Documentation; (b) modifications to the Cloud Services not provided by Redis, or (c) use of the Cloud Services with products or software not provided or approved in writing by Redis.
3.3 Ticket Priority Level and Response Times. Redis will: (a) reasonably assess and assign each Ticket a priority level (“Priority Level”), as defined in Table 2 – Priority Level Definitions below; (b) respond to each Ticket according to Customer’s applicable Support Package; and (c) confirm the Priority Level with Customer’s Technical Contact and, if needed, resolve any disagreement regarding the Priority Level as soon as reasonably practicable. Response Times apply for production Databases of the Cloud Services.
| Priority | Definition |
| P1 – Critical | A catastrophic problem in Customer’s production Database that results in the inability to access Customer data or in loss of Customer data. Not applicable for non-production Databases. |
| P2 – High | A significant problem in Customer’s production Database that could disrupt essential operations, without impact on data availability and with no data loss. Not applicable for non-production Databases. |
| P3 – Moderate | A moderate problem in Customer’s production or non-production Database that involves partial or limited loss of non-critical functionality, another problem not involving loss in functionality, or not preventing continued essential operations. P3 – Minimal also includes any problem relating to non-production test and development Databases. |
| P4 – Low | A general usage question or minor problem. It also includes enhancement or modification requests. There is no impact on the quality, performance, or functionality of Customer production or non-production Databases. |
3.4 Ticket Escalation Process. This Section applies to Customers with Support Packages of Business and above. If the business impact of the problem has changed or was not correctly stated in the Ticket by the Technical Contact initially, Customer will request to have the Priority Level of the Ticket raised. If Customer encounters a P1 – Critical technical problem with its production Database (e.g., Database Instances are down or inaccessible) and Customer is not satisfied with the response or resolution provided by Redis for such problem, Customer may escalate the Ticket as follows (an “Escalation Request”):
| Escalation Path | Description |
| Step 1 | Verify that the Ticket is up-to-date and all requested information and files have been provided, and ask for escalation through one of the channels listed in Section 3.1 above, indicating the: (a) Ticket number; (b) Technical Contact’s details; and (c) reason for escalation. |
| Step 2 | A Support Services engineer or an operator will take Customer’s information and generate an Escalation Request. |
| Step 3 | Once an Escalation Request has been received, Redis’ Support Services team will respond to the Technical Contact to acknowledge the Escalation Request, determine the mode of communication, and frequency of updates. Redis will work to ensure that the appropriate resources are available to identify a solution or a workaround. |
3.5 Root Cause Analysis. For P1 – Critical and P2 – Moderate Tickets, Redis will: (a) perform a root-cause analysis to identify the cause of such failure in a reasonable time frame after closure of the Ticket; and (b) provide Customer with a report detailing the cause of, and procedure for correcting such failure, including timelines for resolution, if available. This Section applies only to Customers with Enterprise and above Support Packages.
For Redis to provide Support Services to Customer and meet the response times of the applicable Support Package, Customer shall provide the following in a timely manner: (a) access to Customer’s Technical Contacts; and (b) any additional information requested by Redis related to the Cloud Services. Customer’s Technical Contacts are the only individuals authorized to initiate and manage the Support Services.
Redis may amend this Support Policy in its sole discretion by posting updated Support Policy terms to the applicable website or Marketplace, if any. Redis will also update the version date at the top of the Support Policy terms. By continuing to access or use Redis’ Support Services after Redis has posted the updated Support Policy, Customer agrees to be bound by the updated Support Policy. Any renewed Commercial Subscription will be governed by the then-current Support Policy.
