The bill grows every time someone subscribes.
Atlassian Statuspage meters the thing you most want to be true — that a lot of people are watching. StatusOwl is priced per status page, and the page opens its own incidents from its own checks. Here is the honest version of what you gain and what you give up.
Free forever on one page — with your own domain and SSL included.
Subscribers are the meter, and the meter only goes one way.
Nobody shops for a status page because the incident timeline is the wrong shade of grey. They shop because the renewal quote arrived and the number moved for a reason that has nothing to do with how much the product is used.
- Hobby~$29/mo
- Startup~$99/mo
- Business~$399/mo
- Enterprise~$1,499/mo
Roughly where the ladder sat at the time of writing. Each step up is largely a bigger subscriber allowance — the published ladder reaches around $399/mo by the time you are notifying 5,000 people. Prices change: check Atlassian’s pricing page before you decide anything.
- Free1 status page$0/mo
- Starter3 status pages$19/mo
- Growth10 status pages$49/mo
- ScaleUnlimited status pages$149/mo
The only axis is how many pages you run. Ten thousand people can read your page during an outage and the invoice does not move. Every limit, plan by plan.
Part of the gap is that StatusOwl does not send anything to your readers. There is no subscribe form, no subscriber list and no notification email. We are not undercutting Atlassian on postage; we have not built the post office yet. If the subscriber list is what you are paying for, that money is buying something real and you should keep paying it. Where subscribers sit on the roadmap.
A page that has already updated itself by the time you log in.
The reason to move is not that it costs less. It is that the monitoring and the page are the same product, so the page is correct before anyone writes anything.
Incidents open themselves
Three consecutive failed checks on an attached monitor opens an incident at your configured impact, seeds an automatically-detected first update and raises the banner. The first successful check posts a recovery update and resolves it.
Read moreOne axis on the invoice
Pages, not people. Free covers one page; Scale removes the page limit entirely at $149/mo. Audience size never appears on the bill.
Read moreYour domain, on the free plan
status.yourcompany.com with automatic SSL is included on every plan, including Free. Staged DNS instructions, re-checked every 10 seconds, with nothing to install or renew.
Read more90 days of real check data
A daily bar per service with the exact uptime percentage, average response time and check count behind each one — drawn from the checks that decide what the page says, not from a number someone typed in.
Read moreMaintenance and incidents, unmetered
Unlimited incidents and maintenance windows on every plan, each with its own append-only update timeline and permanent public detail page.
Read moreAudit log on every plan
Every incident, maintenance window and status-page change is recorded, including on Free. Access is checked against your organisation membership and role before every read and write.
Read moreOne clarification, because the wording matters: StatusOwl does send scheduled uptime reports by email — daily, weekly or monthly, with uptime, average and p95 latency. Those go to addresses you choose. They are a report for your team, not a notification for your customers.
There is no import tool. You will be typing.
Every vendor's switching page says migration is painless. This one is a couple of hours of retyping, one DNS change, and a permanent loss of your published incident history. Better you know that now.
Create the org and claim a subdomain
You get {subdomain}.statusowl.app immediately — format-validated, globally unique. The page is live before you touch DNS, so you can build it in the open without anyone finding it.
Recreate each component as a monitor
This is the manual part. Every component on your Statuspage becomes an HTTP, ping or TCP monitor here — method, expected status codes, headers, timeout, follow-redirects. Attach the monitors to the page and the page starts driving itself.
Run both pages for a week
Leave the old page up. StatusOwl only knows what it has checked, so the uptime bars fill in from the day you start. A week side by side tells you whether the automatic incidents fire when you expect.
Move the domain
Point status.yourcompany.com at status-pages.statusowl.app. The dashboard walks the ownership TXT, the CNAME and the ACME TXT one record at a time, re-checking every 10 seconds and showing Cloudflare's own error text if a record is wrong. The certificate issues and renews on its own.
What does not come across
- Past incidents and their update timelines
- Every incident you have written on Statuspage stays on Statuspage. There is no import, so a public history you have built over years does not follow you. If that record matters to your customers, export it and keep the old page reachable at an archive URL.
- Historical uptime figures
- The 90-day bars start empty and fill in one day at a time from your first check. For the first three months your page will show less history than the one you left.
- Your subscriber list
- There is nowhere to put it. StatusOwl has no subscriber system at all — see below, because this is the thing most likely to make switching a bad idea for you.
- Component groups, templates and custom CSS
- Grouped components and incident templates do not exist here. The renderer accepts custom CSS but there is no editor to set it, so treat your current styling as something you will rebuild with logo, colours and theme instead.
The grey bars are honest, not broken. A day with no checks reads as no data, and it stays that way. Four weeks in, the strip looks like this.
You should stay on Statuspage if any of these are true.
A status page company that oversells is a contradiction. Read this list before the pricing one — if a single line lands, the renewal is the cheaper option.
You need to notify subscribers today
This is the big one. Statuspage's subscriber system — email, SMS, webhook, RSS — is mature and it is the reason most teams pay for it. StatusOwl has none of it. Publishing an incident here updates the page and sends nothing to anyone. If people currently find out about your outages because Statuspage emailed them, switching makes your incident communication worse.
Your team is paged by your status tooling
A failing HTTP, ping or TCP check in StatusOwl opens an incident on the page and notifies nobody. Our six notification channels are real, but the only thing wired to fire them today is a server-metric alert rule from the Watch Owl agent.
You live inside Atlassian
Jira, Opsgenie and the rest of the ecosystem plug into Statuspage properly. StatusOwl integrates with Slack, Discord, Microsoft Teams, ntfy, email and signed webhooks — and none of that is a substitute for an incident that already exists in your Atlassian workflow.
You need audience-specific pages or component groups
Showing different components to different customers, and grouping components under headings, are both Statuspage features with no equivalent here. StatusOwl gives you separate pages instead, which is a blunter tool.
You need SAML, or a password on an internal page
Sign-in is email and password. A private page here returns a 404 to anyone without the link — there is no password prompt and no SSO gate in front of it.
You need to correct an incident after posting it
Incidents are immutable once created. Title, impact, start time and affected services cannot be changed; you can post another update or delete the whole incident. Statuspage lets you edit.
The five things people ask before they move.
Short answers, including the ones that talk you out of it.
- Is there an importer for Statuspage components and incidents?
- No. There is no import tool of any kind. Moving means recreating each component as a monitor by hand and pointing your DNS at the new page. Past incidents, their update timelines and your historical uptime figures do not come across. An importer is on the roadmap under 'Exploring', which means it has not been started.
- Will my subscribers be notified when I publish an incident on StatusOwl?
- No. StatusOwl has no subscriber system — no subscribe form on the page, no subscriber list in the dashboard, no email, SMS or RSS notification. Publishing an incident updates the page and nothing else. It is being built, and until it ships this is the strongest reason to stay on Statuspage.
- How is StatusOwl priced if not per subscriber?
- Per status page. The ladder runs from $0 on the free plan to $149 a month with no page limit, and every plan in between is priced on how many pages you run. Nothing on the bill moves when more people read your page.
- Can I keep my custom domain?
- Yes. Point the same hostname at status-pages.statusowl.app with a CNAME. Custom domains with automatic SSL are included on every plan, including Free. Expect a short window where the old page and the new one are both live while DNS propagates.
- What does StatusOwl do that Statuspage does not?
- It runs the checks itself. Three consecutive failed checks on a monitor attached to your page opens an incident automatically, seeds a first update and puts the banner up, then posts a recovery update and resolves on the first successful check. On Statuspage the monitoring is somebody else's job and a human still has to publish.
Build the new page before the renewal lands.
Free forever on one page, with your own domain and automatic SSL. Run it next to the old one for a week and decide with real data.