Terraform Provider HashiCorp Terraform

Manage StatusPage.me with Terraform

Define status pages, monitors, incidents, maintenance windows, and live metrics as code. Review changes before they reach the dashboard, then apply the same configuration everywhere.

View the Provider on Terraform Registry Read the Setup Guide
Plain HCL, no wrappers terraform plan before every change Import existing pages and monitors

Use the hosted-status-page/hsp provider with your existing StatusPage.me API key.

Terraform® and the Terraform logo are trademarks of HashiCorp, Inc. StatusPage.me is not affiliated with, endorsed by, or sponsored by HashiCorp.

HashiCorp Terraformstatuspage.tf
terraform {
  required_providers {
    hsp = {
      source  = "hosted-status-page/hsp"
      version = "~> 0.1.0"
    }
  }
}

provider "hsp" {}

resource "hsp_status_page" "app" {
  name = "Example Status Page"
  slug = "example"
}

resource "hsp_monitor" "website" {
  status_page_id = hsp_status_page.app.id
  name           = "Website"
  target         = "https://example.com"
}
Infrastructure as Code

Keep operational configuration in the same workflow as the systems it describes

Status pages are part of how you run production. Terraform gives teams a reviewable, repeatable way to create and change them instead of reconstructing configuration by hand.

Review changes before apply

See the planned change to a monitor, maintenance window, or status page in your normal pull-request workflow.

Repeatable environments

Use the same configuration pattern for production, staging, regional pages, or customer-facing services.

A record of operational intent

Your repository shows how a status page, monitor, and maintenance policy are meant to be configured.

Supported today

Manage the operational objects that belong on a status page

Each resource also has a matching data source for reading existing configuration into Terraform.

Status pages

Create and manage the public home for your service health.

Monitors

Configure site, API, and DNS checks alongside the page they report to.

Incidents

Create immutable incident records and append public timeline updates.

Maintenance windows

Plan maintenance communication with the rest of your operational changes.

Live metrics

Keep display metrics in the same configuration workflow as the page that shows them.

Data sources

Look up existing status pages, monitors, incidents, maintenance windows, and metrics when composing configuration.

A predictable workflow

From API key to a managed status page in four steps

1

Create a scoped API key

Grant only the read and write scopes required by the resources your configuration manages.

2

Add the provider

Declare hosted-status-page/hsp and set HSP_API_KEY in your local shell or CI secret store.

3

Describe the resources

Write the status page and the operational objects it needs in HCL.

4

Plan, review, and apply

Terraform shows the proposed change before it calls the StatusPage.me API.

Know the boundaries

Use Terraform where it fits

The provider intentionally focuses on supported API configuration. Advanced API-monitor authentication, headers, queries, and request bodies remain dashboard-managed for now.

Database monitors are not currently exposed. The is_simple status-page setting retains last-applied state because the API does not return it.

Read resources and limitations
Ready to use it?

Put your status page configuration under version control

Start with the setup guide, then use the Terraform Registry reference for every resource argument and import command.

Read the Terraform Setup GuideCreate a StatusPage.me Account