Status
Last updated
This page does not yet report live status. It is deliberately not wired to an automatic “all systems operational” badge, because a badge served from a static build says “operational” most confidently during the outage it was built for. Until it reads real health checks, it lists what the parts are and where to look.
| Component | What it covers |
|---|---|
| Web app and API | Sign-in, notes, search, everything under /w. |
| Sync (collaboration server) | Live editing. A failure here shows as a sync badge, not data loss. |
| Background jobs | Transcription, email intake, embeddings, exports, notifications. |
| Object storage | Recording audio and attachments. |
| Database | Everything else. Backed up nightly with continuous archiving. |
How to tell whether it is us
- Your notes keep working offline. A capture you have made is on your device before it is anywhere else, and it syncs when we come back.
- The sync badge in the app footer is the honest signal: saved locally means it is safe on your device, synced means it is safe on ours.
- If something looks wrong and this page says nothing, it probably means we do not know yet. Tell us on the support page.
Incident history
Incidents that affect customer data are written up here with what happened, what was affected and what changed as a result. There are none to report.
Recovery objectives
We target a 15-minute recovery point (how much work an outage could cost you) and a 4-hour recovery time (how long it takes to bring everything back on new hardware). The restore is rehearsed against a scratch database on a schedule, not assumed.