mirror of
https://github.com/supabase/supabase.git
synced 2026-07-05 05:14:21 +08:00
89 lines
5.3 KiB
Markdown
89 lines
5.3 KiB
Markdown
---
|
||
id: sla
|
||
title: Service Level Agreement
|
||
---
|
||
|
||
The following Service Level Agreement, which is incorporated into and forms part of the Subscription Agreement between Supabase, Inc. ("Supabase") and Customer (the "Agreement"), will apply to the Services for Enterprise Customers specified in an Order Form during the applicable Subscription Term:
|
||
|
||
## Platform
|
||
|
||
### 1. Uptime Commitment
|
||
|
||
Supabase will provide Actual Availability for at least ninety-nine and nine tenths percent (99.9%) of the total time in each calendar month during the Subscription Term, as measured by Supabase (the **"Uptime Commitment"**).
|
||
|
||
### 2. Service Credits
|
||
|
||
If the Uptime Commitment is not met during any particular calendar month during the Subscription Term, then Customer will be eligible for a service credit ("Service Credit"), provided that Customer reports to Supabase such failure to meet the Uptime Commitment and requests such Service Credit in accordance with this Exhibit. The amount of any Service Credit due hereunder shall be calculated as follows:
|
||
X \* Y, where X = the total fees due from Customer to Supabase for the affected Services for the relevant calendar month (regardless of when billed or payable), and Y = the Credit Percentage corresponding with the Actual Availability provided (as a percentage of total time) for the relevant calendar month, as set forth in the table below.
|
||
|
||
| Actual Availability | Credit Percentage |
|
||
| -------------------------------------------------- | ----------------- |
|
||
| Less than 99.9% but greater than or equal to 99.0% | 10% |
|
||
| Less than 99.0% but greater than or equal to 98.0% | 15% |
|
||
| Less than 98.0% but greater than or equal to 96.0% | 20% |
|
||
| Less than 96.0% | 30% |
|
||
|
||
### 3. Credit Requests and Payment
|
||
|
||
To request a Service Credit, Customer must send an email to Supabase at support@supabase.io within thirty (30) days of the end of the month in which the Uptime Commitment was not met. Customer must include either its account ID or registered email address, and the previously reported dates and times that there was no Service Availability. If Supabase confirms that Customer is eligible for a Service Credit, Supabase will issue a credit to Customer’s account within thirty (30) days. Service Credits are not refunds, cannot be exchanged into a cash amount, and may only be used against future billing charges. Except as set forth in Section 4 below, the Service Credits shall be Customer’s sole and exclusive remedy, and Supabase’s sole and exclusive liability, for any failure by Supabase to meet the Uptime Commitment.
|
||
|
||
### 4. Definitions
|
||
|
||
All capitalized words used but not defined in this Service Level Agreement have the meaning set forth in the Agreement.
|
||
|
||
#### 4.1 Scheduled Availability
|
||
|
||
"Scheduled Availability" means the time, in minutes, that the applicable Services are generally accessible and available to Customer’s Permitted Users.
|
||
|
||
#### 4.2 Unscheduled Downtime
|
||
|
||
"Unscheduled Downtime" means the time, in minutes, that the applicable Services are not generally accessible and available to Customer’s Permitted Users, excluding inaccessibility or unavailability due to Customer’s or Permitted Users’ acts or omissions, force majeure events, scheduled maintenance disclosed with at least 24 hours’ notice by email, hacking or virus attacks, or reasonable emergency maintenance.
|
||
|
||
#### 4.3 Actual Availability
|
||
|
||
"Actual Availability" means Scheduled Availability less Unscheduled Downtime.
|
||
|
||
## Support
|
||
|
||
Supabase Support Service Level Agreements.
|
||
|
||
### 1. Urgent
|
||
|
||
**Critical Issue**
|
||
|
||
Defect resulting in full or partial system outage or a condition that makes Supabase unusable
|
||
or unavailable in production for all of Customer’s Users.
|
||
|
||
### 2. High
|
||
|
||
**Significant Business Disruption**
|
||
|
||
Issue resulting in a situation meaning major functionality is impacted and
|
||
significant performance degradation is experienced. Issue impacts significant proportion of user base and / or major
|
||
Supabase functionality.
|
||
|
||
### 3. Normal
|
||
|
||
**Minor Feature or Functional Issue / General Question**
|
||
|
||
Issue results in a component of Supabase not
|
||
performing as expected or documented. An inquiry by a Customer representative regarding a general technical issue
|
||
or general question.
|
||
|
||
### 4. Low
|
||
|
||
**Minor Issue / Feature Request**
|
||
|
||
An Information request about Supabase or feature request.
|
||
|
||
## Target response times
|
||
|
||
| Severity Level | Standard | Priority | Priority Plus |
|
||
| -------------- | ------------------------------------- | ------------------------------------- | -------------------------------------- |
|
||
| 1. Urgent | 1 business hour<br />24/7 × 365 | 1 business hour<br />24/7 × 365 | 1 business hour<br />24/7 × 365 |
|
||
| 2. High | 4 business hours<br />Monday - Friday | 2 business hours<br />Monday - Friday | 2 business hours<br />24/7 × 365 |
|
||
| 3. Normal | 1 business day<br />Monday - Friday | 1 business day<br />Monday - Friday | 12 business hours<br />Monday - Friday |
|
||
| 4. Low | 2 business days<br />Monday - Friday | 2 business days<br />Monday - Friday | 1 business day<br />Monday - Friday |
|
||
|
||
Business hours are from 6am to 6pm (local time), except where otherwise stated.
|