# Status pages that follow your monitors

Publish a status page on your own domain. Components take their status from your uptime monitors and open incidents, you post updates from the dashboard, the API or an AI agent, and customers follow along by RSS, Atom or Slack.

## What a status page includes

### CNAME: Your own domain

Serve the page on a subdomain such as status.acme.com by adding one CNAME record. The certificate is issued and renewed automatically.

### group: Grouped components

Group components the way customers see your product, such as API and Dashboard. Each one shows its status, and you choose which ones show 90 days of uptime bars.

### write / review: Incidents with a review step

Write an update, check exactly what visitors will see, then publish. Incidents move through Investigating, Identified, Monitoring and Resolved.

### maintenance: Scheduled maintenance

Announce a maintenance window ahead of time. It switches to In progress when the window starts and to Completed when it ends.

### theme: Your branding

Add your logo and pick a theme, colours, light or dark appearance, corner radius and font. The editor previews the page as you change it.

### 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 that posts straight to the hosted page, so you can still update customers if the Maple dashboard is unreachable.

### post_status_page_update(): Managed by agents and code

Create pages, components and incidents through API v2. AI agents set up a page with the apply_status_page_config MCP tool and post incidents with post_status_page_update.

## Related

- [Uptime Monitoring](https://maple.dev/features/uptime-monitoring.md)
- [Alerting](https://maple.dev/features/alerts.md)
- [AI & MCP Integration](https://maple.dev/features/ai-mcp-integration.md)
- [API Performance](https://maple.dev/use-cases/api-performance.md)