sla ▸ targets committed LEGAL

Commitments you can hold us to.

For teams running automations in production, Enterprise plans come with uptime targets, support response times, incident communication, and Monitors as fast as every 10 seconds.

Talk to sales View live status
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
figures ▸ headline targets 01
99.9%monthly uptime target (Enterprise)
10sfastest Monitor cadence (Enterprise)
< 1 hrP1 support response (Enterprise)
24/7incident monitoring

Specific targets, credits, and remedies are set in your Enterprise agreement. The figures above describe the Enterprise tier and are a starting point for that conversation, not a self-serve guarantee.

scope ▸ what is covered 02

What the SLA covers

Uptime commitments apply to the Writ-managed services.

Managed API & app Covered The /v1/* managed endpoints, REST API, and app.usewrit.app.
Cloud run fleet Covered Workflow execution on the managed cloud fleet, including the gVisor-isolated tier.
BYO / local runs Outside scope Runs on your own hardware depend on your machine and network, so they sit outside the managed-service uptime target.
support ▸ response times 03

Support response targets

Response times scale with severity. Priority queues and a dedicated contact come with Enterprise.

Severity Definition Enterprise target response
P1 - Critical Managed service down or major degradation in production. Under 1 hour
P2 - High Significant feature impaired; no full workaround. Same business day
P3 - Normal Minor issue or question with a workaround. 2 business days

Self-serve plans receive community and standard support; the targets above are part of an Enterprise agreement.

incident ▸ how we communicate 04

How we communicate

Transparency during an incident is part of the commitment.

  • Public status updates as an incident moves through investigating, identified, monitoring, and resolved.
  • A post-incident summary for qualifying incidents, with cause and corrective actions.
  • Direct notification to your Enterprise contact for P1 events.
  • Service-credit eligibility measured against the public status record.

No fabricated numbers. Uptime is measured from our monitoring stack and published on the status page. Credits are calculated against that record, not a marketing figure.

faq ▸ common questions 05

SLA questions

Who gets an SLA?
A contractual SLA with uptime targets and support response commitments is part of our Enterprise plan. Self-serve plans run on the same infrastructure with the same engineering, but a signed, remedied SLA is an Enterprise agreement.
Does the SLA cover runs on my own machine?
Uptime commitments cover the Writ-managed services - the API, app, and cloud run fleet. Runs on your own BYO or local agent depend on your hardware and network, so they sit outside the managed-service uptime target by nature.
How fast can Monitors check on Enterprise?
Monitors check as fast as every 10 seconds on the top cloud tiers, Enterprise included. A detected change can fire a workflow within seconds.
How do I see current status?
Live component health, uptime, and incident history are on the status page. SLA credit eligibility is measured against that record.
sla ▸ close 06

Get a service agreement for production.

Enterprise teams get uptime targets, fast support, and Monitors as fast as every 10 seconds.

Talk to sales Explore Enterprise