Know your sites are down before your customers do.
HTTP checks every minute, outages confirmed on the second failed check, a Microsoft Teams alert, and a status page with your logo on it.
Five monitors free, no card. Hosted, or on your own server on Enterprise.
A scripted outage on an example status page. Every element is the real UI.
- GitHub
- GitHub Actions
- Next.js
- React
- TypeScript
- Node.js
- Prisma
- PostgreSQL
- TimescaleDB
- Docker
- Caddy
- Let's Encrypt
- Ubuntu
- OVHcloud
- Cloudflare
- Stripe
- Twilio
- Microsoft Teams
- Tailwind CSS
- Redux
- Apache ECharts
Two failed checks open an incident. Two good ones close it.
Every site is requested on its own schedule, down to once a minute, with DNS, connect, TLS and first-byte timing on each request. A single timeout is usually the network, so nothing is reported until the next check fails too.
- Expected status codes per site
- Email alerts, and Teams immediately or after a per-site delay
- A second message when the site is back
- 14:02:00Check fails
pay.acme.com did not answer within 10 s. Nothing is sent yet.
- 14:03:00Confirmed
The next check fails too. The incident opens and the status page shows Checkout as down.
- 14:03:02Alert sentTeams · #ops
Microsoft Teams message in #ops, right away or after the delay set for this site.
- 14:05:00Recovered
Two good checks in a row. The incident closes after 2 min and #ops hears about that too.
One link for customers, with your logo and theme on it.
Each status page has its own address, name, logo and theme, an announcement banner for planned work, and 90 days of uptime bars per site. SSL and domain expiry are checked daily so renewals stop being surprises.
- Categories, search and six themes
- Unlimited viewers on every plan
- Only the sites you choose to publish
Owners run the workspace. Site admins see only what they own.
Invite the team and give each person a role: owners manage billing and people, admins manage every site, site admins get the sites you assign and nothing else. Enterprise runs the same product on your own servers with Docker Compose.
- Owner, admin and site admin roles
- Per-site access for site admins
- Self-hosted on the Enterprise plan
Free for five sites. Pay when the team grows.
Every plan has the public status page and SSL expiry. Teams alerts start on Pro; roles, domain expiry and 90 days of history on Team.
For a personal project or a small shop.
- 5 monitors
- Checks every 15 minutes
- Email alerts
- Public status page
- 30 days of history
- SSL expiry checks
- 1 seat
For a freelancer or a small team with a few sites.
- 25 monitors
- Checks every minute
- Alerts by email, Slack, Teams, Telegram and webhooks
- Public status page
- 60 days of history
- SSL expiry checks
- 3 seats
For product teams that run a few services.
- 50 monitors
- Checks every minute
- Alerts by email, Slack, Teams, Telegram, webhooks, SMS and calls
- 90 days of latency, uptime kept forever
- SSL and domain expiry checks
- Categories, search and six themes
- 10 seats: owners, admins and site admins limited to their sites
For companies that need a contract, not a card.
- Unlimited seats and 1000 monitors
- Everything in Team
- Self-hosted on your own servers
- Docker Compose deploy and nightly backups
- SLA, invoicing and a signed agreement
- Priority support and onboarding
Prices in USD, excluding VAT. Every plan includes the public status page with unlimited viewers.
How fast will I know a site is down?
With one-minute checks an outage is confirmed by the second failed check, so within about two minutes. The alert goes out right away, or after the delay you set for that site.
Why two failed checks instead of one?
A single timeout is usually the network between the checker and the site, not the site. Confirming twice removes almost all false alarms without slowing real incidents down meaningfully.
Can I run it on my own servers?
Yes. The Enterprise plan ships as Docker images with a Compose file: database, checker, web app and a reverse proxy with automatic HTTPS. Backups go to any S3-compatible storage.
What happens to old data?
Raw checks are kept for a week, 5-minute latency buckets for 30 days, hourly buckets for 90 days and daily uptime forever. The status page and reports use the aggregates, so they stay fast at any scale.
Can I change plans later?
Any time. Upgrades apply immediately and downgrades at the end of the billing period. Your history is kept for the plan you move to.