Overview
Communicate service health to customers and stakeholders.
StatusDashboard helps your team publish live service health and communicate incidents, maintenance, and announcements to customers. You run the account from the admin console; your audience visits branded status dashboards on the web.
The sections below explain how the product fits together, the core concepts you will use every day, and where to find detailed guides for each area.
How the platform is organized
StatusDashboard is a hosted platform for communicating service health. Your team runs the account; your customers visit branded status pages.
The admin console is where your team signs in — set up components, post incidents and maintenance, manage subscribers, and invite teammates.
Status dashboards are the public pages your customers visit — live component status, event history, and optional subscription links. You can run one or many (for example, one per product or region).
Platform docs use these names throughout: you work in the admin console; your audience visits your status dashboards.
Core concepts
Dashboards are your unique status dashboards. Each dashboard is a standalone page hosted at a dedicated subdomain (acme.statusdashboard.io) or a custom domain (status.acme.com). One organization can run multiple dashboards — for example, one per product, region, or audience.
Components are the individual services your customers care about: API, Web App, Payment Processing, CDN, and so on. Each component has a live status indicator on the dashboard. StatusDashboard updates component statuses automatically when incidents and maintenance windows are opened or resolved.
Events are how you communicate what's happening. There are three types:
- Incidents — unplanned issues affecting one or more components
- Maintenance — planned work with a scheduled start and end time
- Informational — announcements or notices not tied to a component impact
Events move through a workflow — a configurable set of lifecycle phases (e.g. Investigating → Identified → Monitoring → Resolved). Events also carry a severity level that reflects the scope of impact (e.g. Degraded Performance, Partial Outage, Major Outage).
Key features
The table below summarizes major platform capabilities and links to the relevant documentation.
| Area | Capabilities | Documentation |
|---|---|---|
| Status dashboards | Multiple public status pages per organization; subdomain or custom domain; branding, whitelabel, custom code, embed widget, IP allowlist, and visitor SSO | Status dashboards |
| Components & events | Service-level status indicators; incident, maintenance, and informational events; configurable severities and workflows; post-mortem reports | Components, Events |
| Audience segments | Tag subscribers in Segments and include or exclude segments on individual events | Segments |
| Public subscriptions | Visitor subscribe, verify, and manage flows on status dashboards for each enabled channel | Subscriptions |
| Email & SMS notifications | Org-wide subscriber lists, bulk import, suppression and blocked-number hygiene, delivery logs, and monthly send quotas | Email, SMS, Email notifications, SMS notifications |
| Outbound integrations | Deliver event notifications to HTTPS webhooks, Microsoft Teams Adaptive Cards, and Google Chat space webhooks; org-wide subscribers, suppression, and delivery logs | Integrations |
| Inbound webhooks | Signed HTTP requests from monitoring, CI, or incident tools to create or update incident events automatically | Inbound webhooks |
| REST API | Programmatic access to org resources; authenticate with per-user API keys | API reference |
| Security & governance | Admin console SSO (SAML, OIDC, Google); role-based access; tamper-evident audit log | Roles & permissions |
| Organization & billing | Invite teammates, assign roles, self-serve plan changes, and payment methods | User accounts, Billing |
| Product support | Tickets from the admin console, email replies, CC colleagues, and attachment-aware conversations with StatusDashboard | Support |
Where to go next
- Quick Start — create your first dashboard and post your first event
- Status Dashboards — how dashboards work and full configuration reference
- Components — how to define and manage components
- Events — incidents, maintenance, and informational events
- Billing — plans, pricing, and subscription management