Every store.
One status screen.
All of Bohuvuj's stores and services — health-checked every 5 minutes, with 24h / 7d / 30d uptime history and a public page for each project.
Zero-config monitoring for every store
Alive in three steps — no agents, no extra servers, no per-service dashboards.
Store exposes /api/health
Each project returns { status, results[] } with a per-component status (db, storage, auth, …).
A cron poller checks every 5 min
A Cloudflare Worker wakes the status service, which calls every active project and stores per-component results.
Public page per project
Each project gets a slug page with uptime bars and a public JSON endpoint you can embed anywhere.
Built as the foundation for a product
Starts as Bohuvuj's internal board — architected to become a multi-tenant monitoring SaaS.
Multi-project by design
Add any future store or service from the Manage page in seconds — the poller picks it up on the next cycle. No redeploys, no new infrastructure.
Open Manage →Real history, not snapshots
Rolling 24h / 7d / 30d uptime bars per component, retained 90 days.
Public JSON per project
/api/status/[slug] so any site can embed a status widget without touching this app.
Private by default
RLS on with no public policies; every read/write flows through the service role server-side.
Alert hooks ready
ok=1 503 semantics mean any uptime checker (or the poller itself) can triage incidents.
Tenant-ready
Projects are isolated rows today; the table-level design maps directly onto per-user workspaces.
Self-serve management
The admin screen manages slug, name, health URL, and enable/disable — the exact surface future customers will use.
Monitored right now
Real-time readout of every project being polled.
Shipping another store? Add it in seconds.
Add the health URL, and it starts appearing within five minutes.