Status pages that stay up when you're down.

Built-in monitoring, automatic incidents, and a pre-rendered status page that keeps answering "is it down?" while everything else is on fire. Open source, AGPL-3.0, self-hostable.

Start free — no credit card Star on GitHub

How it works

1. Add a monitor. HTTP, TCP or keyword check on any URL or host. Pick the interval; GET or lightweight HEAD requests.
2. We confirm before we shout. A monitor must fail two consecutive checks before an incident opens, so a blip never pages you.
3. Your status page updates itself. The incident is written, the page is re-rendered to static HTML, and subscribers are emailed — with Slack, Discord and webhook alerts for your team.

What you get

• Pre-rendered status pages that survive your origin going down
• HTTP, TCP and keyword monitors with configurable intervals
• Automatic incident open, update and resolve — no manual posting
• Email subscribers with double opt-in verification
• Email, Slack, Discord and custom webhook notifications
• Custom domains and branding on paid plans
• Scheduled maintenance windows and an embeddable uptime badge
• Self-host the whole platform with docker compose up

Pricing in one line

Free ($0) — 1 status page, 10 monitors, 5-minute checks. Indie ($9/mo) — 5 status pages with custom domain, 50 monitors, 1-minute checks. Pro ($30/mo) — 10 status pages, 100 monitors, 30-second checks. Self-hosting is unlimited and free. Full pricing.

Common questions

What is UptimeCrow?

UptimeCrow is an open-source status page platform with built-in uptime monitoring. It watches your APIs and websites, opens incidents automatically, updates your public status page, and alerts subscribers the moment downtime is detected.

How do status pages stay online when my origin is down?

UptimeCrow pre-renders your status page as static HTML on every incident update, served decoupled from your origin. Even if your app, API and database are all down, subscribers can still read your status page.

How does UptimeCrow prevent false alarms?

A consecutive-failure state machine. By default a monitor must fail 2 checks in a row before an incident opens, so a single network blip never pages your team. The confirmation count is configurable per monitor.

Can I self-host UptimeCrow?

Yes. The full stack is AGPL-3.0 and runs with a single docker compose up. You bring PostgreSQL and Redis; no vendor lock-in and no data leaving your infrastructure.

Is UptimeCrow really free?

Yes — free forever, no credit card. The free plan includes 1 status page, 10 monitors, 5-minute checks, email alerts, an uptime badge and 7-day history. Self-hosting is unlimited.