Evidence
The ledger
| Claim | Evidence | Last verified |
|---|---|---|
| Rolling patch upgrades are zero-downtime | 156/156 probes returned HTTP 200 during a live 26.6.0 → 26.6.2 upgrade — the published probe log, plus the UPGRADES.md row | 2026-08-25 |
| Minor upgrades have a ~16 s service window and sessions survive | Measured for 26.6.2 → 26.7.0, stop-start strategy — UPGRADES.md | 2026-08-25 |
| Every supported upgrade path re-proves itself nightly | The upgrade matrix: public GitHub Actions, cron 03:17 UTC — install the old version, log in, upgrade, and the pre-upgrade session must still refresh | nightly, in public |
| A clean install takes ~10 minutes | The smoke workflow installs from scratch on every commit — run durations are public | every commit |
| Sessions survive a full rolling restart | ./verify --drill session — runs in CI on every commit, and on your cluster whenever you like | every commit |
| Backups actually restore | ./verify --drill restore — pgBackRest restore to a scratch directory, on your own cluster | run it yourself |
| PostgreSQL fails over automatically | ./verify --drill failover — Patroni switchover with a write test through the load balancer | run it yourself |
Claims we do not make (yet)
- Air-gapped installs. The offline bundle is planned and will ship with the subscription. Until it exists, we don't sell it.
- A single-node-to-HA growth path. Growing from one node to three today means a fresh 3-node install plus a realm import. Documented, not hidden.
- An SLA. We publish measurements, not promises. An uptime number without a public probe log is marketing.
- SOC 2 / ISO certification. Certifications attest to how a vendor handles your data. Your data never reaches us — the code is auditable and the drills are runnable instead.
Corrections
Found a claim that's wrong, stale, or missing a receipt? Email hello@keelinfra.io — we correct within one business day.