Is Atlassian Statuspage free? What it actually costs in 2026

What the free tier actually includes

• —100 subscribers
• —25 components
• —2 team members who can log in and post updates
• —2 metrics
• —No custom domain — the page lives on a statuspage.io address
• —No SMS or webhook notifications

Where the wall is

Subscribers, and then your own domain. Notifying customers is the entire point of a status page, and 100 subscribers is a number a growing product passes quietly. The second wall is branding: a custom domain starts at Hobby, so until you pay, your outage page is visibly not yours.

After that: Hobby at $29 a month (250 subscribers, 5 team members, custom domain); Startup at $99 (1,000 subscribers, SMS and webhook notifications); Business at $399 (5,000 subscribers, custom CSS/HTML/JS, RBAC); Enterprise at $1,499 (25,000 subscribers).

Can you self-host Atlassian Statuspage? No — cloud only

No. Statuspage is Atlassian-hosted only, which is arguably the point — a status page on your own infrastructure goes down with your infrastructure. Self-hosted alternatives like Cachet and Uptime Kuma exist; run them somewhere your main stack is not.

When paying is still the right call

Stay if you are on the free tier and it covers you, which it does for a lot of small products. Stay if you are already an Atlassian shop — the Jira and Opsgenie integrations mean an incident can update the public page without anyone remembering to do it manually, and that integration is worth real money during an actual outage. Stay if you need the compliance and audit features enterprise customers ask for. And stay if your status page is contractually part of an SLA, where a self-hosted page sharing infrastructure with the service it reports on is a genuine problem.

What you are locked into

Low on data, higher on habit. Components and incident history export via the API, and rebuilding the page elsewhere is not difficult. What is genuinely awkward is the subscriber list: people signed up to hear from you at a specific address, and moving them to a new system means asking them to opt in again, which not all of them will. Custom domains ease the transition — if status.yourcompany.com already points at Statuspage, repointing it is a DNS change your customers never see.

If you would rather not pay: Uptime Kuma