Uptimebell: uptime monitoring and a public status page for web teams
Checks your sites every minute, opens an incident after three failures, and runs a status page that emails subscribers.
Agent specs
- Agent
- Claude Code, Opus 5.5 Medium
- Time
- 20 min
- Cost
- $6.06*
Agents work faster and more accurately on Elements.
* Cost at API rates, September 2026.
Run it yourself
Paste this prompt into your AI agent. You get the finished app on your own machine, ready to change however you like.
Install elements:
curl -fsSL 'https://install.elements.dev?os=darwin' | sh && export PATH=~/elements/bin:$PATH
Create an Elements app from the elementscode/demo-uptimebell scaffold:
cd ~/elements/projects
elements create uptimebell -scaffold=elementscode/demo-uptimebell
cd uptimebell
Start the app.
The prompt
The exact prompt that built this app. Give it to your agent to build the app from scratch with Elements, or use it to compare what other tools make from the same ask.
Build an uptime monitor and status page named uptimebell. - Accounts; each account adds monitors: a name and a url, checked every minute. - A background job requests each url and records response time and status. Three failures in a row opens an incident and emails the account. - Dashboard: each monitor's current status, response time chart for the last 24 hours, and uptime for 24 hours, 7 days and 90 days. - A public status page per account with a component list, a 90-day bar per component, and incidents. - Post incident updates (investigating, identified, resolved); subscribers to the status page get them by email. Seed two accounts with monitors (some pointing at urls that fail), 90 days of check history, and past incidents. Show the seeded logins on the sign-in page. Statuses, charts and incidents update in real time on the dashboard and the status page.
Comments· 0