UptimeFlare

uptimeflare

lyc8503's UptimeFlare — an uptime monitor and status page: HTTP, HTTPS and TCP checks every minute, 90 days of uptime bars, twelve hours of latency charts, incident history, scheduled maintenances, webhook notifications and a JSON API — running as one Cloudflare Worker: the status page built by @opennextjs/cloudflare into Workers + Static Assets, and the checks on a Cron Trigger of the same Worker, their state in a Cloudflare D1 database provisioned by Terraform through Orun and its schema applied by migrations — and packaged as an Orun baseline: one command takes a new status page from nothing to live and checking on stage and prod, in its own repository, under its own name, in ONE landing.

Upstream already runs on Cloudflare, as two deployables — a Pages project built by @cloudflare/next-on-pages for the page and a second Worker for the checks, sharing one D1 database. Here they are one Worker: its custom entry (apps/web/worker.ts) re-exports OpenNext's fetch and adds scheduled, which runs upstream's checker loop unchanged. The Durable Object remote checker (geo-specific checks) is left out. What the baseline adds is everything needed to make a copy of it somebody else's, built the way turso-starter and cron-starter are. See specs/epics/uptimeflare for the design, the milestones and the as-built status.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/uptimeflare
cd uptimeflare
orun new --blueprint repo-blueprint.yaml --out ~/sites/acme-status --run-hooks --resume \
  --set reponame=acme-status --set productname="Acme Status" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → uptimeflare → Build). Two phases: 01-product creates the repository and lands the whole product as ONE pull request — intent, CI, tooling, the D1 root, the migrations, the status page with its checker, and its tests — and one convergence, per environment, applies the D1 database, then its migrations, then deploys the Worker with its id and its Cron Trigger, smoke-tested on a check the trigger recorded; 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase. The Workers Free plan is enough: the product registers one Cron Trigger per Worker.

The new repository receives the product only — the app, its D1 root, its migrations and their runner, its tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Cloudflare Worker and database names. None of this repository's machinery ships.

What is here (the product)

Configuring the monitors

Everything a status page shows is in apps/web/uptime.config.ts, as upstream has it: pageConfig (title, header links, groups, logo, footer), workerConfig (the monitors, the write cooldown, notifications, callbacks) and maintenances. It ships with three public monitors — Cloudflare and GitHub over HTTPS, Google Public DNS over TCP — so a new page has something to check; replace them with your own. Each monitor's id keys its history: keep it and the history stays, change it and the monitor starts over.

A check through a proxy (checkProxy) works for globalping:// and http(s):// proxies; worker://<region>, upstream's Durable Object, is not part of this port — such a monitor reports why it is down, or is checked from the Worker itself with checkProxyFallback: true.

Only id, name, tooltip, statusPageLink and hideLatencyChart reach the browser (the CVE-2026-29779 fix, kept); a test holds that list. A webhook whose URL embeds a token is still a credential in this file, as upstream designs it — keep the repository private, or send notifications from a callbacks function, which receives the Worker's env.

Getting started

pnpm install
pnpm run wire:fixture   # render apps/web/wrangler.jsonc from the offline fixture
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # next build + opennextjs-cloudflare build → apps/web/.open-next

pnpm --filter @app/web db:migrate:local   # create the monitor_state table in wrangler's local D1
pnpm --filter @app/web dev                # http://localhost:3000 — the pages, against that D1 (no scheduler)
pnpm --filter @app/web preview            # wrangler dev over the built Worker, same local D1

Watching a check run

wrangler dev never runs the clock; --test-scheduled adds a /__scheduled endpoint that fires the handler:

cd apps/web
pnpm exec wrangler dev --port 8808 --config wrangler.jsonc --test-scheduled

curl http://127.0.0.1:8808/api/data                     # {"error":"No data available"} — nothing checked yet
curl "http://127.0.0.1:8808/__scheduled?cron=*+*+*+*+*"  # runs the checker once
curl http://127.0.0.1:8808/api/data                     # {"up":…,"down":…,"updatedAt":…,"monitors":{…}}

Deployed, the trigger fires every minute; the state is written when a status changes and otherwise every three minutes (kvWriteCooldownMinutes). Workers → the Worker → Triggers shows the one Cron Trigger; its logs show each check.

A private status page

Store user:password as the product's Orun secret STATUS_PAGE_PASSWORD for an environment and redeploy it: the build hands it to the Worker as a secret (tooling/wire/worker-secrets.mjs, the value over stdin, never in a bundle), and apps/web/proxy.ts asks every request for those credentials, the API's included. Locally, put the same line in apps/web/.dev.vars (.dev.vars.example). Removing the Orun secret does not remove the Worker's copy: delete it with wrangler secret delete STATUS_PAGE_PASSWORD --name <worker> too.

How it maps to UptimeFlare's own deployment

How the database reaches the Worker

infra/terraform/cloudflare-d1 ──apply──► orun secret WIRING_CLOUDFLARE_D1 (stage, prod)
                                               ▼
infra/db-migrate  dependsOn cloudflare-d1 (enforced on main) · secretEnv WIRING_CLOUDFLARE_D1
  apply:  packages/db's runner → POST …/d1/database/<id>/query, each pending migration once
                                               ▼
apps/web  dependsOn cloudflare-d1 + db-migrate (enforced on main) · secretEnv WIRING_CLOUDFLARE_D1_<ENV>
  build:  tooling/wire/live.mjs → wrangler.jsonc with the environment's database id
          (dev, verify-only, renders the fixture) → next build → opennextjs-cloudflare
  deploy: worker.ts (fetch + scheduled) and its one trigger, * * * * *
  smoke:  /api/data carries an updatedAt the trigger's checks wrote, no older than ten minutes

wrangler.jsonc is committed as the fixture render of wrangler.template.jsonc, because the deploy lane's verify-app-structure step checks the config exists before it builds.

CI

Licence

UptimeFlare is © lyc8503 and its contributors, under the Apache License 2.0 (apps/web/LICENSE); the code here derived from it keeps that licence.