# Atlassian Statuspage Pricing in 2026: Public, Private and Audience Pages

> Atlassian Statuspage is free for 100 subscribers, then $29 to $1,499 a month for a public page. Private pages start at $79 and audience-specific pages at $300.

Source: https://quackback.io/blog/statuspage-pricing

Published: 2026-11-19

> **Atlassian Statuspage pricing in 2026:** A public status page is free for 100 subscribers and 2 team members, then costs $29, $99, $399 or $1,499 a month as subscribers and team members grow. Private pages for employees are a separate product, from $79 to $1,499 a month. Audience-specific pages, which show each customer group its own status, start at $300 a month. SMS and webhook notifications start on the $99 Startup plan.
>
> *Pricing last verified November 2026. Vendors may change plans and pricing without notice. Check [Atlassian's Statuspage pricing page](https://www.atlassian.com/software/statuspage/pricing) for the latest figures. Quackback is our product.*

[**Atlassian Statuspage**](https://www.statuspage.io) is the best-known hosted status page. The catch is in the price list: Atlassian sells three page types, each priced on its own, and each counts a different kind of reader. Public pages count **subscribers**, private pages count **employees** and audience-specific pages count **users** and customer **groups**. Every type also caps **team members**, the people who log in to post incidents.

![A staircase of public page plans from Hobby at $29 to Enterprise at $1,499 a month, with subscriber limits rising from 250 to 25,000](/blog/statuspage-pricing/hero.webp)

## What you will actually pay

Each example is the cheapest plan that covers it, at the monthly prices on Atlassian's pricing page.

| **Your situation** | **Plan you need** | **Per month** | **Over 12 months** |
|---|---|---|---|
| Under 100 subscribers, 2 people posting incidents | Public Free | $0 | $0 |
| Early SaaS, 200 subscribers, 3 people on call | Public Hobby | $29 | $348 |
| 800 subscribers who want SMS alerts | Public Startup | $99 | $1,188 |
| 3,000 subscribers, 15 people on call | Public Business | $399 | $4,788 |
| Internal IT page for 250 employees, SMS alerts | Private Growth | $249 | $2,988 |
| Separate status for 8 customer groups, 400 users | Audience-specific | $300 | $3,600 |

Two things move the bill most. SMS and webhook alerts start at $99, so Hobby only fits if email, Slack and Teams are enough. And a team with both a customer page and a staff page pays twice: the Business and Growth rows above come to $648 a month together.

## Public page pricing

| **Plan** | **Price** | **Subscribers** | **Team members** | **What it adds** |
|---|---|---|---|---|
| **Free** | $0 | 100 | 2 | 25 components, 2 metrics, email, Slack and Teams notifications, REST API |
| **Hobby** | $29/mo | 250 | 5 | 5 metrics, basic customization, custom domain |
| **Startup** | $99/mo | 1,000 | 10 | 10 metrics, SMS and webhook notifications, custom CSS, team member SSO with Atlassian Guard |
| **Business** | $399/mo | 5,000 | 25 | 25 metrics, custom CSS, HTML and JS, component subscriptions, role-based access control |
| **Enterprise** | $1,499/mo | 25,000 | 50 | 50 metrics, yearly purchase orders and invoicing |

![Atlassian Statuspage's pricing page on 19 November 2026](/blog/statuspage-pricing/pricing-page.webp)

*Atlassian Statuspage's pricing page, captured 19 November 2026.*

**Every plan includes** incidents, components, scheduled maintenance, incident templates, page analytics, the REST API, chat and automation integrations, a status embed and free SSL.

**Notifications are unlimited.** Atlassian does not charge per message. The plan decides the channel.

**Components.** The pricing page prints a limit of 25 for Free only. If you run a large catalogue of services, check Atlassian's pricing page for the paid limits.

## Private page pricing

**Private pages** tell signed-in employees about problems with internal tools and the third-party services they depend on.

| **Plan** | **Price** | **Employees** | **Team members** | **What it adds** |
|---|---|---|---|---|
| **Starter** | $79/mo | 50 | 5 | 5 metrics, email notifications, custom CSS, incident templates, team member SSO |
| **Growth** | $249/mo | 300 | 15 | 15 metrics, SMS and webhook notifications, component subscriptions, IP allowlisting |
| **Corporate** | $599/mo | 1,000 | 35 | 35 metrics, role-based access control, yearly purchase orders for eligible purchases |
| **Enterprise** | $1,499/mo | 5,000 | 50 | 50 metrics, alerting integrations, an account representative |

The pricing page lists no free private plan.

## Audience-specific page pricing

**Audience-specific pages** show each customer group only the components it uses, and send notifications only to the groups an incident affects. That saves you from running a separate status page per customer.

They start at **$300 a month** for 25 team members, 10 groups, 500 users and 30 metrics, with SMS and webhook notifications, the Manage API and component subscriptions. Atlassian says the price per extra group and user falls as you grow, but it does not print those tiers. Past 10 groups or 500 users, ask Atlassian for a quote.

## What pushes you up a tier

**Subscribers.** The main lever on public pages. Lists grow after every incident, as worried customers sign up, so a page that fits Hobby in January can need Startup by summer. A list of 1,001 subscribers needs Business: $399 a month, up from $99.

**SMS and webhooks.** If your customers expect a text message, or your systems need a webhook, Startup is your real starting price.

**Team members.** An on-call rotation across several teams can pass Hobby's 5 or Startup's 10 before subscribers do.

**Component subscriptions.** Letting a customer follow only the components they use starts on Business for public pages and on Growth for private pages. Without it, every subscriber hears about every incident.

## Hidden costs to consider

**Yearly billing takes paperwork.** Every plan is priced by the month. Yearly card billing is set up by hand with a signed order form, and yearly purchase orders are listed only on Enterprise public plans and on Corporate and Enterprise private plans. The pricing page states no yearly discount; ask Atlassian.

**Atlassian Guard for other users.** Team member SSO with Atlassian Guard is free on Startup and up. Atlassian notes that users on other Atlassian products, such as Jira, who are not on your Statuspage plan are charged for Atlassian Guard.

**No uptime monitoring.** The pricing page lists no uptime checks on any plan. Statuspage expects you to connect a monitoring tool that updates components, so budget for that tool too.

**Hosted only.** Statuspage has no self-hosted or open-source edition. Your subscriber list and incident history live in Atlassian's cloud.

Statuspage is still the easy choice if you run on Atlassian already: private pages show status in the Jira Service Management portal and connect to alerting tools such as Opsgenie and PagerDuty.

## Statuspage alternatives

| **Tool** | **Free plan** | **Paid plans** | **Uptime monitoring** | **Self-hosted** |
|---|---|---|---|---|
| **[Quackback](https://quackback.io)** | 3 components, 100 subscribers | See [Quackback pricing](/pricing) | No, set by hand or through the API | Yes, free under AGPL-3.0 |
| **Statuspage** | 25 components, 100 subscribers | $29 to $1,499/mo for public pages | No | No |
| **[Instatus](https://instatus.com/pricing)** | 15 monitors, 200 subscribers | Pro from $20/mo; check Instatus's pricing page for Business | Yes | No |

**Instatus** is the pick if you want monitoring built in. Its free plan includes 15 monitors, 5 team members and 200 subscribers. Pro starts from $20 a month with 50 monitors, 5,000 subscribers and a custom domain. Business adds 1,000 monitors, 25,000 subscribers, SAML SSO and every page type, including private pages; check Instatus's pricing page for the Business price. See [Quackback vs Instatus](/compare/quackback-vs-instatus).

## How Quackback compares

[Quackback](https://quackback.io) includes a [status page](/features/status) on every plan, Free included. You get components and groups, incidents with updates, scheduled maintenance, incident templates, 90 days of uptime history, subscriber emails and an RSS feed. It sits on your portal beside a [help center](/features/help-center), a [support inbox](/features/inbox) and feedback boards, so customers check status and search your answers in one place.

- **Open source.** Quackback is licensed under AGPL-3.0. Self-host every feature free with Docker, including private and audience-specific status, and keep your subscribers and incident history on your own servers.
- **One price for the whole product.** Paid plans include seats (5 on Pro, 20 on Business, unlimited on Enterprise) and a status page with more components and subscribers on each tier. Status, help center, inbox and feedback share one plan. See [Quackback pricing](/pricing) for current figures.
- **Quackback AI knows the status.** When a customer asks in chat whether something is down, [Quackback AI](/features/ai) checks the live status before it answers. It is on Pro and up.
- **Built for your tools.** The [Status API](/features/api) lets your monitoring tool update components. Webhooks, which send incident and maintenance events to your systems, and the [MCP server](/features/mcp), which lets AI agents work in your workspace, start on Pro. [Integrations](/integrations) start on Business.

Be clear about the trade-offs. Quackback does not monitor your uptime, and neither does Statuspage: you set status by hand or from a monitoring tool through the API. Quackback subscribers hear by email and RSS, with no SMS, Slack or Teams subscriptions. The Free plan has 3 components, against 25 on Statuspage Free. Private status pages and status by audience are on Quackback Enterprise, or free when you self-host.

For the full side-by-side, see [Quackback vs Statuspage](/compare/quackback-vs-statuspage). For how a status page cuts support load during an outage, read the [status page guide](/status-page-guide) or see [a status page for SaaS](/status-page-for-saas).

---

> **Try Quackback** — every signup starts with a 14-day Pro trial. When it ends, you choose a paid plan or Free. Or self-host it with every feature.
> [Start free trial](https://app.quackback.io/signup?plan=pro&from=blog-statuspage-pricing) | [Self-host with Docker](https://feedback.quackback.io/hc/en/articles/67-docker) | [View on GitHub](https://github.com/quackbackio/quackback)

---

## Frequently asked questions

### Is Atlassian Statuspage free?

Yes, for a public page. The Statuspage Free plan includes 100 subscribers, 25 components, 2 team members and email, Slack and Teams notifications. Private and audience-specific pages have no free plan listed.

### Do I pay separately for a public and a private Statuspage page?

Yes. Statuspage public, private and audience-specific pages are separate products, each with its own plan. A team with a Business public page ($399 a month) and a Growth private page ($249 a month) pays both.

### Can I pay for Statuspage yearly?

Yes, but not from the pricing page. Atlassian sets up yearly credit card billing by hand with a signed order form, and lists yearly purchase orders on its top plans. The pricing page states no yearly discount, so ask Atlassian.

### Which Statuspage plan includes SMS notifications?

SMS and webhook notifications start on the Statuspage Startup plan, at $99 a month for 1,000 subscribers. The Free and Hobby public plans send email, Slack and Microsoft Teams notifications. On private pages, SMS starts on Growth at $249 a month.

### Does Statuspage monitor uptime?

No. The Statuspage pricing page lists no uptime monitoring on any plan. You connect a monitoring tool that updates component status through the API. Instatus includes monitors. Quackback, like Statuspage, takes status from you or your monitoring tool through its Status API.
