Back to pricing
Which one are you?

Don’t pick a plan.
Find yourself in one.

Each plan is written around a person, not a feature list. Read the signals that you’ve outgrown the step below — when one sounds like you, that’s your plan. The upgrades show up only as answers to a pain you already feel.

Start here · Free · $0

You’re already covered.

Fifty monitors, five-minute checks, SSL tracking, a status page, the real-time Live view, and an API key with MCP access — free forever, no card, no clock. That is a real setup, not a trial. You’ll know you’ve crossed the starting line when you need to see faster, or when someone else starts reading the page you built. That’s where the three steps below begin.

01

Indie

Everything in Free, plus —
This is you if

Solo makers and indie hackers whose work is now something other people see

For the solo maker, indie hacker, or freelancer running things that people actually depend on. Free already gives you fifty monitors and an API key, so this is not about running out of room — it is about resolution and presentation. You want to know in a minute rather than five, and when a client or a user lands on your status page, you want it to carry your name rather than ours.

You have outgrown Free when

Any one of these sounds familiar? That’s the signal.

  • Five-minute checks are too slow — a short blip can start and finish before your monitor ever looks.
  • Someone other than you is reading your status page, and it still shows exit1 branding.
  • Sixty days of history is starting to fall short of the question you are being asked.
  • You caught an outage from a customer message instead of an alert.

When five minutes is long enough to miss it.

1min

between checks

five times the resolution of Free

On Free, a check runs every five minutes — which means a two-minute outage can begin and end without your monitor ever noticing. Indie drops that to one minute, so a short blip surfaces as a real event instead of vanishing between polls. It also hands you the status page builder: your logo, your colours, your layout, with the exit1.dev badge gone. The page a client opens stops looking borrowed.

How Indie fixes it

Each upgrade below is the answer to a pain above — never a spec for its own sake.

The pain · Outages that vanish between checks
1-minute checks — five times the resolution of Free, enough to catch the short ones.
The pain · A status page that looks borrowed
The full status page builder on your page — your logo, colours and layout, with the exit1.dev badge removed.
The pain · Fifty monitors starting to feel like a ceiling
100 monitors, and DNS record monitoring on top of the protocols Free already covers.
The pain · History that runs out mid-question
90 days of retention, 3 API keys instead of 1, and 3 webhook integrations alongside email.
In one line

Minute-resolution checks and a status page with your name on it, for four dollars a month.

This is me — start with Indie
02

Nano

Everything in Indie, plus —
This is you if

Small teams running production, and freelancers with a real roster of clients

For the small team running something in production, and the freelancer whose client list has become a fleet. Nano is where monitoring stops being a personal habit and starts being infrastructure: half-minute resolution, a page per client, domains watched alongside uptime, and a full year of history to answer questions from last quarter.

You have outgrown Indie when

Any one of these sounds familiar? That’s the signal.

  • A minute is still long enough to miss the failures you care about.
  • One status page is not enough — different clients or services need their own.
  • You once renewed a domain late, or nearly did, and the registrar’s reminder got lost with everything else in your inbox.
  • You ship planned work and want to stop the alerts firing during a deploy window.
  • Your users are concentrated in one region and you want checks to run from there, not wherever they land.

When monitoring becomes infrastructure, not a habit.

30sec

between checks, across up to 250 monitors

twice the resolution of Indie, with region choice

At some point the questions change. Not “is it up?” but “which client is affected, when does that domain expire, and can you show me last quarter?” Nano answers all three: 250 monitors at thirty-second checks, five branded status pages so each client gets their own, domain expiry tracked next to uptime, maintenance windows that keep deploys from paging anyone, and a full year of retained history. It also lets you pin checks to the US, EU, or Asia rather than accepting the default shard.

How Nano fixes it

Each upgrade below is the answer to a pain above — never a spec for its own sake.

The pain · A minute is still too coarse
30-second checks across up to 250 monitors.
The pain · One page for many clients
Up to 5 branded status pages — one per client, each with their own look.
The pain · A domain that quietly lapses
Domain Intelligence tracks WHOIS/DNS expiry alongside your uptime and warns you before a domain runs out — the renewal stops depending on memory.
The pain · Deploys that page the whole channel
Maintenance mode — instant, scheduled, or recurring windows that suppress alerts during planned work.
The pain · Checks running from the wrong side of the world
Region choice — pin checks to the US, EU, or Asia. Plus 10 API keys, 10 webhooks, and a full year of retention.
In one line

Half-minute resolution across 250 monitors, a branded page per client, domains watched alongside uptime, and a year of history behind it all.

This is me — start with Nano
03

Pro

Where most teams settle
Everything in Nano, plus —
This is you if

Teams with paying users, someone on call, and a fleet to cover

For product teams, startups, SaaS companies, agencies, and MSPs — anywhere the site going down means paying users notice first, and where uptime is part of what you deliver. Monitoring is no longer one person’s browser tab: a few people share responsibility, someone is on call, and a failure at 3am has to reach a human.

You have outgrown Nano when

Any one of these sounds familiar? That’s the signal.

  • An email alert isn’t enough anymore — you need a text or a Slack ping to reach whoever is on call.
  • Thirty seconds is still slower than your error budget tolerates.
  • You’re hand-rolling webhook glue to get alerts into Slack, Discord, or Teams, when those channels could just be native.
  • A client or auditor has asked you to prove uptime from more than a year ago.
  • Your fleet has outgrown 250 monitors, or five status pages.

When an outage has to wake someone, not just fill an inbox.

15sec

between checks, across up to 1,000 monitors

the fastest interval exit1 runs, at the highest limits

On the smaller plans, a failed check at 3am is an email read at 9am — and your incident channel hears nothing. On Pro, the same failure is a text on the on-call phone and a ping in your Slack channel as soon as the next fifteen-second check confirms it, so someone is on it before the support queue moves. Afterward you pull the full timeline from three years of retained logs to write the postmortem, and your REST keys and MCP connection mean the next question — “what broke last night?” — gets answered straight from your editor.

How Pro fixes it

Each upgrade below is the answer to a pain above — never a spec for its own sake.

The pain · A 3am alert no one sees until morning
SMS alerts (25/hr, 50/mo) put it on the on-call phone, plus native Slack, Discord, and Microsoft Teams.
The pain · Thirty seconds is still too slow
15-second checks — the fastest interval exit1 runs — across up to 1,000 monitors.
The pain · Proof of uptime that expires before the contract
3-year log retention, plus CSV export for analysis outside the app.
The pain · One branded page per client, past five
50 custom-branded status pages — one per client, their look, no exit1 badge.
The pain · Running the whole fleet across a team
100 API keys to script per-client setup, 100 webhooks, per-log comments, and extra email recipients per check and per folder. Named team members and roles are on the roadmap, not shipped yet.
In one line

Fifteen-second checks across a thousand monitors, alerts that reach the person on call by text and in your team channel, and three years of retention so your proof of uptime outlives the client contract.

This is me — start with Pro
Found yourself?

Start where you are.
Move up when it stops fitting.

Every plan builds on the one below it. Cancel anytime, change tiers whenever the moment comes.

Start freeCompare all plans