Skip to main content

for developers

Uptime monitoring built for developers

Define your monitors the way you define the rest of your infrastructure: in code, reviewed in a pull request. A Terraform provider, a full REST API and an MCP server, plus a status page your users can trust. Run the single binary yourself or start free on the hosted tier, no card.

what you get

  • As code Terraform + REST + MCP
  • Checks HTTP, TCP, DNS, TLS, ping
  • Check interval every 60s
  • Self-host one binary, AGPL
  • Probes multi-region, run your own
  • Price to start free, no card

monitors as code

Declare monitors, status pages and notification channels in HCL with the official Terraform provider. Run `terraform plan` on every pull request so a reviewer sees the diff before it ships, and roll back a bad check with a revert.

an API that means it

A full REST API covers everything the dashboard does, authenticated with scoped, org-bound tokens you can narrow to exactly one job. Script onboarding, wire checks into CI, or build your own tooling on top.

query it from your assistant

An MCP server lets an LLM client read your monitoring and take fenced, audited actions. Ask what is broken and since when in plain language, answered from the same config that lives in your repo.

probes where your users are

Run regional probe agents on your own boxes and check from where your customers actually are. Each agent authenticates with a scoped, org-bound token.

Declare a monitor in Terraform

resource "uptimepage_target" "api" {
  name     = "api prod"
  interval = 60

  check = {
    type = "http"
    http = {
      url = "https://example.com/healthz"
      expected_status = {
        kind  = "exact"
        exact = 200
      }
    }
  }
}

links

FAQ

Can I manage monitors as code?
Yes. An official Terraform provider covers monitors, status pages and channels, so you declare them in HCL and review changes in a pull request.
Is there a REST API?
Yes, a full REST API mirroring the dashboard, authenticated with scoped, org-bound tokens you can narrow to a single job.
Does it work with LLM tooling?
Yes. An MCP server lets an LLM client read your monitoring and take approval-gated, audited actions from the same config that lives in your repo.
Can I self-host it?
Yes. The whole product is one AGPL binary; compose brings it up next to Postgres and ClickHouse in minutes.

Start in under 5 minutes.

Start free

features · pricing · notes