Status
How operational state is communicated today.
We don't yet run a public status page. The platform's production deployments are small enough that a curated status feed would mostly say "all green" — and when it isn't, the customers affected hear it directly.
What you can rely on today
Operational practice — without the status page
- Direct notification. Production customers get notified by email and (where contracted) via Slack-shared channel within minutes of a confirmed incident affecting their environment.
- Post-mortems on the blog. Anything customer-visible gets a public write-up: what happened, timeline, fix, prevention. Not all on the blog yet — they'll land there as we accumulate the first few.
- SLA enforcement. Growth and Enterprise tiers carry contractual uptime SLAs (99.9% / 99.99%). Credit calculations are run quarterly; statements available on request.
- Internal observability. Prometheus + Grafana on the production deployment; on-call rotation for Enterprise customers; failure-spike alerts route to the on-call phone.
Roadmap
When this becomes a real status page
A public status page lands when we have enough customer-visible components to make it useful — realistic estimate: 2026 H2. The page will live at status.thoryn.org with per-component health (Hub · Broker · Trust Registry · etc.) and historical incidents.
Until then, the honest answer to "is it up?" is ask us directly — we'll tell you, with timestamps, in the same response.
Need a real-time uptime guarantee?
Enterprise tier carries a 99.99% SLA with quarterly credit. We can also share the last 12 months of internal Prometheus uptime on request.