Application Overview
This page gives you a quick map of StatiBeat so you can decide where to go next.
If you already know the task you want to complete, the task-based guides in the sidebar are usually faster than this overview.
Public status page
The public status page is what customers, subscribers, and internal stakeholders use to understand service health.
It can show:
- the current overall status
- active incidents and active maintenance
- upcoming maintenance
- a service or component hierarchy
- recent history
- service, incident, and maintenance detail pages
Private pages can require a shared password, viewer SSO, or both. Visitors can also manage subscriptions and custom-view access from self-service links when those features are enabled.
Read next:
Page administration
Page administration is where operators run the day-to-day status page.
Use page admin to manage:
- incidents, maintenance, updates, and post-incident reports
- hierarchy, components, lifecycle stages, and status types
- subscribers, custom views, RSS feeds, and analytics
- customization, domains, viewer access, and page access
- Slack, Beats, AI settings, API tokens, Hosted MCP, and Terraform
Some areas appear only when the workspace plan or feature set includes them. If you do not see a feature, check your plan, workspace entitlements, or administrator access.
Read next:
- First-Run Setup
- Admin Quickstart
- Customizing Your Status Page
- Page Routing and Viewer Access
- Page Access
- Beats
- Setting Up and Using the Slack App
Organization administration
Organization administration is for tenant-wide setup rather than a single status page.
Use org admin to manage:
- status page creation and imports
- tenant users
- organization-wide authentication
- billing and plan changes
Use page admin when you are operating a specific page. That split helps larger teams separate billing and user ownership from incident communication.
Read next:
Automation and integrations
StatiBeat includes several automation paths. Choose the one that matches the job:
- use API Quickstart when you are building scripts or internal tools
- use Terraform Workspace and Export when configuration should live in code
- use Hosted MCP when an OAuth-capable AI client needs approved access
- use Beats when monitoring should feed status communication
- use Setting Up and Using the Slack App when incident work happens in Slack
Start with the manual workflow first. Automation works best after the page structure, roles, and communication style are already clear.