Live
Status
LiveNeeds Workers Paid
NoEstimated monthly cost
$0/moReplaces
Statuspagefrom $29/mo
How it runs on Cloudflare
- WorkflowsRuns checks on a schedule.
- WorkersPings endpoints, serves the page.
- D1Uptime history.
Compared
Compared onStatuspageSaaSUptime Kuma on a VPSSelf-hosted sampleStatusboardFlareyard on Cloudflare
Who holds your dataThey doYouYou
Servers to runNoneOne, at leastNone
ScalingPlan tiersResize by handAutomatic
UpdatesForced on youYou patchPull requests
Your agent can change itNoYes, you deployYes, tests gate it
Same
- HTTP checks
- Status page
- Incident notes
Different
- Checks from Cloudflare's network
- Nothing to keep up
- Your agent can add a check type
What it costs you
What it creates in your account
- Workers
- Cron Triggers
- D1
What it asks Cloudflare for, and why
workers-platform.writeDeploy the checker.Requiredd1.writeKeep uptime history.RequiredScope names are illustrative until the OAuth scope list is final.
Shape it
Ask your agent, in your own copy of Statusboard:
› Ping our API every minute from three regions and post incidents to Slack.Updates
Each release arrives as a pull request. Sample history.
v1.0.0First release.