Decision guide
Compare the base subscription with optional add-ons.
Status is computed from current releases, alerts, and aggregate lifecycle counts in the control-plane dataset.
Current status
Needs attention
Current service status summary.
This route publishes a public-safe aggregate of current release, site setup, site, and alert posture. It is intentionally narrower than the internal ops dashboard.
Aggregate counts only.
Current dataset, not a cached marketing score.
Paired with reliability and release notes for context.
Status is computed from current releases, alerts, and aggregate lifecycle counts in the control-plane dataset.
9
Tenants in dataset
5
Runtime registered
2
Active alerts
Current public-safe status
Status stays honest by publishing the current dataset shape instead of a blanket all-green claim.
Needs attention
Needs attention
Release posture
Current release registry state across stable and beta channels.
- Stable None
- Beta validation-1771969452
- Latest stable validation n/a
- Open release notes Review the release history route.
Watching
Site setup posture
Current lifecycle pressure in the public-safe dataset.
- Queued 0
- Running 0
- Failed 1
- Open launch path Review the public lifecycle route.
Needs attention
Alert posture
Current alert volume and routing severity in aggregate.
- Active alerts 2
- Waived alerts 0
- Blocking alerts 2
- Open reliability Inspect the current aggregate signal cards.
Dataset summary
Needs attention
Current public-safe service view
This is an aggregate of current tenant, site setup, alert, and release state in the control-plane dataset.
- Latest stable release No stable release recorded in the current dataset.
- Latest beta release validation-1771969452
- Site setup activity 0 running, 1 failed site setup job(s).
Boundary reminder
Setup truth
Why this route is aggregate-only
Public status can disclose current system state without exposing raw tenant details or protected infrastructure identifiers.
- Allowed Aggregate counts, current release ids, alert totals, and route-safe lifecycle state.
- Not allowed Tenant-specific domains, secrets, raw logs, or operational commands.
Validated
validation-1771969452 (beta)
Snapshot-backed release record with module and post-type version governance.
- Snapshot id 218346347
- Module versions 119
- Post type versions 64
- Built at 2026-02-24T21:46:30.140013
- Hero Initial release
- Rich Text Initial release
- Cta Initial release
- Split Initial release
Status disclosure: this is the current control-plane aggregate, not a synthetic uptime badge detached from the dataset.
Carry service truth into launch planning or account entry
Operational guide is more credible when it can route cleanly back into launch planning and protected access.