Status
System status
All systems operational
Components — last 90 days
Web application
100.00%
Public API
99.97%
Pricing engine
100.00%
Document generation (PDF)
99.95%
Recent incidents
| Date | Component | Duration | Summary |
|---|---|---|---|
| 2026-06-28 | Public API | 21 min degraded | Elevated latency during a database failover test; no errors returned. Runbook updated. |
| 2026-05-30 | Document generation | 34 min degraded | PDF renders queued behind a large batch job; concurrency limits added. |
SLA commitments
| Plan | Monthly uptime | Support response | Remedy |
|---|---|---|---|
| Starter | 99.5% | 2 business days | Service credits |
| Professional | 99.5% | 1 business day | Service credits |
| Enterprise | 99.9% | 4 business hours | Credits + termination right after 3 consecutive misses |
We publish 99.5% rather than the 99.99% that appears on most vendor sites because we run a single region today. A number you cannot hold is not a stronger promise — it is a refund schedule you have not budgeted for. Full terms, how uptime is measured, and the credit schedule are in the service level agreement.
Subscribe to incident notifications: status updates post here and to the email list — subscribe on the blog and check "status alerts".