Free & Open Source Status Page | openstatus
Ship your status page before your SOC 2 auditor asks for it
The status page trusted by growing teams. Communicate incidents, prove compliance readiness, and stay audit-ready on your own domain. Hosted for you, or self-host the open source stack.
Trusted by teams who ship transparency
- Cal.com
- Documenso
- WhiteBIT
- Traefik
- OpenPanel
- Probo
- Hanko
- Superwall
- StreamElements
- Smplrspace
- Passbolt
- TwentyCRM
The status page that closes enterprise deals
Security questionnaires ask how you notify customers during an incident. openstatus answers that in one link: a branded page on your own domain, with timestamped incident history an auditor can read without asking you for screenshots.
Themes, custom domains, public or password-protected access, status reports, maintenance windows and subscriptions: see it all on status pages.
Monitor from 28 regions: know before your customers do
Monitor your endpoints from 28 regions across multiple clouds. Get alerted on Slack, Discord, PagerDuty, or email the moment something breaks. Your status page updates automatically, with no manual work during incidents.
Read more about uptime monitoring.
Managing openstatus for humans and agents
Every action in the dashboard is reachable programmatically. One API key, four ways in:
- CLI: manage from your terminal
- API: typed HTTP endpoints with an OpenAPI spec
- MCP server: let Claude, ChatGPT, or Cursor run your monitoring
- Terraform provider: version monitors as HCL
Read more about our tooling.
Try it before you sign up
Check any URL's response time from every one of our 28 regions. No account, no credit card. It's the same probe network that powers your monitors.
Status Page
Dashboard
Frequently asked questions
What is openstatus?
Openstatus gives you a branded status page and uptime monitoring that's audit-ready out of the box. Set up status.yourcompany.com, connect your monitors, and start communicating incidents in minutes.
Do I need a status page for SOC 2?
SOC 2's CC2.3 criteria requires you to demonstrate incident communication with external parties, but it doesn't prescribe a specific tool. That said, a status page is the fastest, most auditor-friendly way to satisfy that requirement.
How does openstatus help with SOC 2 compliance?
Openstatus gives you everything an auditor needs to verify your incident communication process:
- Branded status page with custom domain
- Incident history with timestamped status reports
- Subscriber notifications so stakeholders are proactively informed
- Maintenance windows for planned changes
- Password protection for internal or client-specific pages
What does the free plan include?
The free plan includes one monitor, one status page (with three page components), and a minimum check interval of 10m.
Who is behind openstatus?
Openstatus is built by Thibault and Max, a bootstrapped two-person team building in public.
What regions does openstatus monitor from?
Openstatus monitors from 28 regions worldwide across all continents:
- Europe: Amsterdam 🇳🇱, Stockholm 🇸🇪, Paris 🇫🇷, Frankfurt 🇩🇪, London 🇬🇧
- North America: Dallas 🇺🇸, New Jersey 🇺🇸, Los Angeles 🇺🇸, San Jose 🇺🇸, Chicago 🇺🇸, Toronto 🇨🇦
- South America: São Paulo 🇧🇷
- Asia: Mumbai 🇮🇳, Tokyo 🇯🇵, Singapore 🇸🇬
- Africa: Johannesburg 🇿🇦
- Oceania: Sydney 🇦🇺
Do you offer annual billing?
Yes. All paid plans are available with monthly or annual billing. Choose annual billing to get 2 months free: that's Starter at $300/year ($25/mo) and Pro at $1,000/year (~$83/mo).
Can I self-host openstatus?
Yes. Openstatus is fully open source and can be self-hosted using its 8.5MB Docker image.
Does openstatus have an API?
Yes. Openstatus exposes a typed JSON-over-HTTP API powered by ConnectRPC, with a published OpenAPI spec.
Can I manage openstatus from Claude or ChatGPT?
Yes. Openstatus ships a remote MCP server at api.openstatus.dev/mcp that connects Claude Desktop, ChatGPT, Cursor, and any Model Context Protocol client to your workspace.
Can I manage monitors as code?
Yes. Openstatus offers two ways to treat monitoring as code:
- YAML + CLI: keep your monitor configuration in your repo and sync with
openstatus monitors apply. - Terraform provider: for teams already managing infrastructure in HCL.