How StatusOwl works, in detail.
Setup guides for status pages and the checks behind them, reference for the read-only API, and a plain account of what StatusOwl does not do yet. Search from the bar above, or start with a category.
Browse by category
Status pages first, then the monitoring that feeds them.
Getting Started
Publish your first status page, attach the services it reports on, and put it on your own domain.
- Quickstart
- Inviting your team
Status Pages
The page itself — services, incidents, maintenance windows, 90 days of uptime history, branding, custom domains and private pages.
- Create a status page
- Services on your page
- Incidents
- 6 more
Monitoring
The checks behind the page. HTTP, TCP and ping monitors, plus SSL certificate and domain expiry tracking.
- HTTP monitor
- TCP / port monitor
- Ping monitor
- 2 more
Notifications
Email, Slack, Discord, Microsoft Teams, ntfy and signed webhooks — and an honest account of what does and does not dispatch today.
- Notifications overview
- Discord
- 4 more
Server Agents
Watch Owl reports CPU, memory, disk, network and patch state from your own hosts. Dockman does the same for Docker containers.
- Watch Owl overview
- Installing Watch Owl on Linux
- Watch Owl alert rules
- 1 more
Account & Billing
Plans and limits, Stripe billing, organization roles and the audit log.
- Plans & limits
- Billing
- Roles & permissions
- 1 more
API Reference
The read-only REST API: keys, scopes, rate limits, errors, and the two monitor endpoints that exist today.
- Authentication
- Monitors API
- Managing API keys
- 3 more
FAQ
Short answers to the questions people ask before signing up, including the ones where the answer is no.
- Frequently asked questions
Something not covered here?
Email us and a person who works on StatusOwl will answer.