The One Status
The One Status is a public-facing status page platform built for MSPs. Publish a branded status page so your clients always know whether your services are operational — and when they're not.
Who Uses It
| Role | How They Use Status |
|---|---|
| MSP Owner | Create and manage status pages; declare incidents; schedule maintenance; configure notifications |
| Technician | Post incident updates; update component statuses; write postmortems |
| MSP Client | View real-time service health; subscribe for email or SMS alerts |
| Client End User | View status page; receive notifications for services they care about |
Key Capabilities
- Multiple status pages — Create one page per client, brand, or service cluster; each page gets its own subdomain
- Components and groups — Model your service stack (Help Desk, Client Portal, Phone System) as components with color-coded status badges
- Automated monitoring — Configure HTTP health checks per component; The One Status polls every minute and auto-updates status
- Incidents — Declare and manage incidents with a structured status workflow; post timestamped updates visible to subscribers and the public
- Postmortems — Write and publish post-incident analyses attached to resolved incidents, visible on the public status page
- Maintenance windows — Schedule planned maintenance with advance subscriber notice; auto-start and auto-complete on schedule
- Subscribers — Clients subscribe via email or SMS; choose notification frequency (immediate, daily digest, weekly digest) and which components to follow
- Outbound webhooks — Push real-time status events to Slack, PagerDuty, monitoring tools, or any HTTP endpoint
- Custom domains — Serve your status page at
status.yourmsp.cominstead of the default subdomain - Branding — Logo, favicon, primary color, background color, header/footer text, and custom CSS per page
- Public API — JSON endpoints for summary, components, and incident history; cacheable with 10-second TTL
- API keys — Scoped programmatic access to the management API
How It Fits in The One Stack
The One Status is standalone — it does not require other The One Stack products. However, it integrates naturally with The One Stack ecosystem via webhooks.
| Integration | What It Does |
|---|---|
| Hub | SSO authentication for the management console |
| Outbound Webhooks | Push incident/maintenance/component events to PSA, Slack, monitoring tools |
| Public API | Embed status data in Portal, your marketing site, or client dashboards |
Prerequisites
- A The One Stack organization with Status entitlement
- At least one user account (owner or admin) to manage the status page
Next Steps
- Getting Started — Create your first status page and publish it
- Component Management — Add components and configure automated monitoring
- Incident Creation — Declare and manage incidents
- Subscriber Notifications — How clients subscribe and receive notifications
- Maintenance Windows — Schedule planned maintenance
- Custom Domain Setup — Use your own domain