Platform status.
Live uptime monitoring, incident history, and scheduled maintenance. Live dashboard goes up when v0.1 ships.
Pre-launch. No production traffic.
Veridra is in controlled-alpha development. There is no live customer production platform and therefore no customer uptime history to report. A public operational status page is a design-partner launch gate.
What the status page will publish
When the platform is live, this page will show:
Live health of every service: sdk-gateway, canonicalizer, signer, log, key-broker, govern, policy, framework, eval, drift, incident, api, packs.
Per-service uptime across the rolling 90-day window. SLO targets published per service.
Every customer-impacting incident with signed postmortem, resolution timeline, and affected systems.
Planned maintenance windows announced minimum seven days in advance.
Status per region: US, EU, UK, Africa — separate health indicators for each.
Email and RSS feeds for incident notifications. No account required.
SLO targets at launch
These are the service-level objectives Veridra will commit to at v1.0 GA. SLO performance against these targets will be published here, monthly, unedited.
| Service | Availability target | Latency target |
|---|---|---|
| sdk-gateway | 99.95% | p99 < 5ms |
| canonicalizer | 99.99% | deterministic |
| signer | 99.99% | p99 < 20ms |
| log | 99.99% | p99 < 100ms |
| api | 99.9% | p95 < 200ms |
| packs | 99.5% | p95 < 60s / pack |
Design partners running in sandbox environments from Q3 2026 receive direct Slack support and dedicated monitoring. Sandbox status is communicated per-tenant during onboarding.
For current engineering roadmap, see the architecture overview. To become a design partner: book a conversation.
April 2026 · pre-launch state · live monitoring at v0.1 (Q2 2026)