Start with what you need right now
Most teams just need the quickest route to a good setup. The automation layer can come once the basics are working well.
Begin with the essentials
Start with the guides that take you from a blank workspace to clear customer communication.
- Shape the page around what customers care about.
- Learn the day-to-day admin workflow.
- Keep incidents, maintenance, and access clear.
Then layer in automation
Once the basics feel solid, this is where API, Terraform, MCP, Slack, and monitoring come in.
- Automate incidents, maintenance, and page management.
- Roll out config as code and governance in stages.
- Connect AI clients and proactive monitoring safely.
These will get you up and running
These are the guides most teams need first.
Getting Started
Set up your first page, hierarchy, and communication workflow without overcomplicating the rollout.
Read getting startedHow to Use StatiBeat
A reader-focused guide for customers, subscribers, and stakeholders using the public status page.
Read public user guidesAdmin Quickstart
The shortest useful path through page administration, from page creation to a tested incident workflow.
Read admin quickstartIncidents, Maintenance, and Message Automation
Learn the core operator workflow before you add deeper integrations or automation.
Read operator guideThen bring in automation and integrations
Use these when you want more leverage without making the setup messy.
Automation and Integrations
A curated entry point for API, Terraform, MCP, Slack, and Beats.
Read automation guideAPI Quickstart
Start the simplest automation path for scripts, internal tools, and CI jobs.
Read API quickstartTerraform Provider
Manage supported configuration domains as code once the communication model is stable.
Read provider docsMCP Integrations
Compare Hosted MCP with the page-scoped MCP server and choose the right connector surface.
Read MCP referenceBeats
Add proactive synthetic monitoring that can raise alerts, drafts, and automated updates.
Read Beats guide