What we commit to, per configuration.
Monthly uptime is best-effort on a single zone, 99.9% on HA, 99.95% on HA+ and 99.99% on Enterprise; the remedy is a pro-rata service credit against the next invoice. One table below for availability, one for recovery, one for support — every figure is the same figure on /pricing, in the FAQ and in the Terms. This page summarises, the Terms of Service govern.
- 1 Contractual — HA configuration. /terms § Availability — monthly uptime on HA (two zones, writer + standby).
- 2 Contractual — HA+ configuration. /terms § Availability — monthly uptime on HA+.
- 3 Contractual — Enterprise agreement. /terms § Availability — monthly uptime on Enterprise.
- 4 Engine changelog 2026-08: restore lands on a roll-up boundary, 5 s by default; the Intra-Segment PITR add-on tightens it to 500 ms.
Monthly uptime targets and what you get if we miss.
| Configuration | Topology | Monthly uptime | Remedy |
|---|---|---|---|
| Single-zone | One dedicated instance in one zone | best-effort | — |
| HA | Two zones · writer + cross-zone standby · automatic failover | 99.9% | pro-rata service credit against the next invoice |
| HA+ | Multi-zone · writer + two standbys · higher-capacity configuration | 99.95% | pro-rata service credit against the next invoice |
| Enterprise | As HA+, under an annual agreement with negotiated quotas | 99.99% | pro-rata service credit against the next invoice |
Uptime is measured per instance per calendar month. Scheduled maintenance, force-majeure events and outages caused by your own configuration are excluded from the calculation, as defined in the Terms. Credits are the sole remedy for availability shortfalls.
Recovery objectives you can put in a runbook.
- Backups
- encrypted nightly snapshots, included, integrity-checked daily, kept in the instance's region.
- Point-in-time recovery
- opt-in. Restore lands on a 5 s roll-up boundary; 500 ms with the Intra-Segment PITR add-on.
- Retention window
- 7 or 30 days self-serve, up to 35 days. Longer windows are agreed per deployment on Enterprise.
- Restore path
- From the console or the HTTP API.
Support that reaches an engineer.
Support reaches us at support@originchain.ai. Enterprise agreements include a named support engineer, and their response-time commitments are written into the agreement.
Need a different number? Ask for it in writing.
Custom availability, retention and support terms are agreed on Enterprise contracts.