Queued is not live
A deployment or build that is queued, requested or building is displayed in exactly that state. Nothing is shown as published before it is.
Status
What is live, checked from your browser.
This page asks the platform health endpoint on this origin whether the web runtime is answering, and shows exactly what came back. It does not claim monitoring that does not exist.
What this check covers — and what it does not
Web runtime — GET /api/health
Checking
Asking the health endpoint on this origin for its status.
Scope of the check
- EndpointGET /api/health on this origin
- What it provesThis web runtime answered and returned {"status":"ok"}
- What it does not proveDatabase, queue, workers, payments or provider connections
- HistoryNone — no uptime record is kept
- External probeNone — the check runs from your browser only
The health route deliberately reads no configuration, database or provider state, so it can never leak or depend on secrets. That also means it can only ever tell you that the web runtime is up.
Area by area
The honest state of each area right now — implemented, live, or still being built.
| Area | State | Note |
|---|---|---|
| Web runtime | Live | The site you are reading, including this page and the health endpoint above. |
| Identity, projects, source and builds | Implemented | Accounts and sessions, projects, source versions with history, comparison and export, isolated builds with verified artifacts, and AI builder run states. |
| Billing backend | Implemented, not live | The credit ledger, verified top-ups and subscription fulfillment are implemented. No price catalog is published, so no purchase can be completed. |
| AI generation | Needs a provider key | A builder run with no configured AI provider key reports not_configured. It never fabricates output to look successful. |
| Deployment and hosting activation | In development | Builds produce verified artifacts; serving and publishing those artifacts to a domain is not activated. |
| Domains, WordPress, App Store, AI agents, backend, usage, admin | In development | Specified modules. They are absent from the customer navigation rather than shown as working features. |
| Monitoring, alerting and status history | In development | The specification calls for platform monitoring, alerting and a public status page architecture. None of those exists yet, and this page does not pretend to be one. |
How to read platform state honestly
A few rules the platform applies everywhere — they are the reason some states look different from a marketing page.
Not configured is not a bug
When a provider key or connection is missing, the platform says not_configured and stops. It does not invent a result or retry forever.
A failure stays a failure
A failed build or run records the failure and its category. A build artifact receipt exists only after the bytes have been hashed, stored and read back.
No invented numbers
There is no uptime percentage, incident history or customer count on this page, because none of those exist yet to report.
Read the boundary, not a banner.
The docs page lists what is implemented module by module, and the developers page lists the endpoints that exist today.
There is no uptime history, incident feed, SLA or third-party probe behind this page. Those are in development, and this page will link them when they exist.