Why we're building StatusCheck
Uptime monitoring got loud, expensive, and metered by the seat. We're building the calm, flat-priced instrument we wanted to reach for first.
Every reliability team has the same moment. A page fires at 03:12. Someone reaches for a phone, squints at a dashboard, and needs to know three things in one look: is it actually down, what’s broken, and what do I do next?
The tools in this category have been getting worse at that moment while getting better at everything else. They’ve added logs, traces, AI summaries, and a per-seat line item for every person who might need to look. The dashboards got denser and colder. The invoices got harder to predict. And somewhere along the way, a false alarm became something you learn to tolerate rather than something the tool should have prevented.
StatusCheck is our attempt to build the instrument we wanted instead.
What we mean by “instrument”
A good measuring instrument is quiet until something needs your attention, precise enough that you don’t double-check it somewhere else, and honest about what it can and can’t see. That is the whole design brief.
Quiet. A single region seeing a failure is a data point. A second region confirming it is an incident. StatusCheck never pages anyone on one region’s opinion, on every plan, and it never sends the same alert twice. When the dashboard turns red, red means something, because it was quiet the rest of the time.
Precise. Every check records the whole timing story: DNS, TCP, TLS, time to first byte, download. Every result is stamped with the region it actually ran from. Down is never just down; it has a reason, and the reason is in the alert.
Honest. Eighteen regions, listed. Every result stamped with the one it came from. A status page that reads from the same confirmed checks as your dashboard, so it can’t say “operational” while your monitors say otherwise.
What we’re not doing
We’re not building an observability platform. Your logs and traces live somewhere already; StatusCheck stays on the outside of your infrastructure, checking what your users can reach, plus heartbeats for the jobs they can’t.
We do charge for people, and we’re not going to pretend otherwise. What we won’t do is make it the main lever: a teammate is $8 a month and an alert-only seat, for somebody who carries the pager but never opens the dashboard, is $2. Add the whole rotation. Nobody should be left off an alert to save money.
We’re not selling white-label as an add-on. Your logo, your domain, no “Powered by”, subscriber emails from your own address: part of the first paid plan. We looked hard at the tools that charge $250 a month per page to remove a line of text, and decided that wasn’t a business we wanted to be in.
Where we are
StatusCheck is in early access. The monitoring engine is a small, stateless Go prober that runs one check and returns exact timings. It is done and deployed across our regions. The dashboard, alerting, and status pages are being finished with the first teams now.
We’re inviting teams in small batches so that each one gets a real onboarding, and we’re locking launch pricing for everyone who joins during early access, for at least a year after general availability, whatever the list price becomes.
If you’ve ever silenced a monitor because you stopped trusting it, we’d like to show you something calmer. Join the waitlist, or email us and a person replies.
announcementearly-access