Status
How we tell you when something is wrong.
A status page that is always green is a status page nobody checks. Here is what we actually monitor and what we commit to telling you.
Current position
This page is not yet automated
Sensa does not currently publish a live automated status feed. Saying otherwise would be the easiest thing on this site to fake, so we are saying it plainly: today, incident communication is direct — we contact affected properties, and you can reach us at any time on hello@sensaspa.app.
An automated status page is on the roadmap and is not done.
What is monitored
| Check | What it proves |
|---|---|
| Liveness | The application process is running and answering. Requires no credentials and discloses nothing. |
| Readiness | The application can reach its database and its dependencies, so it can actually serve a request. |
| Background jobs | Scheduled work — no-show sweeps, reminders — is running on its interval rather than silently stopped. |
| Error log | Unhandled exceptions since the last restart, checked after every deployment. |
What we commit to
- A verified backup before every deployment. Not a scheduled backup we assume exists — one taken and checked as part of the release.
- Migrations rehearsed before they run. Schema changes are executed against real data inside a transaction and rolled back, so we know they apply before they apply.
- We tell you what broke. Including when the cause was ours, and including the part that is embarrassing.