Where these 2 reports land
Build it1
Scope it1
Keep it0
Category report
Uptime
2 products ranked by how much of their useful core an AI coding agent can reproduce: 1 strong build, 1 scoped build, and 0 weak replacements.
How the score breaks down here
- Interface
- 59
- Core workflow
- 67
- Data access
- 63
- Operations
- 35
- Trust & safety
- 54
63/100 average buildability
Why people keep paying here
- execution polish2 of 2 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
- scale infra2 of 2 reports
Reliability at the vendor's scale is an operations problem, not a prompt.
- brand trust1 of 2 reports
Trust, audits, and counterparties matter more than feature parity.
The typical achievable core in this category: ping endpoints, store status history, and notify when checks fail.
Build it
Better Stack / UptimeRobot paid
A cron loop, a fetch, an alert webhook, and a status page. The $30/mo is for the dashboard gloss.
Scope it
Instatus
The page itself is the easy part: components, colored dots, an incident timeline, a 90 day uptime bar; an agent will hand you that with a focused implementation. The notification fan-out is where it gets annoying: email is a Resend account and a loop, but you inherit double opt-in, unsubscribes, bounce handling, and explaining why the incident email landed in spam during the outage. Hosting is the other half: a status page on the same infra as the thing it reports on is decoration, so you need a separate host and domain and the discipline to keep it boring. Add the workflow Instatus quietly gives you, writing an update from your phone at 2am, per-component subscriber preferences, Slack and RSS and webhooks. Buildable in a focused implementation for a personal project; not the thing to hand-roll if a real customer contract mentions the words 'status page'.