Statuspage pricing runs from $0 to $1,499 a month on Atlassian's public plans, but the plan name is not what decides your bill. Subscribers are. Public pages cost $29 (Hobby, 250 subscribers), $99 (Startup, 1,000), $399 (Business, 5,000) and $1,499 (Enterprise, 25,000) a month, and every one of those caps is a cliff rather than a slope. Crossing from 250 to 251 subscribers costs $840 a year. Crossing from 1,000 to 1,001 costs $3,600 a year. Private internal pages are a separate product with its own ladder, starting at $79 a month for 50 authenticated subscribers, which is 13.6 times more per subscriber than the public entry plan.
These are the list prices published on Atlassian's own Statuspage pricing page, in US dollars. What follows is the full rate card for both page types, the per subscriber arithmetic Atlassian does not print, and the two upgrade triggers that catch teams out most often.
The Atlassian Statuspage public page rate card for 2026
Public pages are the ones your customers see. Every paid tier includes unlimited notifications and free SSL, and the core feature set (incidents, components, scheduled maintenances, templates, page analytics, REST API access) is the same on all of them. What changes between tiers is scale and a small number of gated features.
| Plan | Per month | Per year | Subscribers | Team members | Cost per subscriber | Notification types |
|---|---|---|---|---|---|---|
| Free | $0 | $0 | 100 | 2 | n/a | Email, Slack, Teams |
| Hobby | $29 | $348 | 250 | 5 | $0.1160 | Email, Slack, Teams |
| Startup | $99 | $1,188 | 1,000 | 10 | $0.0990 | Email, SMS, webhook |
| Business | $399 | $4,788 | 5,000 | 25 | $0.0798 | Email, SMS, webhook |
| Enterprise | $1,499 | $17,988 | 25,000 | 50 | $0.0600 | Email, SMS, webhook |
Atlassian publishes no discounted annual rate for these plans, so every per year figure above is simply the monthly list price times twelve. There is no prepay saving to find.
The custom domain, the thing that makes the page read as yours rather than as something.statuspage.io, first appears on Hobby at $29. The free plan does not include it. That single line is why most teams that get past a proof of concept end up paying something.
The three subscriber cliffs
Cost per subscriber falls as you go up, from $0.1160 on Hobby to $0.0600 on Enterprise, which looks like a normal volume discount and is one. The problem is that you do not buy subscribers, you buy tiers, so the discount only ever arrives as a step. Here is what one additional subscriber costs at each boundary.
| The subscriber that triggers it | Forced move | Extra per month | Extra per year | Increase |
|---|---|---|---|---|
| Subscriber 101 | Free to Hobby | $29 | $348 | from free |
| Subscriber 251 | Hobby to Startup | $70 | $840 | 241% |
| Subscriber 1,001 | Startup to Business | $300 | $3,600 | 303% |
| Subscriber 5,001 | Business to Enterprise | $1,100 | $13,200 | 276% |
Every one of those jumps is somewhere between 241% and 303%. There is no intermediate step, no overage rate, and no way to buy 1,200 subscribers. This matters more than it looks, because subscriber counts are the one number in your monitoring stack you do not control. Customers subscribe to your status page after an incident. A bad week can push you across a boundary, and the boundary stays crossed.
If your subscriber count is anywhere near 250 or 1,000, that is worth a calendar reminder rather than a surprise renewal. It is also worth knowing that Atlassian's yearly credit card billing is not self serve: the FAQ states the setup is manual and requires a signed order form, so a finance team expecting to prepay online will need to contact support first.
Private pages cost 13.6 times more per subscriber
Private pages are for telling your own employees that an internal tool is down. Atlassian prices them as an entirely separate ladder, and the per head economics are nothing like the public one.
| Private plan | Per month | Per year | Authenticated subscribers | Team members | Cost per subscriber |
|---|---|---|---|---|---|
| Starter | $79 | $948 | 50 | 5 | $1.5800 |
| Growth | $249 | $2,988 | 300 | 15 | $0.8300 |
| Corporate | $599 | $7,188 | 1,000 | 35 | $0.5990 |
| Enterprise | $1,499 | $17,988 | 5,000 | 50 | $0.2998 |
Compare the entry tiers directly. Public Hobby is $29 for 250 subscribers, or $0.1160 each. Private Starter is $79 for 50 authenticated subscribers, or $1.5800 each. That is 13.6 times more per subscriber to tell your own staff what you would tell the public for a tenth of the price.
The comparison that makes the pattern unmistakable is at the top, where both ladders charge the identical $1,499 a month. Public Enterprise gives you 25,000 subscribers at $0.0600 each. Private Enterprise gives you 5,000 at $0.2998 each. Same price, five times fewer people, on the same vendor's rate card. Atlassian's own guidance is that companies tend to want a private page around the 50 employee mark, which is exactly where the $79 entry tier runs out.
The $70 jump to send an SMS
Here is the upgrade trigger that has nothing to do with headcount. Hobby, at $29, sends email notifications only. Slack and Microsoft Teams are included, but SMS and webhooks are not. To send a single text message to a single subscriber you have to move to Startup at $99.
That is $70 more a month, $840 a year, a 241% increase, for a notification channel. And unlike the subscriber cliffs it is not a scale problem you can defer: either your incident communication plan involves SMS or it does not, and you find out which on day one. Worth checking before you standardize on Hobby because the monthly figure looked small.
There is a second cost that only appears in the FAQ rather than the pricing grid. SSO through Atlassian Guard is included at no extra charge for Statuspage team members on Startup, Business and Enterprise. But Atlassian is explicit that if you have users on other Atlassian products, such as Jira, who are not part of your Statuspage plan, those users will be charged for Atlassian Guard. In a shop that already runs Jira, turning on SSO for the status page can surface a licensing line item that has nothing to do with the status page.
Audience-specific pages
The third page type shows different component statuses to different customer groups, which is what you need when one tenant is affected and the rest are fine. It starts at $300 a month, or $3,600 a year, for 25 team members, 10 groups, 500 users and 30 metrics. At 500 users that is $0.60 per user, so it sits between the public and private rates, and it carries the Manage API and full custom CSS, HTML and JS.
It is priced as a starting point rather than a fixed tier, so treat $300 as a floor and expect a quote if your group or user counts are higher.
What none of these plans include
A status page publishes an incident. It does not find one. Statuspage has no checks, no probes and no synthetic monitoring at any tier, so every plan above assumes something else already told you that you are down and that a human then went and updated the page. That second subscription is a real budget line and is covered in more depth in our comparison of status page pricing across vendors, which sets Statuspage against Instatus, Better Stack, Hyperping and PagerDuty.
It is also worth pricing the pair together rather than separately. Some status page software bundles the monitoring that drives the page, which removes both the second invoice and the manual step where somebody has to remember to flip a component to degraded at 3am. Our own plans include branded status pages alongside the checks that update them, flat from $49 a month, with 30-second checks from $59.
One more thing to weigh if you are picking an Atlassian product for the long term. Atlassian closed Opsgenie to new customers in June 2025 and shuts it down entirely on April 5, 2027, and teams caught by that are now running a migration nobody planned. Nothing suggests Statuspage is heading the same way, and it remains actively sold, but what happened to Opsgenie pricing is a reasonable input into how much of your incident process you want to build on one vendor's roadmap.
For teams in regulated industries the calculation shifts again, because outage communication stops being a courtesy and becomes something with a deadline attached. If a customer contract or a regulator specifies notification within a fixed window, that duty belongs in the same register as your other deadline-bound obligations rather than in one engineer's memory of what the runbook said. The status page is where you discharge it, but it is not where you track it.
Is Atlassian Statuspage worth the money?
For a public page with under 250 subscribers, $29 a month is a fair price for a hosted, branded, custom domain status page with a REST API and a genuinely good incident workflow. Statuspage is the category default for a reason and the product is mature.
The two situations where the price stops making sense are both structural. If your subscriber list is growing through an incident-heavy period, the tier cliffs mean your status page bill can triple in a month for reasons entirely outside your control. And if your main need is internal, the private ladder is expensive enough per head that a general purpose internal comms channel plus a cheap public page often does the same job. Run your own subscriber count against the cliff table above before you commit to an annual order form.