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 kicking the tyres.

A personal project, a side build, or a first look at exit1. Ten monitors and five-minute checks are free forever — no card, no clock. You’ll know you’ve crossed the starting line the moment someone else starts depending on what you watch. That’s where the three steps below begin.

01

Nano

Everything in Free, plus —
This is you if

Freelancers, agencies-of-one, and solo makers with a site people pay for

For the freelancer or agency-of-one whose client now opens the status page you set up — and for the solo maker whose own customers depend on the thing you built. The site stopped being a side project the moment someone other than you started counting on it. The point isn’t more dashboards; it’s that your monitoring stops looking like a hobby in front of the people paying you.

You have outgrown Free when

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

  • A client now sees your status page — and it still carries the exit1.dev badge and a status.exit1.dev/abc123 URL instead of your brand.
  • The last time you went down, a client noticed before your monitor did — five-minute checks are too slow for something people pay for.
  • Ten monitors no longer covers a real setup: the site, the API, a staging box, and a couple of client properties.
  • You once renewed a domain late, or nearly did, and the registrar’s reminder got lost with everything else in your inbox.

When someone else starts depending on your site.

2min

between checks, from the US and EU

down from 5-minute checks on Free

A client opens the status page you set up and asks why it shows status.exit1.dev/abc123 and another company’s logo. In that one question, the whole setup reads as borrowed, not built. With Nano the page is yours — your logo, your colours, arranged in the drag-and-drop builder, with the exit1.dev badge gone — and checks run every two minutes from the US and EU, so a regional outage surfaces on your monitor in about two minutes instead of waiting for a client to notice first.

How Nano fixes it

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

The pain · A status page that looks borrowed
Up to 5 status pages with your own logo and colours, built in a drag-and-drop builder, with the exit1.dev badge removed.
The pain · Hearing about downtime from a client
2-minute checks from the US and EU (down from 5), so a regional outage surfaces in about two minutes — you tell the client, not the other way round.
The pain · Outgrowing ten monitors
50 monitors — room for the site, the API, a staging box, and a few client properties.
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.
In one line

A status page that’s yours, not ours — branded, badge-free, and backed by 2-minute checks from the US and EU. Plus headroom for 50 monitors when one site becomes several.

This is me — start with Nano
02

Pro

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

Software teams with paying users and someone on call

For product teams, startups, and SaaS companies where the site going down means paying users notice first. 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, not sit in an inbox until morning.

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, and Nano sends only email and webhooks.
  • You’re hand-rolling webhook glue to get alerts into Slack, Discord, or Teams, when those channels could just be native.
  • Someone asks what broke last night, and the only answer is locked in a dashboard nobody is logged into — Nano has no API and no MCP.
  • Two-minute checks feel slow when paying users notice a gap before you do.
  • Sixty days of logs runs out right when you need history for a trend or a postmortem.

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

30sec

between checks, confirmed in seconds

down from 2-minute checks on Nano

On Nano, 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 30-second check confirms it, so someone is on it before the support queue moves. Afterward you pull the full timeline from a year 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, not from a dashboard nobody’s logged into.

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 · Detection that lags behind your users
30-second checks catch and confirm a failure in seconds, not the two minutes Nano takes.
The pain · Monitoring stranded in a dashboard
A REST API with 10 keys, plus MCP to query monitors from Claude, Cursor, and Windsurf.
The pain · History that runs out before the postmortem
365-day log retention, plus CSV export for analysis outside the app.
The pain · Outgrowing fifty monitors
500 monitors, and 25 custom-branded status pages.
In one line

When a check fails, it reaches the person on call — by text and in your team channel — instead of sitting in an inbox until morning. And a year of logs and a live API mean the postmortem answers itself.

This is me — start with Pro
03

Agency

Everything in Pro, plus —
This is you if

Agencies, MSPs & large fleets

For agencies, MSPs, and consultancies where uptime is part of what you deliver and bill for. And for in-house teams whose fleet has simply grown past a few hundred sites. At this scale the monitoring itself has become something you have to stand behind.

You have outgrown Pro when

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

  • You are bumping against 500 monitors — new client sites, APIs, and SSL certs are competing for slots, and you have started deciding what not to watch.
  • A client or auditor has asked you to prove uptime from more than a year ago, and Pro’s 365-day retention can’t reach it.
  • You are running 25 status pages and still need more — one per client, with their branding, not yours.
  • A client SLA or a postmortem has made you wish the gap between checks were tighter than 30 seconds — when you are accountable for the number, the measurement window is something you think about.

Room for the whole fleet, three years deep.

15sec

between checks, the fastest exit1 runs

down from 30-second checks on Pro

You sign your fourteenth client, go to add their sites, and find you are rationing slots against the 500 cap. A month later a renewal meeting turns into “show us last year’s uptime,” and your logs stop at 365 days. Agency clears both: 1,000 monitors so you stop choosing what to leave unwatched, and three years of history so the number is there whenever a client asks.

How Agency fixes it

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

The pain · Rationing monitors against the 500 cap
1,000 monitors — double Pro’s ceiling, real headroom to keep onboarding clients and cover every site, API, and cert without choosing what to leave unwatched.
The pain · Proof of uptime that expires before the contract
3-year log retention (up from 365 days) — history that outlives a typical client contract and any audit.
The pain · One branded page per client, past twenty-five
50 custom-branded status pages — one per client, their look, no exit1 badge.
The pain · Accountable for the number, yet capped at 30s
15-second checks (down from 30s) — the fastest interval exit1 runs.
The pain · Running the whole fleet across a team
25 API keys to script per-client setup, plus 50 webhooks, SMS doubled (50/hr, 100/mo), and 50,000 emails/mo. Named team members and roles are on the roadmap, not shipped yet.
In one line

1,000 monitors so you stop rationing what you watch, and three years of retention so your proof of uptime outlives the client contract — at the fastest 15-second checks exit1 offers.

This is me — start with Agency
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