Simple, transparent pricing
Start free, upgrade when you need more. No per-monitor fees. No surprises.
Straight talk before the table
I built watch4.me because I was tired of stitching three different free tiers together to keep an eye on my own projects. One for HTTP, one for cron jobs, one for SSL expiry, and not really trusting any of them. So I made the thing I actually wanted: every monitor type in one place, checked from multiple points around the world so one bad network path doesn't wake me at 3am over nothing.
Then I ran the numbers, and the result surprised me. I'd assumed the “premium” alert channels were expensive. That's why everyone gates them, right? Turns out email is essentially free, and SMS costs me almost nothing per message. The real cost is running the checks well, which happens to be the engineering I'm good at.
Here's the distinction that changed how I priced this. Some things cost real work to build but nothing per use, like a Slack integration. Others cost every single time you use them, like SMS. A gate only makes sense for the second kind. So I stopped gating the first: I built it once, and everyone gets it. The few things I do gate, I gate because there's a real per-use cost or a real abuse risk, and I'll tell you which is which.
No “contact sales,” no credit meter ticking in the background. — Joe
Free
For personal projects and getting started
- 10 active monitors
- 5-minute check interval
- All 6 monitor types
- Email, Slack, Discord, Webhook, Telegram
- 1 status page + 25 subscribers
- 7-day event history
- 1 team member
10 monitors, 5-minute checks, real alerts — not a demo. You can run a small project on this, and commercial use is fine. It's cheap for me to offer, so I do.
Start freeStarter
For freelancers and small teams
$90/year, billed annually
- 50 active monitors
- 1-minute check interval
- All 6 monitor types
- Email, Slack, Discord, Webhook, Telegram + 25 SMS/month
- 3 status pages + 100 subscribers
- 30-day event history
- 3 team members
25 SMS a month — real texts, and they renew every month, not a one-time bundle you burn through. They cost me almost nothing to send, so I'm not going to make you count them.
Get startedPro
For growing businesses
$190/year, billed annually
Pay yearly, save $38 (2 months free) You're saving $38/year
- 200 active monitors
- 30-second check interval
- All 6 monitor types
- Email, Slack, Discord, Webhook, Telegram + unlimited SMS
- 10 status pages + 500 subscribers
- 90-day event history
- 10 team members
30-second checks are the one thing that actually costs me more to run — so this is the honest reason to move up, not an artificial wall. SMS is unlimited here (fair use for real alerting).
Get startedBusiness
For agencies and enterprises
$490/year, billed annually
- 500 active monitors
- 30-second check interval
- All 6 monitor types
- Email, Slack, Discord, Webhook, Telegram + unlimited SMS
- 25 status pages + 2000 subscribers
- 1-year event history
- 25 team members
A full year of history and everything included. Storage is cheap; I gate the longest retention windows because someone has to draw the line, and this is the fairest place for it.
Get startedOn every plan, and why
- Slack, Discord, Telegram & webhook alerts
- I'm not knocking Better Stack for putting Slack on a higher tier. Building a solid integration takes real work. But once it's built, sending a message costs nothing per alert. I built it once; there's no per-use bill to recover, so everyone gets it.
- Commercial use allowed
- UptimeRobot moved their free tier to personal-use-only in 2025. Free tiers get abused, and I understand the call. I went the other way and defend it differently: use it for client work, no asterisk.
- Failure verification from a second location
- One probe seeing a blip isn't an outage. A failing check is re-verified from a second location before you're paged. Included, because a false 3am page is the fastest way to lose your trust.
- All 6 monitor types, no per-monitor fees
- HTTP, SSL, heartbeat, TCP, DNS, domain expiry, all at one flat rate. Per-monitor pricing is a reasonable model; it just happens to punish anyone running a handful of projects, which is who I built this for.
The part of the bill you don't see: staying up when it counts
An uptime monitor that goes quiet during its own bad day is worse than useless. So I think about this product the way I'd audit any critical system, by hunting down single points of failure and removing them one by one. I'm honest that I'm not done; here's where I already am:
- Checks run from more than one independent cloud (my own probes plus edge locations on Fly.io and Cloudflare) so one provider's bad route doesn't blind your monitoring or invent an outage that isn't real.
- A failing check is re-verified from a second location before you're paged. A single bad path doesn't wake you at 3am over nothing.
- I'm actively reducing the single points of failure that remain. I'd rather say that outright than pretend a small product is bulletproof. It's the same discipline I'm selling you: know where things can break, and watch them.