What we actually guarantee, and what we do not. This page exists because the
alternative is you finding out during an incident.
The short version. One site, one replica, no availability
guarantee, no service credits, and today your backups live in the same place as
your database. We do verify that those backups restore — automatically, every
day. If that trade is wrong for you, it is wrong, and we would rather say so now.
Availability
Uptime guarantee
None. Soft target, best effort, no SLA and no credits.
Redundancy
None. Single site. Your workload and its database each run as one replica, so a node failure is an outage, not a failover.
Planned maintenance
Announced by email in advance. Expect a small number of short windows a year; some of them are full restarts.
Incident communication
Yes. You hear from a person who knows what happened, not a status badge.
Your data
Backup frequency
Daily, overnight (03:00 UTC).
Recovery point (RPO)
Up to 24 hours. Work done between the last nightly backup and a failure can be lost.
Retention
14 days of daily backups.
Restores are tested
Yes — automatically, daily. The newest backup is restored into a throwaway database and the restore must succeed, or we are alerted. Size and checksum checks are not enough: a truncated dump passes both.
Off-site copy
Not today. Backups sit on the same cluster as the database. That covers corruption and accidental deletion. It does not survive losing the site — that would take the data and the backups together. We are working on it; until this page says otherwise, assume it is not there.
Encryption at rest
Disk-level on our own hardware. Not per-tenant encryption.
Security posture
Database network isolation
Yes. Your database accepts connections only from your own namespace.
Shared infrastructure
Your workload runs on a cluster shared with other tenants and with our own build systems. We isolate at the network and namespace level, not with dedicated hardware per customer.
Compliance certifications
None. No SOC 2, no ISO 27001, no HIPAA/BAA. If you need an auditor's letter, we are not your supplier.
Getting your data out
Exports on request
Yes — a standard database dump, whenever you ask, at no charge.
Lock-in
None intended. It is your database in a standard format; you can take it anywhere.
If we shut down
You get notice and a final export. We would rather hand you a dump than disappear.
Why publish this at all? Because every line above is something
we would otherwise have to explain under pressure, to someone who had assumed
the opposite. A limit you knew about is a trade-off. The same limit discovered
mid-incident is a betrayal.