Operational Status
A current view of each plane in the Vorantiq operating environment. This page is hand-authored and updated when state changes; it is not yet wired to an external status provider, and we will say so plainly until that integration ships.
Pre-launch posture
Vorantiq is in pre-general-availability. Real-time telemetry exists in production but is not yet aggregated into an external uptime feed. The states below reflect last-known operational posture, not a continuous probe.
Status legend
Plane is running on its intended architecture and meeting expected behavior under current load.
Plane is running but a known dependency, latency target, or capacity headroom is below intended posture.
Plane is running but a recent change, anomaly, or external dependency warrants closer attention before it is declared fully operational.
Plane cannot be advanced or modified in production until live database identity is verified. Existing production behavior is unaffected.
Capability is intentionally not yet integrated with an external monitor. We will not show fake green dots here.
Plane status
Control Plane
OperationalTenant policy enforcement, quotas, autonomy posture, kill-switches.
Identity Plane
OperationalAuthentication, session management, refresh-token rotation, tenant binding.
Routing Plane
Blocked by Production-Safety StopProvider selection, model routing, latency tracking, pricing lookup.
Execution Plane
OperationalAgent/orchestrator runtime, provider adapters, task lifecycle.
Audit Plane
Under observationHash-chained audit log, integrity verification, append path.
Spend Plane
Under observationStripe webhook ingestion, billing reconciliation, SpendGuard scaffolding.
Frontend Surface
OperationalPublic marketing, Trust Center, Legal, Architecture, dashboard surface.
Active conditions
Production-Safety Stop is active. Live database identity is unverified, so Phase B runtime advances (routing-schema migrations, SpendGuard rollout, audit-events backfill) are paused until DATABASE_URL is confirmed against the live Neon endpoint via the Vercel/Neon dashboard. Existing production behavior is unaffected; only future advances are gated.
Incident communication
P0 / P1 / P2 severity bands with first-update and cadence targets are documented under Reliability Posture. When an incident is active, this page is updated by hand on the same cadence as the status-page entry.
Maintenance communication
Planned maintenance is announced at least 24 hours in advance for any tenant-visible surface, and at least 7 days in advance for any change that requires tenant action. Routine deploys without tenant-visible behavior change are not announced.
External monitoring (planned)
Future state: an externally hosted status page with continuous uptime probes per plane, RSS/email subscription, and historical incident archive. We will not switch the marketing copy to “monitored continuously” until the probe is live and reporting.