SLA
DBaaS Service-Level Agreement (SLA)
These product-specific SLAs define the Service Availability Target for Database as a Service (DBaaS). It applies to each Client using the Service. Capitalized terms used herein but not defined herein shall have the meanings set forth in the Exoscale Terms and Conditions or EUSA, whichever applies.
Exoscale DBaaS is powered by managed-database technology from Aiven Ltd. For transparency, this SLA reflects that foundation, but it is Exoscale’s own commitment to the Client and applies to all paid DBaaS service plans.
SLA
| Plan | Metric | Target | Definition |
|---|---|---|---|
| Startup | Availability | >= 99.95% | The Monthly Uptime Percentage during which Exoscale DBaaS is available and operational for use. Startup plans run on a single node, so availability is guaranteed at 99.95%. |
| Business | Availability | >= 99.99% | The Monthly Uptime Percentage during which Exoscale DBaaS is available and operational for use. Business plans run on a multi-node, highly available setup, raising the guarantee to 99.99%. |
| Premium | Availability | >= 99.99% | Same as Business: a multi-node, highly available deployment with a 99.99% Monthly Uptime Percentage guarantee. |
| Hobbyist | Availability | Best effort, no formal SLA | No monetary credits or uptime guarantee apply. |
Non-binding objectives
| Plan | Metric | Target | Definition |
|---|---|---|---|
| All | Backup success rate | >= 99% | A backup is successful when it is fully stored, listed, and restorable within the advertised retention window for the service plan. |
Backup retention profile (per plan)
For more information on how backups work and how to restore data, see the Backups and Restore guide.
| Service type | Hobbyist | Startup | Business | Premium |
|---|---|---|---|---|
| Apache Kafka | No backups | No backups | No backups | No backups |
| PostgreSQL | 1 day with PITR | 2 days with PITR | 14 days with PITR | 30 days with PITR |
| MySQL | 1 day with PITR | 2 days with PITR | 14 days with PITR | 30 days with PITR |
| OpenSearch | Hourly backup for 1 hour and Daily backup for 1 day | Hourly backup for 24 hours and Daily backup for 3 days | Hourly backup for 24 hours and Daily backup for 14 days | Hourly backup for 24 hours and Daily backup for 30 days |
| Grafana | Backup every 1 hour up to 1 day | Backup every 1 hour up to 1 day | Plan not available | Plan not available |
| Valkey | Backup every 12 hours up to 1 day | Backup every 12 hours up to 1 day | Backup every 12 hours up to 3 days | Backup every 12 hours up to 3 days |
| Thanos | Plan not available | Data persisted in object storage (no snapshot backups) | Data persisted in object storage (no snapshot backups) | Plan not available |
Nature of the Non-binding Objectives Commitment
- This provision does not constitute a legally binding obligation but rather specifies a target value that Exoscale will endeavor to achieve.
- In this case, no monetary credits or other compensation will be granted if the objective is missed.
- This is provided for transparency and capacity-planning purposes only.
Other product specifications
For detailed product features, technical specifications, and tutorials, please refer to the DBaaS documentation.
Exclusions
The following events are excluded from the Service Availability Target and shall not be considered a Service Outage, including but not limited to:
- Caused by factors outside of Exoscale’s reasonable control, including any force majeure event and hostile actions by third parties such as denial-of-service attacks.
- Downtime caused by the use of Beta Services and/or Beta Features also called Preview.
- Periodic Maintenance Updates, which shall not occur more often than once (1) per calendar month.
- Critical Bug fixes and Security Updates.
- Customer-generated service system load (network requests, client queries, storage usage) that exceed the resource-based capabilities (network traffic, cpu usage, memory usage, disk usage) of the given service plan level.
- Customer modification or termination of critical resources (including operating credentials, the VPC, virtual machines, object storage, networking) utilized by Provider to provide the Cloud Services.
Client Responsibilities
While Exoscale is responsible for operating and maintaining the DBaaS infrastructure, Client remains responsible for the following but not limited to:
- Database schema design and query optimization
- Backup strategy, restore validation, and disaster recovery planning
- Monitoring of resource usage, performance, and costs
- Application-level and network-level access control and credential management
- Data classification and regulatory compliance for stored data
- Client defined encryption and recovery keys
- Set maintenance window time
For a complete explanation of the shared responsibility framework between Exoscale and Clients, please see the Exoscale Shared Responsibility Model documentation.
Retribution
The standard retribution and SLA credit schemes apply for this product as described under General Exoscale Terms and Conditions or EUSA, whichever applies. The Service Credits shall be the sole remedy for not meeting the SLA. In the event that the Monthly Uptime Percentage for Exoscale DBaaS falls below the committed Service Level Objective, the Client will be eligible for service credits as follows:
| Plan | Monthly Uptime Percentage | Service Credit Percentage of Monthly Service Fees for Affected Resources |
|---|---|---|
| Startup | from 99.95% to 98.3% | 50% |
| Business and Premium | from 99.99% to 98.3% | 50% |
| Any paid plan | below 98.3% | 100% |
Service credits apply only to plans with a committed availability target (Startup, Business, and Premium); Hobbyist plans are best-effort.
Claim Service Credit
To request a service credit, refer to the Service Unavailability Credit section of the Exoscale Terms and Conditions or the EUSA, whichever applies.