Statuspage doesn't monitor anything. Its own core feature list leans on REST API access and third-party integrations because something else has to tell it when a component is down, whether that's a person clicking a dropdown or a monitoring tool posting to its API. If that monitoring tool is already ObserveOne, the question worth asking before the next Atlassian invoice arrives is whether ObserveOne's own status page already does the job. Below is what Statuspage actually charges, what moving a status page over looks like, and the gaps that are still real if you do.
Statuspage prices on subscriber count and team size, not monitor count. Pulled from atlassian.com/software/statuspage/pricing on September 21, 2026:
| Plan | Price | Detail |
|---|---|---|
| Free | $0/mo | 100 subscribers, 25 components, 2 team members, 2 metrics. Email, Slack and Microsoft Teams notifications, REST API access. No SMS, no custom domain. |
| Hobby | $29/mo | 250 subscribers, 5 team members, 5 metrics. Adds basic customization and a custom domain. Still email, Slack and Teams only, no SMS or webhook notifications yet. |
| Startup | $99/mo | 1,000 subscribers, 10 team members, 10 metrics. First tier with SMS and webhook notifications, custom CSS, and SSO through Atlassian Guard. |
| Business | $399/mo | 5,000 subscribers, 25 team members, 25 metrics. Adds custom CSS/HTML/JS, component subscriptions (subscribe to one component instead of the whole page), and role-based access control. |
| Enterprise | $1,499/mo | 25,000 subscribers, 50 team members, 50 metrics. Same feature set as Business plus yearly purchase orders and invoicing. |
Every plan ships the same core feature list: incidents, components, scheduled maintenances, incident templates, page analytics and REST API access, per the pricing page's own FAQ. What actually changes between tiers is subscriber headroom and which notification channels and customization options unlock, not which features exist at all.
Source: atlassian.com/software/statuspage/pricing, fetched September 21, 2026.
Moving a status page isn't a code migration. It's re-pointing a public page at data that, if ObserveOne is already running the checks, mostly already exists.
Statuspage components carry a status someone sets, by hand or through the API. ObserveOne's status pages skip that layer: attach an existing monitor with obs status-page add-monitor and the page shows that monitor's real check results, not a status someone typed in. Anything tracked as a component needs a live ObserveOne monitor behind it first.
ObserveOne's incident timeline uses the same four stages Statuspage popularized: investigating, identified, monitoring, resolved. The gap is formatting. Update bodies only render bold text, inline code and paragraph breaks, since the page is public, unauthenticated and ships with no client-side JavaScript at all. Statuspage's incident templates and richer formatting don't carry over.
Statuspage lets you announce a maintenance window before it starts. Nothing in ObserveOne's current status-page docs does the same. An incident there can only open once something is actually happening.
Status pages are one of the seven resource types obs export and obs apply handle, matched by slug, so a fleet of pages defined once in obs.json and rolled out with obs apply works for the page shell itself. Monitor attachments are the one piece apply skips; those still go through obs status-page add-monitor and remove-monitor one call at a time.
Subscriber notifications (email, SMS, webhook), a custom domain, custom CSS/HTML/JS branding, audience-specific pages and SSO have no ObserveOne equivalent today. A team leaning on any of those keeps paying for Statuspage, or something like it, regardless of what happens to the monitoring underneath.
Ranked by how closely each one replaces Statuspage. Every row links to a full side-by-side breakdown.
| Tool | Best for | Pricing | Comparison |
|---|---|---|---|
1 ObserveOneAI-powered synthetic monitoring and self-healing test automation | AI-First QA Teams | Free tier available, paid plans from $6/mo | vs Statuspage |
2 PagerDutyDigital operations management and incident response | DevOps Teams | Free (5 users), Pro $21/user/mo, Business $41/user/mo (+ Add-ons) | vs Statuspage |
3 OpsgenieAtlassian's on-call and alert-routing tool, now being retired (end of support April 2027) | SRE Teams | Legacy; no longer sold by Atlassian (migrate to Jira Service Management or Compass) | vs Statuspage |
4 New RelicObservability platform for every engineer | Developers | 100 GB/mo free data ingest, $0.40/GB beyond. Standard from $10/mo/user, Pro from $349/user/mo | vs Statuspage |
5 PingdomWebsite performance and uptime monitoring | Web Developers | Synthetic from $16.5/mo, RUM from $16.5/mo (100k pageviews) | vs Statuspage |
6 GrafanaOpen-source observability and data visualization | Engineers | Open source free, Cloud from $0 (scalable usage-based) | vs Statuspage |
7 UptimeRobotFree uptime monitoring for websites | Freelancers | Free (non-commercial, 50 monitors), Solo $10/mo ($9 billed annually), Team $41/mo ($35 billed annually) | vs Statuspage |
8 PrometheusOpen-source metrics monitoring and alerting toolkit | DevOps | Free and open source | vs Statuspage |
9 Better StackUptime monitoring, incident management and status pages | DevOps Teams | Free tier, paid from $29/responder/mo (billed annually, $34 monthly) | vs Statuspage |
10 StatusCakeWebsite uptime, performance and SSL monitoring | Small Businesses | Free tier, Superior $24.49/mo ($20.41 billed annually), Business $79.99/mo ($66.66 billed annually) | vs Statuspage |
Take subscriber notifications out of the picture and most of Statuspage's reason for existing goes with them. Telling the people who signed up that something's wrong, over email, SMS or a webhook, without anyone refreshing a page, is the actual product. ObserveOne's status pages have no subscriber list at all. Custom domains, custom CSS/HTML/JS, component subscriptions, audience-specific pages and SSO are real features on Statuspage's higher tiers that ObserveOne doesn't attempt. None of that is a knock on ObserveOne so much as a reminder that Statuspage is a dedicated status-communication product and ObserveOne's status page is one feature of a monitoring platform. If the actual requirement is subscribers getting paged when something breaks, that requirement still needs Statuspage or something like it.
There's a free plan: 100 subscribers, 25 components, 2 team members, email, Slack and Microsoft Teams notifications, and REST API access, per atlassian.com/software/statuspage/pricing. SMS notifications, custom CSS and SSO all start on paid tiers.
Yes. Public or private pages at /status/<slug>, server-rendered and auto-refreshing, showing 90-day uptime bars and a 24-hour uptime percentage for whichever monitors are attached, plus an operator-authored incident timeline on top.
No. ObserveOne's status pages have no subscriber list or notification system of their own. That's still a separate job Statuspage does that ObserveOne's status page doesn't.
Not currently. Pages are served at /status/<slug> on ObserveOne's own domain, with no documented option to point a custom domain at one, which Statuspage has offered starting on its $29/mo Hobby tier.
If Statuspage is open in a tab because it's the only place customers can check whether things are working, and the monitoring behind that page is already ObserveOne, turning on ObserveOne's own status page costs nothing and takes a few minutes. If the Atlassian invoice keeps arriving for subscriber emails, a custom domain or a page the brand team signed off on, none of that ships in ObserveOne yet.
Check your site free, no signup