Legal & ComplianceEnterprise SLA

Enterprise SaaS Service Level Agreement (SLA) & Credit Schedule

Define 99.9% uptime commitments, planned maintenance windows, response time SLAs, and pro-rata credit calculation.

saas-service-level-agreement-sla.md•44 lines•343 words
# SERVICE LEVEL AGREEMENT (SLA) & UPTIME COMMITMENT

This Service Level Agreement ("SLA") is an addendum to the Master Services Agreement between **[Company Name LLC]** ("Provider") and **[Customer Organization]** ("Customer").

---

### 1. MONTHLY UPTIME PERCENTAGE COMMITMENT
Provider commits to maintaining a Monthly Uptime Percentage of at least **99.9%** across all production API and web endpoints during each billing month.

$$\text{Monthly Uptime } \% = \frac{\text{Total Minutes in Month} - \text{Downtime Minutes}}{\text{Total Minutes in Month}} \times 100$$

---

### 2. EXCLUSIONS FROM DOWNTIME
Downtime calculations strictly exclude:
1. Scheduled maintenance announced at least forty-eight (48) hours in advance, not to exceed four (4) hours per calendar month (scheduled between 02:00 - 06:00 UTC);
2. Outages caused by factors outside Provider's reasonable control, including upstream internet backbone failures or Force Majeure events;
3. Customer misuse or unauthorized script flooding that exceeds published API rate limits.

---

### 3. SERVICE CREDIT REMEDY SCHEDULE

| Monthly Uptime Percentage | Service Credit Applied to Next Invoice |
| :--- | :---: |
| **99.9% - 100%** | 0% (Standard Operational Target) |
| **99.0% - 99.89%** | **10% Credit** of Monthly Recurring Fee |
| **95.0% - 98.99%** | **25% Credit** of Monthly Recurring Fee |
| **Below 95.0%** | **50% Credit** of Monthly Recurring Fee |

---

### 4. INCIDENT SEVERITY & RESPONSE TIME MATRIX

| Severity Level | Definition | First Response SLA | Ongoing Updates |
| :---: | :--- | :---: | :---: |
| **SEV-1 (Critical)** | Core API down; all customer operations blocked | **< 15 Minutes** | Every 30 minutes |
| **SEV-2 (High)** | Major feature unavailable; viable workaround exists | **< 1 Hour** | Every 2 hours |
| **SEV-3 (Normal)** | Minor defect; core operations unaffected | **< 4 Business Hours** | Daily update |

---

### 5. CREDIT CLAIM PROCEDURE
Customer must notify [email protected] within thirty (30) calendar days following the end of the month in which the downtime occurred to claim applicable service credits. Service credits represent Customer's sole and exclusive financial remedy for downtime.
💡 Ready to customize? Copy and paste directly into your preferred text editor or IDE.Open in DocSwift Tool

How to Use & Customize This Template

1

Set Target Uptime Tier

Standard enterprise SaaS targets 99.9% (Three Nines), allowing up to 43.8 minutes of downtime per month.

2

Define Severity Levels

Ensure your engineering on-call rotation can realistically meet the 15-minute response SLA for SEV-1 tickets.

3

Append to Master Contract

Attach this SLA as Schedule B to your enterprise customer agreement.

Pro Formatting & Best Practice Tips

  • Always define service credits as the "sole and exclusive remedy" to prevent customers from suing for indirect business losses.
  • Scheduled maintenance should only take place during off-peak weekend UTC hours.

Frequently Asked Questions

How much downtime is allowed under 99.9% uptime?

99.9% uptime permits up to 43.8 minutes of unscheduled downtime per calendar month (or 8.76 hours per year).