Can I vibe code UptimeRobot / Better Stack?
Ping your sites, alert you when they're down, status pages.
An uptime monitor is the single most vibe-codeable infrastructure product: a scheduled function hits your URLs, records status and latency, and alerts you on failures. Cron + fetch + a notification — that's the whole product for personal use. Add a public status page (a static page reading the same table) and you've replaced the paid tier entirely. The paid products earn keep at team scale: global probe locations, on-call rotations, incident management. You need none of that for your own sites.
Build an uptime monitor for my sites. A scheduled function (every minute) checks each URL in my monitors table: status code, latency, and an optional keyword the body must contain. Three consecutive failures → alert me (email + Slack webhook) and again on recovery, with downtime duration. Store checks efficiently (raw for 48h, hourly rollups kept forever). Public status page at /status: per-site current state, 90-day uptime bars, incident list. Admin page to add/pause monitors. Bonus: daily SSL and domain expiry checks with 14-day warnings. Next.js + Postgres + Vercel cron.
A monitor checking your URLs every minute from a scheduled function, logging status/latency, alerting on Slack/email/SMS after N failures, plus a public status page with uptime history.
- Multi-region probes (your checks come from one place)
- On-call schedules, escalations, incident timelines
- SSL/domain expiry monitoring unless you add it (add it — one prompt)
- Sub-minute check frequency on some tiers
Teams pay for the on-call machinery around the ping, not the ping. Solo builders have been overpaying for cron + fetch for years.
A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.
Start Course 01 →