UptimeHub
Statuspage plan finder

Atlassian Statuspage pricing and Statuspage cost by plan

Every Statuspage plan caps three things at once. Most people price the subscriber cap and get caught by the team member cap. Enter both, plus the features you cannot do without, and see the plan you will actually pay for.

What one more person on the team costs

6th team member +$70/mo

Hobby $29 to Startup $99

11th team member +$300/mo

Startup $99 to Business $399

26th team member +$1,100/mo

Business $399 to Enterprise $1,499

See plans and pricing

Statuspage cost calculator

Live
Must have

Plans and allowances read from Atlassian's Statuspage pricing page, in USD per page per month. Atlassian publishes no annual discount, so a year is twelve months. Every page is billed on its own plan.

How much does Atlassian Statuspage cost?

Atlassian Statuspage costs $0 to $1,499 a month for each page. Public pages are Free (100 subscribers), Hobby $29, Startup $99, Business $399 and Enterprise $1,499. Private pages for employees are a separate ladder at $79, $249, $599 and $1,499, and audience-specific pages start at $300. Every tier caps subscribers, team members and metrics at the same time, so the plan you pay for is set by whichever cap you hit first, and Statuspage does no monitoring at any price.

The subscriber cap gets the attention because it is the headline number on each plan. The team member cap is the one that surprises engineering teams. A company with 400 customers subscribed and twelve engineers on the incident rotation fits Startup on subscribers and needs Business on people, so it pays $399 a month rather than $99. Atlassian sells no extra seats on their own, so the only way past a team cap is the next plan.

The short version

Public pages
Free, $29, $99, $399, $1,499 a month
Private pages
$79, $249, $599, $1,499 a month
Audience-specific pages
From $300 a month
Billing unit
Per page, each on its own plan
Annual discount
None published
Uptime monitoring
Not included on any plan

Statuspage public page plans and what each one caps

Public pages are the customer-facing kind most teams mean when they say Statuspage. The three caps move together, and the sixth column shows how many subscribers each plan allows per person on the team.

Plan Per month Subscribers Team members Metrics Subscribers per team member What it adds
Free $0 100 2 2 50 Email, Slack and Microsoft Teams notifications, 25 components, REST API. No custom domain.
Hobby $29 250 5 5 50 Adds a custom domain and basic customization. Email is the only subscriber channel besides Slack and Teams.
Startup $99 1,000 10 10 100 Adds SMS and webhook notifications, custom CSS, and team member SSO through Atlassian Guard.
Business $399 5,000 25 25 200 Adds custom HTML and JavaScript, component subscriptions and role-based access control.
Enterprise $1,499 25,000 50 50 500 Adds yearly purchase orders and invoicing.

The seat cliff

+$1,100

The 26th team member moves a public page from Business at $399 to Enterprise at $1,499, whatever the subscriber count. That is $13,200 a year for one more login.

Which cap binds

100 to 1

Startup allows 100 subscribers per team member. If your audience is smaller than a hundred times your incident team, people, not subscribers, set your plan.

The feature floor

$99

SMS or webhook notifications start at Startup, so a team of three with 80 subscribers that needs a webhook pays $99, not $29. Component subscriptions and access roles start at $399.

Statuspage private page pricing and audience-specific pages

Private pages are for employees who sign in, usually through your identity provider. They are a separate product with their own ladder, not an option on a public plan.

Private plan Per month Readers Team Per reader
Starter $79 50 5 $1.58
Growth $249 300 15 $0.83
Corporate $599 1,000 35 $0.60
Enterprise $1,499 5,000 50 $0.30

Atlassian's own pricing page says companies usually start a private page "around the 50 employee mark". Fifty is exactly the Starter cap, so the company that fits Atlassian's description of a new private page customer is one hire away from Growth at $249.

Audience-specific tier Per month Per year
Tier 1, 500 users and 10 groups $300 $3,600
Tier 2 $500 $6,000
Tier 5 $1,100 $13,200
Tier 10 $2,100 $25,200
Tier 11 $2,200 $26,400
Tier 20 $3,100 $37,200
Tier 30 $4,100 $49,200
Tier 31 $4,150 $49,800
Tier 40 $4,600 $55,200

Audience-specific pages show different components to different customer groups. Tier 1 is $300 with 500 users, 10 groups, 25 team members and 30 metrics; each tier up to 10 adds $200, then $100 to tier 30, then $50. Atlassian does not publish how many users the higher tiers hold, so ask for the allocation before you sign.

Four billing rules that change the Statuspage total

Every page is its own bill

A public page and a private page are two plans. Ten client pages on Hobby are $290 a month, $3,480 a year, before any of them needs SMS.

A year is twelve months

No annual discount is printed. Yearly card billing needs a signed order form, so Startup is $1,188 a year and Business $4,788 either way.

No seat add-on

Some third-party summaries quote a per-seat fee. Atlassian's page lists none: team members are an allowance, and the way past it is the next plan.

Nothing watches the service

Statuspage shows what someone tells it. Detecting the outage needs a separate monitoring subscription, which belongs in the same budget line.

Notifications themselves are not metered. Atlassian states that all plans include unlimited notifications, and SSL on a custom domain is free. What the plan decides is which channels you can use: email, Slack and Microsoft Teams on every public plan, SMS and webhooks from Startup up.

Atlassian Statuspage compared with UptimeHub

The two products start from opposite ends. Statuspage is incident communication with no detection. UptimeHub is detection that publishes a branded page from the checks. Which costs less depends on what you need the page to do.

Need Atlassian Statuspage UptimeHub
Detect the outageNot included, buy a monitor separatelyChecks from 6 regions, confirmed from a second region before alerting
Page updates itselfThrough an integration you wire upYes, driven by the same checks
12 people posting updatesBusiness, $399 a monthPro, $49 a month billed yearly, unlimited team
Ten branded pages$290 a month on Hobby, more with SMSPro, unlimited pages; Business white-labels them
Subscriber notification listsYes, the core of the productAlerts go to your team channels, not a customer subscriber list
Different views per customer groupAudience-specific pages from $300Separate pages per client on Business
Jira and Atlassian ecosystemNativeWebhook, Slack, Teams, PagerDuty

Stay on Statuspage when

  • Thousands of customers subscribe to updates by email or SMS and expect to manage that subscription themselves.
  • You need audience-specific views or component subscriptions, and your incident process already lives in Jira.
  • Your team is small enough to fit the plan your subscriber count needs.

Move to UptimeHub when

  • The team cap, not the audience, is what keeps pushing your plan up.
  • You run several pages, for products or for clients, and each one is a separate Statuspage bill.
  • You pay for monitoring elsewhere and want one tool that detects the outage and shows it, from $24 a month billed yearly.

Statuspage set against eleven other vendors is in the status page pricing comparison. If you are replacing it, the Statuspage alternative with monitoring included covers the switch, and Statuspage alternatives with real prices lists who has already moved. Teams buying through Jira should read Jira Service Management status page pricing first, because the page there sits on a different plan.

Where these numbers come from, and what is deliberately not claimed

Every public and private plan, its subscriber, team member and metric allowance, the notification channels per plan, the unlimited notification policy and the manual yearly billing come from Atlassian's Statuspage pricing page. The audience-specific ladder comes from Atlassian's support article on audience-specific page pricing. That each page is paid for separately is stated in an accepted answer on Atlassian Community. We do not claim a price for extra team members, because Atlassian publishes none, nor an annual discount, component limits on paid public plans, the user allocation of audience-specific tiers above the first, or any negotiated price.

Atlassian Statuspage pricing questions

How much does Atlassian Statuspage cost?

A public Statuspage costs $0 to $1,499 a month per page: Free for 100 subscribers, Hobby $29 for 250, Startup $99 for 1,000, Business $399 for 5,000 and Enterprise $1,499 for 25,000. Private pages run $79 to $1,499 and audience-specific pages start at $300. Each page carries its own plan.

Is Atlassian Statuspage free?

There is a free public plan with 100 subscribers, 25 components, two team members, two metrics and email, Slack and Microsoft Teams notifications. It has no custom domain, so the page lives on a statuspage.io address. A third person who needs to post incidents moves you to Hobby at $29 a month.

What are team members in Statuspage?

Team members are the people who log in to create incidents, change component status and manage the page. Each plan includes a fixed number: 2, 5, 10, 25 and 50 on the public ladder. Atlassian prints no price for an extra seat, so going over the allowance means moving up a whole plan.

How much does a private status page cost on Statuspage?

Private pages, for employees who sign in, are $79 a month for 50 authenticated subscribers, $249 for 300, $599 for 1,000 and $1,499 for 5,000. At the entry tier that is $1.58 a month per reader, 13.6 times the $0.116 a Hobby public subscriber costs.

How much do audience-specific pages cost?

Audience-specific pages start at $300 a month for 500 users, 10 groups, 25 team members and 30 metrics. Each tier from 2 to 10 adds $200, tiers 11 to 30 add $100 each and tiers above 30 add $50, so tier 10 is $2,100 and tier 30 is $4,100. Atlassian does not publish the user allocation above tier 1.

Does Atlassian Statuspage offer annual billing or a yearly discount?

Annual billing exists but Atlassian publishes no discount for it. Yearly credit card billing is set up manually with a signed order form, and yearly purchase orders are listed only on Enterprise. In practice a year costs twelve months: $348 on Hobby, $1,188 on Startup, $4,788 on Business and $17,988 on Enterprise.

Is each Statuspage page billed separately?

Yes. Each page is activated and paid for on its own plan, which an accepted answer on Atlassian Community confirms directly. A company running a public page and a private page pays for both, and an agency with ten client pages on Hobby pays $290 a month.

Does Statuspage include uptime monitoring?

No. Statuspage publishes incidents and component status that you or an integration set. It does not check whether your site or API is up at any tier, so you need a separate monitoring tool to detect the outage and update the page.

Which Statuspage plan includes SMS and webhook notifications?

Startup at $99 a month is the cheapest public plan with SMS and webhook notifications; Free and Hobby send email and post to Slack and Microsoft Teams only. On private pages SMS and webhooks start at Growth, $249 a month. Atlassian does not charge per notification on any plan.

Is there a cheaper alternative to Atlassian Statuspage?

For a branded page driven by real checks, yes. UptimeHub includes a status page on every plan with the monitoring that updates it, from $24 a month billed yearly, and Pro at $49 yearly covers unlimited pages and team members. Statuspage remains stronger for subscriber notification lists and audience-specific pages.

A status page that knows when you are down

UptimeHub checks your sites, APIs and ports from six regions, confirms a failure from a second region before it alerts anyone, and flips your branded status page on your own domain from the same checks. Every plan includes a page, Pro adds unlimited pages and team members, and the price is per monitor, never per seat or per subscriber.

See plans and pricing