Skip to main content

for saas teams

A status page your SaaS customers actually trust

Monitor every dependency, open incidents automatically, and show customers a branded status page on your own subdomain, without standing up a status tool of your own.

Monitor the whole stack

Your API, your database, your payment provider, your mail sender. A SaaS is down whenever any dependency your customers feel is down, so each one gets its own monitor: HTTP, TCP, DNS, TLS, domain, ping, heartbeat and browser-flow checks every 60 seconds, each with its own expectations and its own alert channels. A slow TLS handshake on the payments endpoint and a broken DNS record on the docs site are different problems, and they can page different people.

Tell customers before they tell you

A down monitor opens an incident automatically and posts it to your public page, so the page updates before the first support ticket lands. Add a human note when you know more and your customers watch the fix land in real time. Subscribers get every update by confirmed email or signed webhook, which means the people who care most stop refreshing the page and stop writing to support.

An uptime bar nobody can quietly edit

The 90-day bar on your page comes from real checks, confirmed across regions, not from which incidents someone chose to publish. There is no button that turns a red day green. That cuts both ways, and that is the point: the number your customers see is the number your checks measured, so the uptime you quote in a sales call is a claim you can make with a straight face.

Alerts that don’t cry wolf

Per-monitor channels, dedupe and flap-suppression mean a 60-second blip in one region never pages on-call at 3 a.m. The same confirmation rule feeds the alerts and the public bar, so the page and your pager can never tell different stories. When on-call does get woken, the page already shows why.

A page that reads as yours

The page lives on your own subdomain with your logo and colours, so it reads as part of your product rather than a third-party widget. Scheduled maintenance windows announce planned work ahead of time, so a migration weekend arrives as a calendar note instead of a surprise incident.

FAQ

Can I put the status page on my own domain?
Every org gets a branded status page on its own subdomain with your logo and colours, and a custom CNAME is on the way.
How fast does it detect an outage?
Checks run as often as every 60 seconds from multiple regions, and a failing check opens an incident automatically and posts it to the page.
Will the status page stay up when my app is down?
Yes. The public page is cached and served independently, so it keeps loading even when the service it reports on is struggling.
Can customers subscribe to updates?
Yes. Visitors opt in with confirmed email or webhook and hear about every incident and maintenance change, with signed payloads they can verify.

At a glance

  • Check interval every 60s
  • Check types HTTP, TCP, DNS, TLS, domain, ping, heartbeat, flow
  • Alert channels Slack, Telegram, PagerDuty, SMS + more
  • Public history 90 days
  • Price to start free, no card

Links

Start in under 5 minutes.

Start free

features · pricing · notes