No client-side rate limits
Upptime calls the GitHub API from the visitor’s browser (60 req/h/IP), so popular pages break with a “rate limit exceeded” screen. StatusBeam renders every byte at the edge from its own store — the browser never talks to a third-party API.
Reliable scheduling
Upptime rides best-effort GitHub Actions cron (a “every 5 min” job can slip to 15–60 min). StatusBeam uses Cloudflare Cron Triggers, which fire on time.
A store that scales
Instead of walking git commit history through a rate-limited API, StatusBeam uses Cloudflare D1 + KV, purpose-built for time-series reads.
A current frontend
Upptime’s page is built on end-of-life Svelte 3 + Sapper. StatusBeam is Astro + shadcn/ui, shipping ~0 JS for everything but the interactive charts.
Every page is available as clean Markdown at <page>.md.txt, the whole site is
published as /llms.txt and /llms-full.txt, and
each page has a Copy Markdown button plus Open in ChatGPT / Claude
actions. See AI & LLM endpoints.
