A status page that's driven by your actual incidents.
When you declare an incident, the status page already says so — because it's the same incident, not a second thing to go and update.
Custom domain, certificates handled, feed subscriptions, maintenance windows — plus the one thing that matters most: it updates itself.
90-Day Uptime
99.8%90-Day Uptime
99.8%Dashboard loading slowly for some customers
InvestigatingWe're seeing elevated load times on the dashboard for some customers and are investigating. We'll confirm here once load times recover.
Posted
Your status page updates itself, straight from the incident.
Declare an incident and the page already says so. Post an update and it's already published, and already in your subscribers' feeds. The affected components flip to the right status on their own — one incident, shown on every surface.
That's the difference from a status page you update by hand — nothing to remember, even during a real incident at 2am.
You set the severity. Your customers see plain English.
Inside the incident, your team works in severities — critical, major, minor. Your customers just need to know: working, kind of working, or down. So the severity you set maps to a public status automatically — four states anyone can read at a glance.
Your URL. Your logo. Certificates you never touch.
From your customer's point of view, it's a page on your product, not a page on ours.
Custom domain. status.yourcompany.com or any subdomain you own — point a CNAME at us. Certificates are handled for you.
Your logo, light and dark. Square or landscape variants, rendered to match the viewer's theme.
Per-page display toggles. Show only what's relevant on each page — uptime history, active incidents, changelog, and more.
Same page. The one your customers bookmark is on the right.
Customers subscribe once — and stay informed.
Every page has a feed anyone can follow — incidents and maintenance land in it as you post them, changelog entries if they want them. Signed-in customers get a personal feed of their own, scoped to the components they can see.
Signed-in customers automatically see more — the components and incidents the public can't.
Status feed
Public feed — anyone can follow
Your personalised feed
Feed content
Schedule the maintenance once.
Schedule a window — what it affects, when it starts — and it's on your status page ahead of time. Planned work never reads as an outage.
Database upgrade
Webhook delivery migration
Your customer sees it coming:
Database upgrade
Run to the work, not the clock
Start early, finish early — or let the window close itself at the scheduled end, or leave it open until you close it by hand.
Mute alerts only if you want to
Suppress alerts just for the components under maintenance — a planned job never hides a real outage somewhere else.
One status page for everything, or one per product. Your call.
A page is made of components — the parts of your product that can be up or down. Run one page covering everything you sell, or one per product, each with its own components, domain, logo, and subscribers. Your team works in one workspace across all of it; each set of customers sees only the page that's theirs.
However many pages you run, your whole team is included — see the pricing.
Webhook deliveries are failing
InvestigatingWebhook deliveries are failing for some endpoints. We've identified the cause and are rolling out a fix — we'll confirm here once deliveries recover.
Posted
Two products, two status pages, one internal workspace.
Want a status page that updates itself? Get in early.
StayUpfront is nearly ready, and I'm bringing in founding customers first — a small group at a time, so I can work with each of you directly. Founding customers get founding-customer pricing, a real say in what gets built, and a personal onboarding call with me.
Drop your emailDirect email from Rob when your slot's ready. No drip sequence.