Engraving of a Roman forum with a speaker's platform in front of a colonnade

Status pages that update when your monitors fail

Link each component to an uptime monitor. When its checks fail, the page on your own domain shows the outage. Post updates from the dashboard, the API or an AI agent, and customers follow along by RSS or in Slack.

status.acme.com Demo

A demo of the Acme status page: all systems operational, then a major outage of Checkout API with an open incident.

When a monitor fails, the page shows it

A monitor counts as down after two failed checks in a row, or anywhere from one to ten if you change it. It can also open an incident for you, published right away or saved as a draft until someone reads it.

One outage, start to finish

From a failed check to a resolved incident

The outage in the page above, as it happened. Maple changes the component's status on its own; people write the words. Every update also goes out by RSS, Atom and Slack.

  1. The checkout-api monitor fails one check. One failure is not enough to change the page.

    Checkout API · Operational
  2. A second check fails, so the monitor is down. The linked component switches to Major outage without anyone touching it.

    Checkout API · Major outage
  3. The monitor opens an incident and publishes it. You can have it saved as a draft for review instead.

    Checkout API · Major outage

    Investigating

    Some card payments are failing. We're looking into it and will post again within 30 minutes.

  4. The on-call engineer posts an update from the dashboard.

    Checkout API · Major outage

    Identified

    A timeout at our payment provider is failing card payments. We're switching to the backup route.

  5. Checks pass again and the component goes back to Operational. The incident stays open while you watch.

    Checkout API · Operational

    Monitoring

    Payments are going through on the backup route. We're watching error rates.

  6. You resolve the incident. It stays on the page, and in the 90-day history, for customers to read.

    Checkout API · Operational

    Resolved

    Card payments have worked normally for 30 minutes. This incident is resolved.

Your brand

It looks like your product, not ours

Five themes to start from, each in light or dark, then your own logo, colours, corner radius and font. Below is the same page in each theme, rendered by the code that serves real pages.

status.acme.com
On your domain
Point a CNAME such as status.acme.com at Maple. The certificate is issued and renewed for you.
Fast and plain
The page is plain HTML that works without JavaScript and keeps serving its last state even if the Maple dashboard is down.
See it before you publish
The editor shows the page as you change it, and nothing goes live until you publish.

Subscriptions and API

Follow along from Slack, a feed reader or a script

Every public page has RSS and Atom feeds, a status badge, and a status.json in the statuspage.io summary format, so tools that already read statuspage.io pages can read yours.

Acme status · RSS

Failed payments at checkout

Identified: A timeout at our payment provider is failing card payments. We're switching to the backup route.

/feed subscribe https://status.acme.com/feed.rss

Slack and feed readers

The page's Subscribe button lists the feed links and the Slack command, /feed subscribe, that posts each update to a channel.

GET /api/v1/status.json

{
  "status": {
    "indicator": "critical",
    "description": "Major System Outage",
    "delayed": false
  },
  "components": [
    {
      "name": "Checkout API",
      "status": "major_outage"
    },
    {
      "name": "Auth",
      "status": "operational"
    },
    {
      "name": "Web app",
      "status": "operational"
    }
  ]
}

status.json

Overall status, every component, open incidents and planned maintenance in one request. Uptime history is available as JSON too.

Badge reading status: operational Badge reading status: major outage

status.acme.com/badge.svg

A badge for your README

badge.svg shows the current status in a README, docs site or app footer.

What it does

What every page includes

CNAME
Your own domain
Point a CNAME such as status.acme.com at Maple. The certificate is issued and renewed automatically.
group
Grouped components
Group components the way customers see your product, such as API and Dashboard, and choose which ones show 90 days of uptime bars.
write / review
Review before you publish
Preview exactly what visitors will see, then publish. Incidents move through Investigating, Identified, Monitoring and Resolved.
maintenance
Scheduled maintenance
Announce a window ahead of time. It switches to In progress when the window starts and to Completed when it ends, with an update posted each time.
password · internal
Private pages
Protect a page with a password, or make it internal so only members of your Maple organization can open it.
break glass
Post when Maple is down
Each page has a break-glass link to a form on the hosted page itself. Open an incident or post an update even if the Maple dashboard is unreachable.
manage_status_page()
Run it from the API or an AI agent
Pages, components and incidents are all in API v2. Over MCP, an agent does it all with one tool, manage_status_page: it creates a page, sets it up, adds a custom domain, publishes it and posts updates.

On the plan

Price, retention and setup

plan
Startup, $39/month, with a 14-day free trial. Every feature is on.
billed as
No separate meter. It is part of the plan.

In production: Superwall sends Maple more than 80 billion traces, logs and metrics a month, about 18 TB, with nothing sampled out. Read the Superwall story

Keep going

Related features

Put your status page live today.

Link your uptime monitors, pick a theme and point your domain at it. Status pages come with the plan, with no separate meter.