A Statuspage alternative built for agents

Statuspage shows status. It does not measure it.

Statuspage is very good at the communication half of an outage: a clean public page, incident timelines, subscriber notifications. What it does not do is find out that something is broken. Component statuses change when a person clicks, when an email automation fires, or when a separate monitoring product pushes an update through an integration. Many teams end up paying for Statuspage and an uptime monitor and then gluing the two together.

In UpButler the monitor and the component are the same system. A component can follow one or more monitors, read a key from a manifest endpoint, or accept pushed statuses. When a check fails, UpButler re-checks before it believes it (two consecutive failures by default), opens an incident, groups failures on the same page within 30 minutes into one incident, and resolves it when the service recovers. Your page stays honest without anyone babysitting it.

Built to be operated by agents

Most of our users now have an AI agent writing and deploying code for them. We think that agent should also be able to wire up monitoring for what it just shipped. Every action in the UpButler dashboard is the same operation in the REST API and in our MCP server, which exposes 50+ tools. One call creates a monitor and the matching status page component:

curl -X POST https://upbutler.com/api/v1/services \
  -H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
  -d '{"name":"Search API","url":"https://api.acme.com/health","statusPage":"acme"}'

An agent without an account can even bootstrap its own workspace with POST /api/v1/agent/bootstrap, start monitoring right away, and hand you a link to claim it. Statuspage has a solid REST API, but it was designed for scripts and integrations, not for an agent that needs to discover what it can do.

Incident updates, drafted for you

Writing the first public update is the hardest part of an incident. When UpButler opens one, it sends the failing check results to a language model and returns likely causes, suggested next steps and a customer-safe summary that avoids internal hostnames and stack traces. When the service recovers, it drafts the post-incident summary. Any note you write can be "polished with AI" before it goes out. Each page can carry AI guidelines ("never mention our cloud provider") and a list of terms the AI must never use; text that breaks them falls back to a neutral template. Prefer to write every word yourself? Turn AI public updates off for the page.

Your brand, at a smaller price

Status pages come with theme presets and font choices on every plan. Starter removes our branding for $12 a month and includes a custom domain as bring-your-own domains roll out; Pro at $29 adds custom CSS and 5 pages. On Statuspage, a custom domain starts with the Hobby plan at $29 a month, and the subscriber limits climb with the price.

Where Statuspage is ahead

We will not pretend otherwise. Statuspage has private and audience-specific pages that show different components to different customers behind a login, which UpButler does not offer. It sends SMS to subscribers. It plugs into Jira, Confluence and Atlassian's incident tooling, and it supports SSO through Atlassian Guard. For a large company with an enterprise audience and an Atlassian contract, those can outweigh everything above.

Switching from Statuspage

UpButler has a Statuspage importer, and you do not have to switch in one go. In the dashboard open Settings → Import, choose Statuspage and paste your public status page URL. No Statuspage key is needed. A dry run shows what will be created before anything is written.

# Public page: no Statuspage key needed. mirror keeps components in sync while you test.
curl -X POST https://upbutler.com/api/v1/import/preview \
  -H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
  -d '{"source":"statuspage","url":"https://status.acme.com","mirror":true}'

# Looks right? Run it (background job; poll GET /api/v1/import/jobs/<id>)
curl -X POST https://upbutler.com/api/v1/import \
  -H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
  -d '{"source":"statuspage","url":"https://status.acme.com","mirror":true}'

1. Components and groups are recreated on an UpButler page, with uptime history rebuilt from their creation date and past incidents.
2. Past incidents and maintenance come along with their timelines. Only finished ones are imported, and a public page exposes about the last 50; use a Statuspage API key and page id instead of the URL to import the full history.
3. With mirror on, UpButler adds a manifest monitor that reads your Statuspage components.json, and the imported components follow it. Run both side by side for a week.
4. Then attach components to real UpButler checks instead of the mirror, so the page updates itself, and delete the mirror monitor.
5. Share your new address, your-name.upbutler.com. Bring-your-own domains are rolling out, from Starter.
6. Subscribers are not imported. Post a "we moved" update on the old page linking to the new subscribe form; email subscribers confirm with double opt-in.

If you were updating Statuspage from scripts or CI, swap those calls for a single batch push:

# Whatever used to call the Statuspage API can push many components at once
curl -X POST https://upbutler.com/api/v1/pages/acme/status \
  -H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
  -d '{"statuses":{"api":"operational","billing":{"status":"degraded","message":"Stripe latency"}}}'

An agent can run the import and rewire your components over the MCP server.