comparing monitoring as code
Atlassian Statuspage in Terraform: two forks, one gap
Search the registry for a Statuspage provider and you get two, neither from Atlassian. The one with the stars stopped shipping in 2022. The one still shipping has eight of them. And the resource you probably came for is in neither.
The table below is the whole comparison, unedited. Read it first if you like, it is the same one we would send you.
AGPL-3.0 · one binary · free tier · no card required
Two forks, neither from Atlassian
| Statuspage | Uptimepage | |
|---|---|---|
| provider from the vendor | none | yes |
| who maintains it | two community forks | Uptimepage |
| most-starred fork | yannh, last release 2022 | not needed |
| maintained fork | sbecker59 v1.1.0, Aug 2026 | ours |
| create the page in code | no resource | yes |
| components and incidents | yes | yes |
| monitoring included | none, bring your own | built in |
Atlassian publishes atlassian/atlassian-operations at v2.0.5 for Jira Service Management operations, and no provider for Statuspage under any namespace it owns.
yannh/statuspage has 52 stars, last release v0.1.12 in May 2022 and last commit in January 2025. sbecker59/statuspage has 8 stars and released v1.1.0 on 1 August 2026.
The maintained fork offers component, component_group, incident, metric, metric_provider, page_access_group, page_access_user and subscriber. Neither fork has a resource that creates the page.
Statuspage publishes status and does not run checks, so the monitoring behind it is a separate tool and a separate provider.
Verified 11 August 2026 against the Terraform Registry and each provider's repository. Providers ship often, so check before you decide.
Atlassian publishes none
Atlassian does have an official provider on the registry, atlassian/atlassian-operations at v2.0.5, but it manages Jira Service Management operations and has nothing to do with Statuspage. For Statuspage itself there is no provider under any Atlassian namespace. Everything you will find is community-maintained.
The two forks, dated
yannh/statuspage is the one search puts first, with 52 stars. Its last release is v0.1.12 from May 2022 and its last commit is from January 2025. sbecker59/statuspage is the maintained one: v1.1.0 released 1 August 2026, eight stars. Popularity and maintenance point at different repositories here, and the star count is what most teams pick on. Check the release date first.
Neither creates the page
The maintained provider offers component, component_group, incident, metric, metric_provider, page_access_group, page_access_user and subscriber. There is no page resource in it. So you click the Statuspage together by hand, then let Terraform fill it in, which is exactly the boundary that makes people give up on the idea. Statuspage also publishes status without running any checks, so whatever actually watches your service is a second tool, a second provider and a second bill.
The resource neither Statuspage fork has
resource "uptimepage_status_page" "public" {
slug = "acme"
name = "Acme Status"
}Where Uptimepage fits
The page is a resource. So are its components, which bind to real monitors rather than to a name you keep in step by hand, and so are the notification channels. Incidents open automatically from failing checks and reach confirmed email and webhook subscribers. Monitoring and the public page are the same binary, so there is one provider and one bill. Hosted free with no card, or self-hosted under AGPL.
- 01Sign in with GitHub or Google. No card, no sales call.
- 02Paste a URL. The first check runs before you have finished reading this.
- 03Publish the status page, or export it to Terraform and keep it in Git.
api99.98%
p95 142ms · one incident in 45 days
dashboard99.91%
p95 318ms · two degraded days
webhooks99.99%
p95 88ms · no incidents
RESOLVED14 min
Elevated latency on the dashboard API
14:22 resolved, latency back under 300ms
14:08 opened automatically by the dashboard check
up degraded down 45 days · email & webhook subscribers