Service Level Agreement (SaaS)
SaaS service level agreement — uptime commitment, support response tiers, service credits, exclusions, and measurement methodology.
Live preview
SERVICE LEVEL AGREEMENT
This Service Level Agreement ("SLA") is effective May 23, 2026 and is incorporated into and governed by the Master Subscription Agreement (the "Agreement") between Northwind Cloud, Inc. ("Provider") and Customer (as named in the Master Subscription Agreement) ("Customer") for the Northwind Platform (the "Service").
1. DEFINITIONS
"Monthly Uptime Percentage" means the total minutes in a calendar month, minus minutes of Unavailability and Excluded Downtime, divided by the total minutes in that month, expressed as a percentage. "Unavailability" and "Excluded Downtime" are defined in Sections 4 and 5.
2. AVAILABILITY COMMITMENT
Provider will use commercially reasonable efforts to make the Service available with a Monthly Uptime Percentage of at least 99.9% during each calendar month.
At 99.9% availability, the maximum allowed Unavailability is approximately 43.2 minutes per 30-day month.
3. SUPPORT & RESPONSE TIMES
Provider will acknowledge support requests within the following target response times, by severity:
- P1 — Critical (Service down or unusable for all users): 15 minutes
- P2 — Major (major feature impaired; no reasonable workaround): 1 hour
- P3 — Minor (minor issue; workaround available): 1 business day
- P4 — Request (question, cosmetic issue, or feature request): 3 business days
Support hours: 24x7 for P1; 9:00 a.m.–6:00 p.m. PT, business days, for P2–P4.
4. MEASUREMENT METHODOLOGY
Uptime is monitored from at least three geographically distributed external locations at 60-second intervals. The Service is "Unavailable" for a given minute if all monitoring locations record a failed request to the production endpoints during that minute. An incident begins at the first such minute and ends at the first subsequent successful minute. Excluded Downtime (Section 5) is not counted as Unavailability.
5. EXCLUDED DOWNTIME
The following are NOT counted as Unavailability:
(a) Scheduled maintenance within the notified window;
(b) Emergency maintenance for security or stability, with notice as soon as practicable;
(c) Force majeure events outside the Provider's reasonable control;
(d) Failures of the Customer's equipment, software, network, or third-party services;
(e) Customer's misuse of the Service or breach of the Acceptable Use Policy;
(f) Suspension for non-payment or material breach;
(g) Beta, trial, or free features expressly designated "no SLA."
Scheduled maintenance window: Sundays 02:00–06:00 UTC, with at least 48 hours' advance notice.
6. SERVICE CREDITS
If the Monthly Uptime Percentage falls below the commitment in Section 2, Customer may request a service credit, calculated as a percentage of the monthly fees for the affected Service:
Monthly Uptime Percentage Service Credit
---------------------------------- --------------
Below 99.9% but at least 99.0% 10%
Below 99.0% but at least 95.0% 25%
Below 95.0% 50%
7. CREDIT REQUEST PROCEDURE
To receive a credit, Customer must submit a request in writing within thirty (30) days after the end of the month in which the miss occurred, including the dates/times of Unavailability and supporting logs. Credits are applied to a future invoice, are non-refundable, carry no cash value, and will not exceed the fees for the affected month.
8. SOLE REMEDY
The service credits in Section 6 are Customer's sole and exclusive remedy for any failure by Provider to meet the availability commitment, subject to the limitation-of-liability provisions of the Agreement.
9. TERM & CHANGES
This SLA remains in effect for the term of the Agreement. Provider may update this SLA on no less than thirty (30) days' notice; no update will materially reduce the committed service levels during a paid subscription term then in effect.
10. GOVERNING LAW
This SLA is governed by the laws of the State of Delaware, consistent with the Agreement.
PROVIDER: CUSTOMER:
_____________________________ _____________________________
Northwind Cloud, Inc. Customer (as named in the Master Subscription Agreement)
Date: ____________________ Date: ____________________
About this template
A Service Level Agreement (SLA) is the part of a SaaS contract that puts numbers behind the vendor's promises — and the part customers most often read too late. Four elements do the real work. (1) **The uptime commitment**, expressed as a Monthly Uptime Percentage. The headline number is less important than what it permits: 99.9% allows roughly 43 minutes of downtime per 30-day month, 99.95% about 22 minutes, and 99.99% only about 4 minutes — so each extra "nine" is an order-of-magnitude tighter. (2) **The measurement methodology** — uptime is meaningless unless the contract says exactly how it is measured (from where, how often, what counts as "down"), because a vendor measuring from a single internal probe can report numbers a customer can never reproduce. (3) **Exclusions** — scheduled maintenance, force majeure, and customer-caused outages are normally carved out; watch for overly broad exclusions that swallow the commitment. (4) **Service credits** — almost always drafted as the customer's *sole and exclusive remedy*, capped at the monthly fee, applied as credit (not cash), and forfeited unless claimed within a short window (often 30 days). That means an SLA is rarely a true guarantee of uptime; it is a pre-agreed, capped discount when uptime slips. Negotiate the credit tiers, the claim window, and a termination right for chronic or severe breaches if availability is business-critical.
When to use it
- Offering a paid SaaS or hosted service and committing to availability targets.
- Responding to an enterprise customer's procurement / vendor-risk requirements.
- Defining support severity tiers and response times for a B2B service.
- Attaching availability terms to a Master Subscription Agreement or order form.
What to include
- A Monthly Uptime Percentage commitment with a clear definition.
- Measurement methodology (where, how often, what counts as down).
- Support severity tiers (P1–P4) with target response times and support hours.
- Excluded downtime (scheduled/emergency maintenance, force majeure, customer-caused).
- A service-credit schedule tied to the size of the miss.
- Credit-request procedure, claim window, and a sole-remedy clause.