Status
Checked live when you loaded this page, not cached.
All systems operational.
CHECKED 2026-09-01 12:47 UTC
Components
- Parliamentary record databaseOperational
- Search and retrievalOperational
Search and retrieval degrades independently of the record itself. Emily keeps answering when it does; she answers from less.
Recovery objectives
These are the targets we hold ourselves to, and the mechanism behind each one. Where the mechanism is weaker than the target, it says so rather than rounding up.
| Objective | Target | Mechanism |
|---|---|---|
| Recovery point objective (RPO) | 24 hours | Supabase takes a daily automated backup of the production database, retained for 7 days. Point-in-time recovery is available on the platform but is not enabled on this project, so a restore returns the state of the most recent nightly backup. Reducing this target means enabling PITR, not editing this line. |
| Recovery time objective (RTO) | 4 hours | Restore of the most recent backup into the production project, followed by the documented smoke checks. Target, not yet rehearsed. It is derived from the restore procedure rather than from a timed run, and it stays a target until a drill has been carried out and recorded. |
| Application recovery | 15 minutes | The application layer is stateless on Vercel. A bad deploy is rolled back by promoting the previous production deployment; nothing has to be restored to do it. |
| Parliamentary corpus rebuild | 7 days | The public record is re-derivable from source: every sync script can replay from the upstream APIs and the RAG index can be rebuilt from the synced tables. Slow, and it costs embedding spend, but it is not lost. Customer data (conversations, CRM, briefings, documents) is NOT re-derivable and depends entirely on the backup above. |
Customer data is stored in a single Supabase project in AWS eu-west-2 (London). There is no second region and no read replica, so a full regional outage at that provider is an outage here too. We would rather write that down than let a buyer discover it.
More on how the service is built and run: Security · Sub-processors · Data processing agreement.
Something wrong that this page says is fine?
The checks above cover the database and the retrieval layer. They do not cover every way the product can disappoint you, and a green page is not a contradiction of what you are seeing. Tell us: support@emilypolitics.com.