System status
The public status page, the status endpoint and the authenticated health report.
System status
The public page
/status is the human-facing status page. It renders the current state of each service with the copy maintained in content/status.ts, and it names how to report a problem.
The public endpoint
GET /api/status requires no session:
{ "success": true, "message": "API server is running", "time": "2026-10-24T09:41:02.118Z" }Use it for an external uptime check. It proves the app is serving; it does not prove the database is reachable.
The authenticated health report
GET /api/health requires a session and reports reachability per service — Postgres, realtime, object storage and serverless functions — each with ok and detail. It never returns environment values, only whether the dependency answered.
{"postgres": { "ok": true, "detail": "Lakebase Postgres reachable" }, "realtime": { "ok": false, "detail": "NEON_REALTIME_SECRET not set" }
}A dependency that is not configured reports ok: false with the reason, which is the difference between "broken" and "not enabled".
Monitoring it yourself
- Ping GET /api/status from your own monitor for availability.
- After sign-in, call GET /api/health to see which dependencies are actually wired.
- Watch the SSE feed: if /api/notifications/live stops delivering while writes still succeed, the realtime dependency is the thing to check.
Environment-driven services
Realtime, storage and functions are optional and switch on when their secrets are present. The health report is the fastest way to see which of them are live in a given environment.