StatOSS compared with Atlassian Statuspage
Statuspage is the incident communication page large companies use, priced per page from $29 a month, with no monitoring of its own. StatOSS is a status page with the checks built in, from free.
Northwind is up.
All 2 monitors are responding, 5 failed checks in the last 24 hours.
API
Up for 6 h 51 min99.65% passed
1,438 checks, median 204 ms, 5 timeouts
95% under 299 ms
- Timed out5 min, 5 checks
Website
Up for 23 h 58 min100% passed
1,438 checks, median 137 ms, all passed
95% under 199 ms
Side by side
| StatOSS | Statuspage | |
|---|---|---|
| Free tier | 1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alerts | Public pages only: 100 subscribers, 2 team members, 2 metrics, 25 components, email, Slack and Teams notifications, no custom domain |
| Cheapest paid plan | Hobby $4 a month: 10 monitors, every minute, 90 days. Pro $15: 100 monitors across 10 pages, a year, your own domain | Hobby, $29 a month per page: 250 subscribers, 5 team members, custom domain, email, Slack and Teams notifications. SMS and webhooks from $99; private pages from $79 |
| Uptime checks | Built in: every monitor checked every minute from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia, the regions in turn, failures checked again from every region | None. Component status comes from integrations (PagerDuty, Pingdom, Datadog and others), email automation or the API |
| What the page shows | Bars with a mark for every failed check, each failure with its time and reason, incidents, maintenance, an error budget | Component states, incident history, optional metrics, a 90-day uptime showcase computed from state changes |
| Subscribers | Email and webhook subscribers on Pro, 1,000 per page and more in blocks of 1,000, per-monitor choice; RSS and Atom on every page | Email, SMS (paid), Slack, webhook, RSS and Atom; capped per plan, with RSS and Atom not counted toward the cap |
| Pricing model | Per account: Pro holds 10 pages for $15 a month | Per page: each page is its own subscription |
| Open source | The core is MIT licensed and runs on your own box | No |
Facts about the other product were read from its own site on 5 October 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.
Who updates the page
Atlassian's own docs say it plainly: Statuspage does not ping your servers. Something else has to notice the outage and tell the page, through an integration, an email, or the API, and until it does the page says everything is fine. StatOSS runs the checks itself: a monitor going down opens an incident on the page and resolves it on recovery, with the failed checks drawn underneath. You can still open incidents by hand, post updates, write post-mortems and plan maintenance windows, and an incident you touch stops being automatic.
What StatOSS does differently
Most uptime pages show a row of green squares, one per day, and a percentage. A five-minute outage at 3 a.m. becomes a square that is still green and a figure that still says 99.99%. StatOSS draws a strip per monitor where every bar is one check, its height the response time, amber for a timeout and red for any other failure, and groups the failed checks into entries with the time and the reason. The mark stays visible for the whole range. A customer who was refused at 3 a.m. finds the moment on the page, and so do you.
Before a failure counts, a second server on another network repeats the check, and only a failure both see goes on the record; two of those in a row make an outage. The response time of every check is kept, and a slow threshold turns a sluggish service into its own state with its own alert. The core is open source under MIT, so the page you get from the hosted service is the page you can run yourself.
When Statuspage is the better pick
If you already run Opsgenie, Jira Service Management and the rest of the Atlassian suite, Statuspage slots in and your incident process stays where it is. If you need tens of thousands of subscribers with SMS, private pages behind SSO, or custom HTML, those are Statuspage tiers and StatOSS does not sell them. If the page must not depend on a small vendor, a large one is the safer choice, though the MIT core means the page can run without us.
Moving over
The import screen under Monitors reads a Statuspage export. Components become monitors or components, and the incidents come along as history, so the page does not start empty. The import page has the steps.