Skip to content

Open-source status page, incident response and uptime monitoring

minor wording (#1979)

Thibault Le Ouay1b678e71a859
diff --git a/apps/web/src/content/pages/home.mdx b/apps/web/src/content/pages/home.mdx
index 11fd550cd..6daf929de 100644
--- a/apps/web/src/content/pages/home.mdx
+++ b/apps/web/src/content/pages/home.mdx
@@ -6,9 +6,9 @@ description: "The open-source status page trusted by growing teams. Communicate
category: "product"
faq:
- question: "What is openstatus?"
- answer: "Openstatus is an open-source status page and uptime monitoring platform. It helps teams communicate incidents transparently, prove compliance readiness for SOC 2 and other audits, and monitor services from 28 regions globally. Openstatus is bootstrapped, not VC-funded, and available as a managed SaaS or for self-hosting."
- - question: "Why do SOC 2 audits require a status page?"
- answer: "SOC 2 Trust Services Criteria require organizations to communicate system availability and incidents to stakeholders. A status page provides documented evidence of your incident communication process — showing auditors that you proactively notify users about outages, maintenance, and degraded performance."
+ answer: "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. It's open-source, self-hostable, and used by teams like Cal.com, WhiteBIT, and Documenso."
+ - question: "Do I need a status page for SOC 2?"
+ answer: "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. Every status report on openstatus is timestamped and documented automatically, giving you an audit-ready trail of how you communicated during incidents. Most teams set it up in under 10 minutes."
- question: "How does openstatus help with SOC 2 compliance?"
answer: "Openstatus gives you a branded status page with incident history, subscriber notifications, and maintenance windows — all the evidence an auditor needs to verify your incident communication process. Every status report and update is timestamped and documented automatically."
- question: "What does the free plan include?"
@@ -63,18 +63,15 @@ Make it yours with [themes from our Theme Store](https://themes.openstatus.dev),
Read more [about status pages](/status-page).
-## Global uptime monitoring from 28 regions
+## Monitor from 28 regions — know before your customers do
-Uptime monitoring helps you detect when your website or service goes down. Instead of learning about issues from users, you get **notified immediately** and can respond faster. Monitor your APIs to ensure they return the expected values within a **defined threshold**, helping you **catch** slow responses or failures before they affect users.
+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 — no manual work during incidents.
-Get a real picture with **28 regions** across multiple clouds. Validate your APIs with **assertions** and **thresholds**. Define monitors as **YAML configuration** with our [CLI](https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/). Deploy our **8.5MB Docker image** behind firewalls or export to [OpenTelemetry](https://docs.openstatus.dev/guides/how-to-export-metrics-to-otlp-endpoint/).
-
-- **28 regions** across **multi-cloud providers** (Fly.io, Koyeb, Railway)
-- **API Monitoring**: assertions, thresholds, status codes, headers, body validation
-- **Monitoring as Code**: YAML configuration, GitHub Actions, CLI
-- **Private Locations**: 8.5MB Docker image for internal monitoring
-- **Integrations**: OpenTelemetry export, notification channels (email, Slack, Discord, etc.)
-- Check all regions in our [global speed checker](/play/checker)
+- **28 regions**, 3 cloud providers — no blind spots
+- Monitor any **HTTP endpoint**, REST or GraphQL
+- Version your monitors with **YAML** and **CI/CD**
+- Monitor behind firewalls with a single **Docker container**
+- Alerts on **Slack**, **Discord**, **PagerDuty**, email, webhooks, ...
Read more about [uptime monitoring](/uptime-monitoring).
@@ -112,17 +109,17 @@ Check your website's latency
<Details summary="What is openstatus?">
-Openstatus is an open-source status page and uptime monitoring platform. It helps teams communicate incidents transparently, prove compliance readiness, and monitor services from **28 regions** globally across multiple cloud providers (Fly.io, Koyeb, Railway).
+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.
-Openstatus is bootstrapped, not VC-funded, and available as a [managed SaaS](https://app.openstatus.dev) or for [self-hosting](https://github.com/openstatushq/openstatus).
+It's open-source, self-hostable, and used by teams like [Cal.com](https://status.cal.com), [WhiteBIT](https://status.whitebit.com), and [Documenso](https://status.documenso.com). Available as a [managed SaaS](https://app.openstatus.dev) or for [self-hosting](https://github.com/openstatushq/openstatus).
</Details>
-<Details summary="Why do SOC 2 audits require a status page?">
+<Details summary="Do I need a status page for SOC 2?">
-SOC 2 Trust Services Criteria require organizations to communicate system availability and incidents to stakeholders. A status page provides documented evidence of your incident communication process — showing auditors that you **proactively notify** users about outages, maintenance, and degraded performance.
+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.
-With openstatus, every status report and update is **timestamped** and documented automatically — giving you an auditable trail of how you communicate during incidents.
+Every status report on openstatus is **timestamped** and documented automatically, giving you an audit-ready trail of how you communicated during incidents. Most teams set it up in under 2 minutes.
</Details>
diff --git a/apps/web/src/content/pages/use-case/compliance.mdx b/apps/web/src/content/pages/use-case/compliance.mdx
index 1bf0211d1..e1abf0a17 100644
--- a/apps/web/src/content/pages/use-case/compliance.mdx
+++ b/apps/web/src/content/pages/use-case/compliance.mdx
@@ -1,14 +1,14 @@
---
-title: "SOC 2-Ready Status Page in 10 Minutes"
+title: "SOC 2-Ready Status Page in 2 Minutes"
publishedAt: "2026-03-13"
author: "openstatus"
description: "SOC 2 auditors expect documented incident communication. Openstatus gives you a branded status page with incident history, subscriber notifications, and audit-ready evidence — set up in minutes."
category: "Compliance"
faq:
- - question: "What SOC 2 criteria require a status page?"
- answer: "SOC 2 Trust Services Criteria CC7.4 and CC7.5 require organizations to detect, communicate, and remediate security events and system availability issues. A status page with timestamped incident reports and subscriber notifications provides documented evidence of your incident communication process."
+ - question: "What SOC 2 criteria relate to incident communication?"
+ answer: "SOC 2's CC2.3 (Communication with external parties) requires you to demonstrate incident communication processes with external users — a mechanism to report failures, open communication channels, and documentation of how incidents are communicated. A status page with timestamped incident reports and subscriber notifications is the fastest way to satisfy this."
- question: "Do I need a status page specifically for SOC 2?"
- answer: "While SOC 2 doesn't mandate a status page by name, auditors expect documented evidence that you proactively communicate incidents to stakeholders. A status page is the most efficient way to satisfy this requirement and is increasingly considered standard practice."
+ answer: "No — SOC 2 CC2.3 requires you to demonstrate incident communication with external parties, but it doesn't prescribe a specific tool. You could use email notifications, a support portal, or other channels. That said, a status page is the fastest, most auditor-friendly way to satisfy the requirement and is increasingly considered standard practice."
- question: "What evidence does openstatus provide for auditors?"
answer: "Every status report, update, and resolution is timestamped and stored. You get a full incident history showing when issues were detected, communicated, and resolved. Subscriber notification logs show you proactively informed stakeholders. This creates an auditable trail without manual documentation."
- question: "Can I use openstatus alongside Vanta or Drata?"
@@ -19,9 +19,9 @@ faq:
## Why SOC 2 auditors care about incident communication
-SOC 2 Trust Services Criteria require you to **detect, communicate, and remediate** security events and system availability issues. Your auditor will ask: _"How do you notify stakeholders when something goes wrong?"_
+SOC 2's CC2.3 criteria (Communication with external parties) requires you to demonstrate incident communication processes — a mechanism for external users to report failures, open communication channels, and documentation of how incidents are communicated. Your auditor will ask: _"How do you notify stakeholders when something goes wrong?"_
-A status page is the most efficient answer. It provides **timestamped, documented evidence** that you proactively inform users about outages, maintenance, and degraded performance.
+SOC 2 doesn't prescribe a specific tool — you could use email, a support portal, or other channels. But a status page is the **fastest, most auditor-friendly** answer. It provides **timestamped, documented evidence** that you proactively inform users about outages, maintenance, and degraded performance.
## What auditors look for
@@ -64,7 +64,7 @@ For internal services or client-specific deployments, protect your status page w
4. Enable subscriber notifications
5. You're audit-ready
-Every paid plan includes custom domain, incident history, subscriber notifications, and password protection — everything you need for SOC 2 compliance.
+Every paid plan includes custom domain, incident history, subscriber notifications, and password protection — everything you need to satisfy SOC 2's incident communication requirements.
---