Better Stack (formerly Better Uptime) publishes a real pricing page, but reading it is its own project. The product is now uptime monitoring, on-call, incident management, status pages, logs, tracing, and session replay stacked into one modular bill. If all you want is "tell me when my app is down and when a cron job doesn't run," most of that pricing table is noise.
Here's the short version, verified against Better Stack's live pricing on August 13, 2026: the free tier is genuinely generous for a small project, and the paid pricing is a base seat plus a menu of per-unit add-ons. Whether it's cheap depends entirely on which parts you turn on.
What does Better Stack actually cost?
Start with what's free, because for a lot of side projects the free tier is the whole answer.
The free plan includes:
- 10 uptime monitors and 10 cron heartbeats
- 1 status page
- Slack and email alerts
- A starter allowance of logs, traces, metrics, and session replay (a few GB each, short retention)
That is a lot for $0. If you run a handful of services and a few scheduled jobs, you may never pay Better Stack anything.
The paid side is where you need to read carefully. It splits into two kinds of charges: seats and add-ons.
Where does the Better Stack bill actually come from?
A paid Responder seat (Uptime plus Telemetry access) is $34/mo, or $29/mo billed yearly. That's the per-person cost for someone who needs the full paid feature set, including on-call response.
On top of seats, the monitoring add-ons are priced per unit. The numbers below are Better Stack's list prices as of August 2026 (monthly, with the yearly rate in parentheses):
Extra uptime monitors +$25/mo ($21/mo yearly) per 50 monitors
Extra cron heartbeats +$20/mo ($17/mo yearly) per 10 heartbeats
Extra status page +$15/mo ($12/mo yearly) each
Call routing +$250/mo ($208/mo yearly) per phone number
Then, separately, telemetry (logs, traces, metrics) and real-user monitoring (errors, session replay, web events) are metered by volume. You either buy a bundle or pay as you go at roughly $0.10 to $0.35 per GB ingested, plus a smaller per-GB retention charge. The exact figure depends on the data type and how long you keep it.
None of this is a gotcha. It's a deliberate, usage-based model that scales down to free and up to enterprise. The catch for a solo dev is that "how much will this cost me" has no single answer until you list what you're turning on.
How much does Better Stack cost for a solo dev?
Two realistic scenarios make the shape clear.
Scenario A: small project, inside the free limits. Eight HTTP monitors, six cron heartbeats, one status page, Slack alerts. Cost: $0. Better Stack's free tier wins here outright, and it's more generous on monitor count than most competitors' free plans.
Scenario B: you've outgrown free. Say you now run 20 services and 30 cron jobs, and you want a second status page for a client. That's 10 free monitors plus enough add-on blocks to cover 20, the free 10 heartbeats plus two more blocks of 10, and one extra status page. On the yearly rate that's roughly $21 (monitors) + $34 (heartbeats, two blocks) + $12 (status page), so about $67/mo before you add a paid seat or any log volume. Add a Responder seat and it's north of $95/mo.
Neither scenario is Better Stack being expensive for no reason. Scenario B buys you real capability. But if the only thing driving that bill is a pile of cron jobs, you're paying observability-suite prices for a dead man's switch.
What about logs, traces, and session replay?
This is the part that makes Better Stack worth its price for the right team and irrelevant for everyone else.
If you want your uptime data, your application logs, your traces, and your session replays in one place with one login, Better Stack is genuinely good at that, and it markets itself as far cheaper than Datadog for the same job. The telemetry bundles start around $30/mo and climb with volume.
If you don't ingest logs into a SaaS at all, that entire pricing dimension is money you'll never spend, and it's also the reason the pricing page looks so intimidating. A pure uptime-and-cron user can ignore two-thirds of it.
Better Stack vs a flat-price monitor: which is cheaper?
Once you're past the free tier and you only care about uptime and cron monitoring, the math changes fast.
CanaryHub is priced as a flat tool rather than a platform:
- Free: 1 project, 3 monitors, 5-minute checks, Telegram alerts (batched every 4 hours), an AI daily digest.
- Pro, $8.99/mo ($71/yr, which works out to $5.92/mo): 3 projects, unlimited monitors, 60-second checks, and instant alerts with no batching.
- Business, $24.99/mo (coming soon): unlimited projects and monitors, team seats, 30-second checks.
The difference that matters for cron-heavy setups: on CanaryHub Pro, monitors and heartbeats are unlimited under one $8.99 price. On Better Stack, heartbeats past the free 10 are $20/mo per additional 10. So the 30-cron-job case that costs roughly $40/mo in Better Stack heartbeat add-ons is inside the flat $8.99 on CanaryHub.
There's also the alert path. CanaryHub is Telegram-first and native, plus email, Slack, and Discord. Better Stack has no native Telegram integration as of this writing, so a Telegram workflow means routing through Zapier or a similar bridge.
Be fair about the trade, though: Better Stack's free tier gives you 10 monitors to CanaryHub's 3, and Better Stack does a pile of things CanaryHub deliberately doesn't.
When should you stay on Better Stack?
Better Stack is the right call, and worth its price, if you need any of these:
- Centralized logs and traces. CanaryHub does not ingest logs, do APM, or do distributed tracing. If you want that under one roof, Better Stack is built for it.
- Real on-call scheduling and escalation. Rotations, phone and voice escalation, and incident management are core Better Stack features. CanaryHub is a solo-dev alerting tool, not an on-call platform.
- Session replay and real-user monitoring. Also out of CanaryHub's scope.
- Hosted status pages beyond one. Better Stack's status pages are mature; CanaryHub does not offer them.
If your list is "watch my endpoints, catch my cron jobs when they go silent, text me on Telegram, and give me one predictable number on the invoice," a flat-rate monitor is the cheaper and simpler fit. If your list includes logs, tracing, or a real on-call rotation, Better Stack earns the modular bill.
How do I move uptime and cron monitoring somewhere cheaper?
Uptime checks port over by just pointing the new monitor at the same URL. Cron heartbeats are one line at the end of the job:
#!/usr/bin/env bash
set -euo pipefail
/usr/local/bin/nightly-backup.sh
# Only runs if the backup above succeeded. Silence = you get alerted.
curl -fsS -m 10 --retry 3 "https://ingest.canaryhub.ai/ping/YOUR_TOKEN" > /dev/null
The pattern is identical to Better Stack's heartbeats: ping a unique URL on success, and if the ping doesn't arrive within the interval plus a grace period, you get an alert. Moving it is mostly find-and-replace on the ping URL.
If you're comparing options first, the honest starting point is your own list. Add up the monitors, heartbeats, and status pages you actually need, decide whether logs and on-call are in scope, and price both. For a lot of indie setups the answer is "Better Stack's free tier, until I outgrow it, then a flat-rate tool" rather than a paid observability suite.
For more on the cron side specifically, see our guide on monitoring a cron job with a dead man's switch.