SLA Overview
A public summary of how openCenter frames service availability, incident severity, and support response expectations.
This page is a commercial and operational summary, not the full SLA. Exact commitments depend on the subscribed tier, deployment topology, and signed agreement.
The most useful public role for an SLA page is to describe the model clearly: who gets commitments, how incidents are triaged, and where buyers should expect contract-specific details.
Purpose
Helps buyers understand the SLA structure before they review the full contract version tied to a specific order form.
- Primary audience
- Buyers, platform operators, SREs, procurement
- Public scope
- Service availability structure, severity handling, support response expectations
- Contract scope
- Specific uptime targets, credits, exclusions, and remedies
- Related pages
- Support Levels, Subscription Terms, Availability and Resilience
SLA commitments apply differently across Community, Essentials, Enterprise, and Regulated packaging.
Public pricing already sets response expectations by tier, which gives buyers a concrete service model before contracting.
Uptime targets, service credits, and exclusions should always be finalized in the order form and full SLA schedule.
The public website should distinguish between operational promises and contractual remedies. The operational story includes monitoring, incident response, and resilience practices. The contract story includes availability targets, exclusions, credits, and scope boundaries.
Community access does not include a commercial SLA. Paid tiers introduce progressively stronger support commitments and may incorporate availability language where the subscribed service and architecture make that commitment meaningful.
Community
No paid SLA. Support is self-service and community-led with no guaranteed response commitment.
Essentials
Standard support model with a published initial response target of 4 hours for covered support issues.
Enterprise
Premium support model with a published initial response target of 1 hour for covered incidents and production-impacting issues.
Regulated
Mission Critical support model with a published initial response target of 15 minutes for the highest-severity covered incidents.
This website does not publish a one-size-fits-all uptime percentage because the real commitment depends on deployment architecture, support scope, maintenance assumptions, and the exact service being sold.
The full SLA should define measurement windows, planned maintenance handling, customer-caused exclusions, and any service-credit mechanics. This page exists so buyers can understand that structure before legal review starts.
If openCenter later standardizes public uptime targets by tier, this page should be updated to publish those numbers plainly instead of forcing buyers to infer them.
See how channels, escalation paths, and tier packaging align to the public response model.
Review the commercial baseline that incorporates SLA and support obligations.
Connect contractual expectations to the technical and operational reliability model.