Atlassian Statuspage → Gatus
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Atlassian Statuspage starts around $29/month and business tiers reach several hundred. Gatus is Apache-2.0 on a small VPS.
Moves cleanly
Nothing — Statuspage holds your incident history and it does not export usefully.
You rebuild
Health checks and the status page itself, both defined in Gatus as YAML.
What Atlassian Statuspage costs you today
Free for a single page with a small number of components and no subscriber notifications worth relying on. Paid tiers scale on components, subscribers and features — private pages, custom domains, SSO and metrics — with team plans in the tens to low hundreds of dollars a month and enterprise quoted. The line most people hit first is subscribers: notifying customers is the entire point of a status page, and it is the thing metered hardest. Checked 2026-08-01.
What actually holds you in
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.
What you are moving to
Gatus is a developer-first health-check service configured entirely in YAML, which means your monitoring lives in the repository, gets reviewed in pull requests, and is deployed like any other code. It handles HTTP, TCP, ICMP, DNS and TLS-expiry checks, evaluates rich conditions on responses — status code, body content, response time, certificate age — and ships a clean dashboard and status page. Apache-2.0, around 11.7k stars, actively developed. It is the natural pick for a team already doing GitOps, and the wrong one if a non-engineer needs to add a monitor.
Free and open source. A single binary or container.
Gatus strengths
- Configuration is YAML in Git — reviewed, versioned and diffable
- Rich condition evaluation, including response body and TLS expiry
- Apache-2.0 with no enterprise carve-out
- Very light: one small binary, minimal memory
What you give up
- No UI for adding monitors — everything is a config change
- Same blind spot as any self-hosted monitor: it can go down with you
- Fewer notification integrations than Uptime Kuma
- Not usable by non-technical team members
The migration, step by step
- 1Write the Gatus configuration as YAML — endpoints, conditions and intervals in one file
- 2Deploy on infrastructure separate from what it monitors
- 3Point a status subdomain at it via DNS
- 4Configure alerting to the channels your team actually reads
- 5Keep Statuspage until the new page has correctly reported one real incident
The gotcha
Gatus is health checks and a status page, not incident communication. Statuspage's subscriber notifications, incident templates and postmortem workflow have no equivalent, and if your customers subscribe to updates you are removing something they use.
When to stay on Atlassian Statuspage
Customers subscribe to your status updates, or incident communication is contractual.
More Layer 3 migrations
Figures verified 2026-08-01 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.