Is the free plan really free, or a trial?

Free is a plan, not a trial. One monitor, one public status page, checks every 5 minutes, 30 days of history, and unlimited subscribers. It stays free for as long as you use it.

We are two people. Do we need a status page yet?

The best time to publish one is before the first outage, because that is when customers go looking for it. It also gives you a place to announce maintenance and a history that shows you take uptime seriously when you are talking to bigger customers.

How long does setup take?

About four minutes for a monitor and a published page. A custom domain is one CNAME record and takes as long as your DNS provider takes to update.

What happens if we can't pay one month?

Your published page stays online no matter what. After a grace period you lose access to paid features until the payment goes through, but your customers never see a page go dark because of a billing problem.

Can we move to another tool later?

Yes. Subscribers can be exported, the API gives you everything else, and there is no contract. We would rather you stayed because it works.

For startups

A status page before anyone asks for one

You will have an outage before you have an ops team. Status Bee gives you the page, the monitors and the alerts from day one, free for one monitor, so the first bad afternoon looks like something you planned for.

Start free

Free for one monitor. No card needed.

Launch morningDay 1

09:02
Added monitor api.fernpost.com, HTTPS, every 60 s
09:04
Published status.fernpost.com from the SaaS template
09:06
Pointed the CNAME. HTTPS issued automatically.
09:11
Connected Slack #alerts
09:31
First subscriber (a customer found the link in your footer)
First incident. Not yet, and that is the idea.

4 min

To a published page

To start

1 min

Checks on Starter

Per-subscriber fees

The first time it matters

A Tuesday afternoon, six weeks after launch.

14:02

The deploy takes the API down

The monitor fails twice. A rule drafts the incident from your template. You approve it from your phone in the coffee queue.

14:05

Twelve customers were about to email

They looked for a status page first, found one, and subscribed instead. Your inbox stays quiet.

14:40

Resolved, with a timeline

The write-up already exists, because the incident does. You paste the link in the customer channel and go back to shipping.

Looks like a company. Costs like a side project.

Start from the SaaS template, rename the components to the words your customers use, and publish. On Starter, put it on status.yourdomain.com with your logo. Nobody can tell it took four minutes.

One public page and one monitor, free for as long as you like
Custom domain over HTTPS from $13 a month
Subscribers are never metered, so growth does not change the bill

Fernpost statusUpdated 12s ago

All systems operational

App100%

API99.97%

30 days agoToday

Get told when something changes

Set it up once and forget it exists

Two HTTPS monitors and an SSL monitor cover most early-stage products. Link them to the page's components, connect Slack, and the page keeps itself honest while you are busy with everything else.

Incidents can open themselves from a failing check
Certificate reminders at 30, 14, 7 and 1 days, so the renewal job failing quietly is not a surprise
Add TCP, ping, DNS and heartbeat checks when the stack grows

Monitors3 up