SERVICE CARD / uptimeflare

UptimeFlare

Service monitoring and a public status page with scheduled probes and D1 history

DECIDE FIRST

What is this project

A self-hosted website and API monitor with a public status page

What problem does it solve

Small teams often learn about outages from customers and lack a simple status history to inspect

Who it is for

  • Small SaaS teams
  • Studios and service providers that need a public status page

What it can do

  • Probe configured URLs on a schedule
  • Store status history in D1
  • Publish a status page with optional notifications

Before you deploy

  • Cloudflare Workers, Pages, D1, KV and Cron
  • The deployer configures monitored URLs and notification targets

What to know first

  • It is not a full incident-management or SLA platform
  • Probe frequency is limited by account quotas and schedules

WHAT HAS BEEN CHECKED

Discovered4 EVIDENCESPEC 0.2.02026-08-03
Public evidence, scoped to this version and date.

How it runs

UptimeFlare verified service screenshot
Screenshot referenced by the published Evidence Pack
UptimeFlare 架構與資料流（依部署契約機械生成）使用者WorkerPagesD1 資料庫KV 儲存Cron 排程使用者設定端點cloudflare.com
Architecture generated from the Service Card data flow.

Give this to your Agent

Please follow https://github.com/smallgreen-cloud/adapter-uptimeflare/AGENTS.md to deploy this service

Where it runs and what it touches

Upstream
lyc8503/UptimeFlare
License
Apache-2.0
Profile
small-app
External services
(user-configured)、cloudflare.com、(user-configured)
Data flow
Scheduled checks status history and optional outage notifications run in your own account

Source evidence

← Back to service index