Better Stack Free Tier 2026 — Uptime Monitoring, Status Pages, and Incident Management for $0

Better Stack Free Tier 2026 — Uptime Monitoring, Status Pages, and Incident Management for $0

Monitoring🛠 Better Stack

Better Stack's 2026 free tier: 10 monitors, 3-minute checks, a free custom-domain status page, incident management, and bundled logs. Setup guide, UptimeRobot/Checkly comparison, and pro tips.

reviewsmonitoringuptime-monitoringfree-tierdeveloper-toolsincident-management

Better Stack Free Tier 2026 — Uptime Monitoring, Status Pages, and Incident Management for $0

Most free uptime monitors stop at “is your site up?” Better Stack (formerly Better Uptime) keeps going: it hands you a branded status page on your own domain, incident management, and a bundled logs/metrics/error-tracking stack — all on the free plan.

In 2026, Better Stack’s free tier gives you 10 monitors and heartbeats, 3-minute check intervals, 1 status page with custom domain support, Slack and email alerts, 3 GB of logs (3-day retention), 40 GB of metrics, 100,000 tracked exceptions per month, and 5,000 session replays. No credit card. No trial timer.

That’s a meaningful bundle for $0 — especially because, as of 2026, UptimeRobot’s free tier now blocks commercial use, making Better Stack one of the few free monitors you can legitimately run on a paying product. This guide covers what’s included, how to set it up, where it beats UptimeRobot and Checkly, and how to squeeze the most out of every free monitor.


Better Stack Free Tier Cheat Sheet

Feature Free Tier Limit First Paid (Freelancer, $29/mo)
Uptime monitors + heartbeats 10 20 monitors
Check interval 3 minutes 1 minute (30s on higher plans)
Status pages 1 (custom domain included) More, with subscribers
Alert channels Email, Slack, 1 phone call Unlimited phone/SMS, more channels
Incident management Basic (acknowledge/resolve) On-call scheduling + escalation policies
Logs (Logtail) 3 GB, 3-day retention Higher retention
Metrics 40 GB Higher
Error tracking 100,000 exceptions/month More
Session replays 5,000/month More
Team members Limited Per-responder pricing
Custom domain on status page Free
Commercial use allowed Yes

What’s NOT on the free tier

  • Full on-call scheduling and escalation policies — drag-and-drop rotations and multi-tier escalation require a Responder license (~$29/responder/month).
  • 1-minute and 30-second checks — locked to the Freelancer and Business plans.
  • More than 10 monitors — each monitor or heartbeat counts toward the 10.
  • Subscriber notifications on status pages — letting customers self-subscribe to status updates is a paid feature.

What It Is and Why Use It

Better Stack is a unified monitoring and observability platform that bundles several products under one account:

  • Uptime monitoring — HTTP/website, keyword, ping, port, DNS, and heartbeat checks from multiple regions.
  • Incident management — alerts, acknowledgements, resolution workflows, and post-mortems.
  • Status pages — public or private, branded, hosted on your own domain.
  • Logs (Logtail) — structured log management.
  • Metrics & dashboards — infrastructure and app metrics.
  • Error tracking — exception monitoring tied to session replays.
  • Session replays — visual playback of user sessions for debugging.

For most free-tier users, the headline trio is uptime monitoring + status page + incident management. That combination is what separates Better Stack from a pure “pinger” like UptimeRobot.

Why teams pick Better Stack over the alternatives

1. The status page is the killer free feature. A hosted, branded status page on your own subdomain — at $0 — is genuinely rare. StatusPage.io and most competitors charge for custom domains. Better Stack includes it free, which instantly makes a small product look more credible and gives customers a single place to check “is it me or is it down?”

2. Incident management, not just alerts. When something breaks, Better Stack treats it as an incident: create it, acknowledge it, assign it, resolve it, and post updates to your status page. UptimeRobot and most free tools stop at firing an email.

3. No commercial-use restriction. As of 2026, UptimeRobot’s free tier disallows commercial use. Better Stack’s free plan has no such clause — you can run it on a paying SaaS without violating terms.

4. One platform, many signals. Logs, metrics, exceptions, and uptime in one place means when an alert fires, you can pivot from “the site is down” to “here are the error logs” without switching tools. Even on the free log/metrics allotments, that’s more than competitors offer at $0.

5. Modern, fast UI. Across 328 G2 reviews and Capterra ratings, the interface is consistently praised as intuitive with setup measured in minutes — a real differentiator from clunkier legacy monitors.


Key Free Tier Features and Limits — In Detail

Uptime monitors & heartbeats (10 total)

You get 10 monitors and heartbeats combined. Monitor types include HTTP/website, keyword (checks page for specific text), ping, port, and DNS. Heartbeats are the inverse — your app pings Better Stack on a schedule, and if a ping stops arriving, an alert fires. Heartbeats are ideal for cron jobs, queue workers, and background tasks that can’t be polled externally.

The 10-monitor math: A typical indie SaaS uses monitors like this — 1 for the marketing site, 1 for the app login flow, 1 for the API health endpoint, 1 for the database (via a heartbeat), 1 for a cron job (heartbeat), 1 for the billing webhook, and so on. You’ll burn through 10 quickly if you monitor every microservice. Pick the critical user-facing paths, not internal plumbing.

3-minute check interval

Free checks run every 3 minutes from multiple regions. That means worst-case detection latency is ~3 minutes, and a brief blip (under ~2 consecutive failures) may not trigger an alert. For most small sites this is fine; for payment-critical flows you’ll want the 1-minute interval that starts on the Freelancer plan ($29/mo).

Status page with custom domain (free)

This is the standout. You get one status page that you can host on status.yourdomain.com. It supports dark mode, your branding, and interactive uptime charts. Setup requires adding a CNAME record with your DNS provider — about 5 minutes of work. G2 reviewers repeatedly call out that custom-domain status pages are “reserved for paid plans” by competitors, which is exactly why Better Stack’s free inclusion stands out.

Limit: Customer subscriptions (letting users sign up for email status updates) and multiple status pages are paid features. On free, your status page is informational and manually updated.

Incident management

When a monitor fails, Better Stack creates an incident. On the free tier you can acknowledge, assign, and resolve incidents, and post status updates to your status page. What you don’t get free is on-call scheduling (rotation calendars, follow-the-sun shifts) and escalation policies (multi-tier “if no one acks in 5 min, page the next person”). Those require a Responder license.

For a solo dev or a small team where everyone watches Slack, the free incident workflow is plenty. For a 24/7 on-call rotation, you’ll need to pay.

Alerts: email, Slack, and 1 phone call

Free alerts cover email and Slack, plus one phone call (a useful “wake me up” lifeline). Webhooks are also available, which lets you route alerts to Discord, Telegram, Microsoft Teams, or any custom automation. SMS and unlimited phone calls are paid.

Bundled observability (logs, metrics, errors, replays)

Even if you came for uptime, the free tier throws in:

  • 3 GB of logs with 3-day retention (via Logtail) — enough to debug an incident that just happened.
  • 40 GB of metrics — basic infrastructure/app metrics.
  • 100,000 exceptions/month — error tracking tied to session replays.
  • 5,000 session replays/month — watch what users did before an error.

These are starter allotments, but they mean Better Stack can be your first observability tool, not just your pinger.


Best Use Cases With Real Examples

Use Case 1: The Indie SaaS That Needs to Look Pro

Scenario: You’re a solo founder shipping a B2B SaaS. Customers ask “do you have a status page?” and you want to answer yes — without paying StatusPage.io $29–$79/month.

Better Stack free tier fit: Perfect. Set up 3–5 monitors (marketing site, app, API, DB heartbeat), create a branded status page on status.yourdomain.com, and route alerts to your personal Slack. When an enterprise prospect asks about reliability practices, you point them at a real status page with uptime history. The free tier handles the monitoring; you handle the product.

Real-world shape: This is the most common Better Stack free-tier story. G2 reviewers consistently cite “a cool-looking status page with custom domains on the free plan” as the reason they chose it over UptimeRobot.

Use Case 2: The Multi-Service Side Project

Scenario: You run a portfolio of small apps — a blog, a API, a Discord bot, and a scheduled data scraper.

Better Stack free tier fit: Strong, with discipline. Use the 10 monitors like a budget:

  • 2 HTTP monitors (blog + API)
  • 1 keyword monitor (verify the API returns expected JSON)
  • 3 heartbeats (Discord bot liveness, scraper cron, nightly backup job)
  • 1 DNS monitor
  • 3 monitors in reserve for the next project

Heartbeats are the secret weapon here — they’re the only way to monitor “things that aren’t a public URL” for free, and they count against the same 10.

Use Case 3: The Small Team That Wants Shared Visibility

Scenario: A 3–5 person team wants everyone to see uptime in one place and share incident awareness, without each person paying a seat fee.

Better Stack free tier fit: Good for visibility, limited for on-call. Invite teammates so everyone sees the dashboard and status page, and pipe alerts into a shared Slack channel. What you won’t get free is formal on-call rotations and escalation policies — for that you’d buy a Responder license. If your team culture is “whoever’s online handles it,” free works. If you need paged rotations, budget for paid.

Use Case 4: Cron and Background-Job Monitoring

Scenario: You have nightly batch jobs, queue workers, and backup scripts. If one silently stops, you want to know.

Better Stack free tier fit: Excellent via heartbeats. Each job pings a unique heartbeat URL at the end of its run. If the ping doesn’t arrive within the expected window, Better Stack fires an alert. This catches the “cron died and nobody noticed for a week” failure mode that pure URL monitors miss entirely — and it’s free.


Step-by-Step Setup Guide

You can go from signup to a working monitor + branded status page in under 15 minutes.

Step 1: Create your account

  1. Go to betterstack.com and click Get started — it’s free.
  2. Sign up with Google, GitHub, or email. No credit card required.
  3. You’ll land in the Better Stack dashboard. The Uptime section is your starting point.

Step 2: Add your first uptime monitor

  1. In the left sidebar, go to Uptime → Monitors → Create monitor.
  2. Choose a monitor type:
    • Website (HTTP) — the default; checks a URL returns 2xx/3xx.
    • Keyword — checks the page contains (or avoids) specific text (e.g., confirm “Out of stock” isn’t present).
    • Ping — ICMP reachability.
    • Port — checks a TCP port is open.
    • DNS — validates DNS records.
    • Heartbeat — for internal jobs that ping Better Stack.
  3. Enter your URL (e.g., https://yourapp.com/health).
  4. Set the check interval to 3 minutes (the free-tier default).
  5. Pick the check locations (multiple regions are available even on free).
  6. Optionally set request headers, expected status code, or timeout for API checks.
  7. Click Create monitor. Within ~3 minutes you’ll see your first check result.

Step 3: Configure alert channels

  1. Go to Uptime → Integrations (or Alerting).
  2. Connect Slack — authorize the Better Stack app to your workspace and pick a channel for alerts.
  3. Confirm your email is set as a contact (done during signup).
  4. (Optional) Add a Webhook to route alerts to Discord, Telegram, Microsoft Teams, or a custom function. Discord/Telegram typically need a small adapter or a service like a Discord webhook URL.
  5. On the free tier you also get one phone call alert — configure your phone number and assign it to a high-priority monitor.

Step 4: Create a status page on your own domain

  1. Go to Status Pages → Create status page.
  2. Name it (e.g., “Acme Status”) and add the monitors/components you want to display.
  3. Publish it — you’ll get a default *.betteruptime.com URL immediately.
  4. To use your own domain: open the status page → Settings → Custom domain → enter status.yourdomain.comSave.
  5. At your DNS provider, create a CNAME record:
    status.yourdomain.com   CNAME   <the-hostname-better-stack-gives-you>.betteruptime.com
  6. Once DNS propagates (usually minutes), your status page is live at your custom domain with your branding, dark mode, and uptime charts.

Step 5: Wire up a heartbeat (for cron jobs)

  1. Go to Uptime → Heartbeats → Create heartbeat.
  2. Name it (e.g., “Nightly backup”) and set the expected period (e.g., 24h) and grace period (e.g., 1h).
  3. Copy the heartbeat URL (e.g., https://uptime.betterstack.com/heartbeat/xxxx).
  4. Add a curl call to the end of your cron job or script:
    curl --request GET https://uptime.betterstack.com/heartbeat/xxxx
  5. If the heartbeat doesn’t arrive within period + grace, Better Stack alerts you.

Step 6: Test an incident end-to-end

  1. Temporarily point a monitor at a URL you control and take it offline (or use https://example.com/force-error).
  2. Wait ~3 minutes for two consecutive failures — an incident is created and alerts fire to Slack/email.
  3. In the dashboard, Acknowledge the incident, then Resolve it once you’ve “fixed” it.
  4. Optionally post a status update to your status page from the incident view.

This confirms your whole alert → incident → status-page loop works before a real outage.


Comparison to Alternatives

Better Stack vs. UptimeRobot

Dimension Better Stack (Free) UptimeRobot (Free, 2026)
Monitors 10 (incl. heartbeats) 50
Check interval 3 minutes 5 minutes
Status page 1, with custom domain 1 (custom domain is paid)
Incident management ✅ Basic ❌ Alerts only
Alert channels Email, Slack, 1 phone call, webhook Email (Slack/SMS paid)
Logs / metrics / errors ✅ Bundled (small allotments) ❌ Uptime only
Commercial use ✅ Allowed Blocked on free in 2026
Heartbeats / cron monitoring ✅ Yes ❌ (cron jobs are paid)
First paid plan Freelancer $29/mo (20 monitors, 1-min) Solo ~$8/mo (60s checks + SSL)

When to choose UptimeRobot: You want the most monitors for the least effort and you’re monitoring non-commercial or hobby projects. 50 monitors beats 10, and the setup is dead simple. But note the 2026 commercial-use restriction — if your project makes money, UptimeRobot’s free tier is no longer compliant.

When to choose Better Stack: You need a status page (especially on your own domain), incident management, heartbeats for cron jobs, or you’re running a commercial project. Better Stack wins on features per dollar, UptimeRobot wins on raw monitor count.

Better Stack vs. Checkly

Dimension Better Stack (Free) Checkly (Hobby, Free)
Monitors 10 uptime + heartbeats 10 uptime monitors
Browser checks 1,000 browser check runs/month (Playwright)
API checks HTTP/keyword/port 10,000 API check runs/month
Check locations Multiple regions 6 locations
Status page 1, custom domain free Separate product (paid)
Incident management ✅ Basic Limited
Monitoring as code Terraform available First-class (Terraform, CLI, Playwright)
Logs / metrics / errors ✅ Bundled ❌ Focused on checks

When to choose Checkly: You’re an engineering team that wants Playwright-based browser checks (log in, click through a flow, assert the cart works) and monitoring-as-code checked into your repo. Checkly’s free tier is unmatched for synthetic behavioral testing.

When to choose Better Stack: You want a status page, incident management, and a broader observability bundle — not just synthetic checks. Better Stack is the better “uptime + status page + ops” tool; Checkly is the better “deep synthetic testing” tool. Many teams run both.

Quick decision guide

  • Just need to know if my site is down (hobby): UptimeRobot.
  • Need a status page + incident management for a real product: Better Stack.
  • Need to test login/checkout flows with real browsers: Checkly.
  • Monitoring cron jobs and background workers: Better Stack (heartbeats) or UptimeRobot (paid cron checks).

Tips to Maximize the Free Tier

1. Use the status page custom domain — it’s your biggest free win

A branded status.yourdomain.com page is the single highest-value free feature. Set it up early. It costs you 5 minutes of DNS work and instantly upgrades your product’s perceived reliability. Most competitors charge $20–$80/month for this.

2. Treat your 10 monitors like a budget

Don’t waste monitors on every internal endpoint. Prioritize user-facing paths: the marketing site, the app shell, the login flow, the primary API health endpoint, and the checkout/billing webhook. Use the remaining slots for heartbeats on critical background jobs.

3. Lean on heartbeats for anything that isn’t a URL

Cron jobs, queue workers, backups, and schedulers can’t be polled — but they can ping Better Stack. Each heartbeat counts as one of your 10, but it’s the only free way to monitor “did my nightly job actually run.”

4. Route alerts with webhooks to extend free channels

The free tier includes webhooks. Use them to fan alerts out to Discord, Telegram, Microsoft Teams, or a custom PagerDuty-style integration — channels that aren’t natively free. A single webhook into a relay (or a no-cost automation tool) multiplies your alerting reach.

5. Use the bundled logs and error tracking for incident triage

When an uptime alert fires, the free 3 GB of logs (3-day retention) and 100K exceptions/month let you pivot straight into “what broke?” Keep your log volume under 3 GB by shipping only warnings+ from noisy services. The 3-day window means check logs during an incident, not a week later.

6. Monitor with multiple regions for free

Even on the free tier, checks run from multiple regions. Configure monitors to require failures from more than one region before alerting — this dramatically cuts false positives from transient network blips without costing anything.

7. Keep the one phone call for your highest-stakes monitor

You get exactly one phone call alert on free. Reserve it for your most critical monitor (e.g., the production app or the payment flow) and use Slack/email for the rest. Don’t burn the phone call on a low-priority blog monitor.

8. Pair with a second free monitor for coverage

If 10 monitors isn’t enough, run Better Stack for your critical paths (status page + incident management) and a second free tool like UptimeRobot (for non-commercial projects) or a self-hosted Uptime Kuma for the long tail. Better Stack becomes the “customer-facing” layer; the other tool covers volume.

9. Know exactly when to upgrade

You should consider Better Stack’s paid Freelancer plan ($29/mo) only when you:

  • Need more than 10 monitors or 1-minute checks on customer-critical services.
  • Need on-call scheduling and escalation policies for a real rotation.
  • Need status page subscriber notifications so customers get email updates.

For solo founders and small teams in their first year, the free tier is usually enough.


The Bottom Line

Better Stack’s 2026 free tier is the best $0 option when “is my site up?” isn’t enough and you also want a branded status page, incident management, and a starter observability stack. The 10-monitor and 3-minute-check limits keep it firmly in small-team territory, and full on-call scheduling is gated behind paid plans — but for indie SaaS, side projects, and small teams that want to look professional to customers, it consistently overdelivers.

With UptimeRobot’s free tier now restricting commercial use, Better Stack is also one of the few free monitors you can run on a paying product without bending the terms. Set it up, claim your custom-domain status page, and you’ve got a credible reliability story for $0/month.

When to start paying: When you need more than 10 monitors, sub-3-minute detection on critical flows, or real on-call rotations. Until then, the free tier does the job.

ToolBrain Score: 8.0 / 10


Sources:

  1. Better Stack — Uptime Monitoring — Official product and feature information
  2. Better Stack Pricing — Current free tier limits and paid plans
  3. Free Status Page — Better Stack — Custom-domain status page details
  4. Better Stack Custom Subdomain Docs — Status page CNAME setup
  5. Better Stack Reviews — G2 — 328 verified user reviews (UI, setup, free-tier praise)
  6. Better Stack Pricing Overview — G2 — Free-tier feature breakdown and reviewer sentiment
  7. Better Stack Reviews — Capterra — Verified user feedback
  8. Better Stack Free Plan 2026 — Costbench — Itemized free-tier limits
  9. Better Stack Pricing 2026 — API Status Check — Plan comparison (Freelancer $29/mo, free 10 monitors / 3-min)
  10. Better Stack vs UptimeRobot — Better Stack Community — Head-to-head comparison
  11. Better Stack vs Checkly — Better Stack Community — Head-to-head comparison
  12. UptimeRobot Free Tier 2026 — SaaSPricingPulse — UptimeRobot 50-monitor / 5-min limits and commercial-use restriction
  13. UptimeRobot Alternatives 2026 — UptimeSignal — 2026 commercial-use restriction details
  14. Checkly Free Tier 2026 — AgentDeals — Checkly Hobby tier limits (10 monitors, 1K browser, 10K API checks)

References

[1] betterstack.com [2] Better Stack Pricing [3] Free Status Page — Better Stack [4] Better Stack Custom Subdomain Docs [5] Better Stack Reviews — G2 [6] Better Stack Pricing Overview — G2 [7] Better Stack Reviews — Capterra [8] Better Stack Free Plan 2026 — Costbench [9] Better Stack Pricing 2026 — API Status Check [10] Better Stack vs UptimeRobot — Better Stack Community [11] Better Stack vs Checkly — Better Stack Community [12] UptimeRobot Free Tier 2026 — SaaSPricingPulse