Skip to content

Open-source status page, incident response and uptime monitoring

chore: improve agent-first marketing visibility (#2710)

Maximilian Kaskea6887e1f3b80
diff --git a/README.md b/README.md
index 0d7cbb522..61a372ee2 100644
--- a/README.md
+++ b/README.md
@@ -26,7 +26,9 @@
## About openstatus
-openstatus is an open-source platform that combines **status pages** and **uptime monitoring** in a single tool. Keep your users informed and your services reliable. Available as a managed service or self-hosted.
+openstatus is the open-source **uptime monitoring** and **status page** platform built for **infra as code**. Declare monitors and status pages in code. Let your agents update them.
+
+Monitors, status pages, and notification channels are declared in YAML or Terraform, applied from the CLI or CI, and operable from Claude, ChatGPT, or Cursor over MCP. Available as a managed service or self-hosted.
<p align="center">
<img src="https://www.openstatus.dev/assets/landing/statuspage-meow.png" alt="openstatus status page" width="720" />
@@ -34,11 +36,12 @@ openstatus is an open-source platform that combines **status pages** and **uptim
## Why openstatus?
+- **Infra as code** — monitors, status pages, and notifications in YAML or Terraform, applied from the CLI or CI
+- **Built for humans and agents** — MCP server, `--json` CLI, typed API, read-only or read-write key scopes, every mutation in the audit log
- **Status pages + monitoring in one tool** — no need to wire up a separate monitoring service
- **28 global regions** checking in parallel across 3 cloud providers
- **Flat pricing, unlimited members** — no per-seat or per-subscriber charges
- **Open source & self-hostable** — AGPL-3.0, private-locations run in a single 8.5MB Docker image
-- **Monitoring as code** — YAML config, CLI, GitHub Actions, Terraform
- **Incident communication** — subscriber notifications via email, RSS, and webhooks
### Status pages
diff --git a/apps/web/src/app/(docs)/docs/[[...slug]]/page.tsx b/apps/web/src/app/(docs)/docs/[[...slug]]/page.tsx
index e80ed59ad..83bf051fa 100644
--- a/apps/web/src/app/(docs)/docs/[[...slug]]/page.tsx
+++ b/apps/web/src/app/(docs)/docs/[[...slug]]/page.tsx
@@ -49,7 +49,7 @@ const EDIT_BASE =
"https://github.com/openstatusHQ/openstatus/edit/main/apps/web/src/content/pages/docs";
const DOCS_DESCRIPTION =
- "Learn how to create your status page, monitor your endpoints, and configure notifications with openstatus.";
+ "Infra as code for uptime monitoring and status pages. Let your agents update them. Learn how to monitor your endpoints, create your status page, configure notifications, and drive it all from the CLI, Terraform, API, or MCP.";
type Params = { slug?: string[] };
diff --git a/apps/web/src/content/docs.config.ts b/apps/web/src/content/docs.config.ts
index 40577b4d6..d7828cde2 100644
--- a/apps/web/src/content/docs.config.ts
+++ b/apps/web/src/content/docs.config.ts
@@ -348,7 +348,7 @@ export function docsNavTree(): DocsNavNode {
label: "openstatus documentation",
href: "/docs",
description:
- "Learn how to create your status page, monitor your endpoints, and configure notifications.",
+ "Infra as code for uptime monitoring and status pages. Let your agents update them. Learn how to monitor your endpoints, create your status page, configure notifications, and drive it all from the CLI, Terraform, API, or MCP.",
children: docsNav.map((section) => {
const parent = sectionParentSlug(section);
return {
diff --git a/apps/web/src/content/llms-context.ts b/apps/web/src/content/llms-context.ts
index 88dd7e87a..24a530ef6 100644
--- a/apps/web/src/content/llms-context.ts
+++ b/apps/web/src/content/llms-context.ts
@@ -3,13 +3,14 @@
// Keep numbers in sync with src/content/pages/unrelated/pricing.mdx.
export const PRODUCT_SUMMARY =
- "Openstatus is an open-source uptime monitoring and status page platform. It runs synthetic checks in parallel from 28 regions across Fly.io, Koyeb, and Railway, surfaces incidents on branded status pages, and exposes a REST API plus MCP server for programmatic control. Available as managed SaaS or self-hosted (AGPL-3.0). Bootstrapped, founded in 2023.";
+ "Openstatus is an open-source uptime monitoring and status page platform built for infra as code: monitors, status pages, and notification channels are declared in YAML or Terraform and driven from a CLI, a typed API, or an MCP server (Claude, ChatGPT, Cursor), so your agents can update them. It runs synthetic checks in parallel from 28 regions across Fly.io, Koyeb, and Railway and surfaces incidents on branded status pages. Available as managed SaaS or self-hosted (AGPL-3.0). Bootstrapped, founded in 2023.";
export const PRODUCT_CONTEXT_MARKDOWN = `## Who it's for
+- Teams that manage uptime monitoring and status pages as infra as code and let agents (Claude, Cursor, ChatGPT, CI) open and resolve incidents over MCP, CLI, or API
- Development teams that want transparent incident communication
- Companies that need multi-region uptime monitoring
-- Teams that prefer infrastructure-as-code workflows (monitoring as code via YAML)
+- Teams that prefer infrastructure-as-code workflows (YAML via the CLI, or the Terraform provider)
- Organizations that require self-hosted monitoring behind a firewall (private locations)
- Open-source projects and startups looking for a free or affordable monitoring solution
@@ -28,16 +29,17 @@ Annual billing gives 2 months free (Starter $300/yr, Pro $1,000/yr, Scale $5,000
- **Multi-cloud** — Monitors run on Fly.io, Koyeb, and Railway for true cloud diversity
- **Status Pages** — Branded public or password-protected pages with custom domains, themes, maintenance windows, and subscriber notifications (email, RSS, Slack)
- **API Monitoring** — Assertions, thresholds, status code checks, header and body validation
-- **Monitoring as Code** — Define monitors in YAML, manage via CLI or GitHub Actions
+- **Infra as Code** — Define monitors, status pages, and notification channels in YAML (CLI, GitHub Actions) or Terraform
- **Private Locations** — 8.5MB Docker image for monitoring internal services behind firewalls
- **Alerting** — Email, Slack, Discord, webhook, WhatsApp, SMS, PagerDuty, OpsGenie, Grafana OnCall
- **OpenTelemetry** — Export synthetic check metrics to any OTLP endpoint
- **SDK** — Node.js SDK on JSR (@openstatus/sdk-node)
-- **MCP server** — Streamable-HTTP MCP at https://api.openstatus.dev/mcp for status reports, maintenance windows, and monitor reads
+- **MCP server** — Streamable-HTTP MCP at https://api.openstatus.dev/mcp with OAuth 2.1, for status reports, maintenance windows, and monitor reads; every mutation lands in the audit log
- **Open-source** — AGPL-3.0-licensed, self-hostable, 8k+ GitHub stars
## Key Differentiators
+- Built for humans and agents: MCP server, --json CLI output, typed API, read-only or read-write API key scopes
- Open-source and bootstrapped (no VC funding)
- Parallel scheduling — all selected regions check simultaneously (vs. round-robin competitors)
- Unlimited team members on paid plans
diff --git a/apps/web/src/content/pages/changelog/mcp-server.mdx b/apps/web/src/content/pages/changelog/mcp-server.mdx
index f2d54f1bb..5ea0325e5 100644
--- a/apps/web/src/content/pages/changelog/mcp-server.mdx
+++ b/apps/web/src/content/pages/changelog/mcp-server.mdx
@@ -15,6 +15,6 @@ Point your client at `https://api.openstatus.dev/mcp` with an `x-openstatus-key`
- **Create, update, and resolve status reports** — drive incidents from chat.
- **Schedule maintenance windows** — without leaving your editor.
-Every mutation requires an explicit `notify` choice, and every call is attributed to your API key in the audit log — so AI actions stay traceable.
+Every mutation requires an explicit `notify` choice and is attributed to your API key in the audit log — so AI actions stay traceable.
Head to the [MCP server reference](/docs/reference/mcp-server) for setup snippets and the full tool list.
diff --git a/apps/web/src/content/pages/home.mdx b/apps/web/src/content/pages/home.mdx
index 27be3bf5b..32e5a49fe 100644
--- a/apps/web/src/content/pages/home.mdx
+++ b/apps/web/src/content/pages/home.mdx
@@ -1,10 +1,10 @@
---
title: "Open Source Status Page & Uptime Monitoring"
-hero: "Ship your status page before your SOC 2 auditor asks for it"
+hero: "Keep your status page in code. Let your agents update it."
publishedAt: "2026-04-07"
-updatedAt: "2026-08-26"
+updatedAt: "2026-09-13"
author: "openstatus"
-description: "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."
+description: "Open-source status page and uptime monitoring. Declare monitors in your repo with Terraform or the CLI. Let agents open and resolve status reports over MCP, every mutation audited. Hosted or self-hosted."
category: "product"
faq:
- question: "What is openstatus?"
@@ -26,7 +26,7 @@ faq:
- question: "Does openstatus have an API?"
answer: "Yes. Openstatus exposes a typed JSON-over-HTTP API powered by ConnectRPC, with a published OpenAPI spec at api.openstatus.dev/openapi. Every action in the dashboard (managing monitors, status pages, status reports, maintenance windows, and notification channels) is reachable from the API. The same API key works across the API, CLI, Node SDK, Terraform provider, and MCP server, and every mutation lands in the audit log."
- question: "Can I manage openstatus from Claude or ChatGPT?"
- answer: "Yes. Openstatus ships a remote MCP (Model Context Protocol) server at api.openstatus.dev/mcp that connects Claude Desktop, ChatGPT, Cursor, and any MCP-compatible client to your workspace. The assistant can list status pages, create and resolve status reports, and schedule maintenance windows. Every publishing tool requires the assistant to explicitly choose whether to notify subscribers, and every call is recorded in the audit log."
+ answer: "Yes. Openstatus ships a remote MCP (Model Context Protocol) server at api.openstatus.dev/mcp that connects Claude Desktop, ChatGPT, Cursor, and any MCP-compatible client to your workspace. The assistant can list status pages, create and resolve status reports, and schedule maintenance windows. Every publishing tool requires the assistant to explicitly choose whether to notify subscribers, and every mutation is recorded in the audit log."
- question: "Can I manage monitors as code?"
answer: "Yes. Openstatus offers two ways to treat monitoring as code: a CLI with YAML config that lives in your repo (`openstatus monitors apply`), and a Terraform provider for HCL-managed infrastructure. Run `openstatus terraform generate` from the CLI to bootstrap an HCL file from an existing workspace."
---
@@ -48,6 +48,17 @@ Free to start. Paid plans from $30/mo. Open source and self-hostable.
<CustomerLogos />
+## Managing openstatus for humans and agents
+
+Every action in the dashboard is reachable programmatically. One API key, four ways in:
+
+- **[CLI](/tooling/cli)**: manage from your terminal
+- **[API](/tooling/api)**: typed HTTP endpoints with an [OpenAPI spec](https://api.openstatus.dev/openapi)
+- **[MCP server](/tooling/mcp-server)**: let Claude, ChatGPT, or Cursor run your monitoring
+- **[Terraform provider](/tooling/terraform)**: version monitors as HCL
+
+Read more about our [tooling](/tooling).
+
## 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.
@@ -60,17 +71,6 @@ Monitor your endpoints from 28 regions across multiple clouds. Get alerted on Sl
Read more about [uptime monitoring](/uptime-monitoring).
-## Managing openstatus for humans and agents
-
-Every action in the dashboard is reachable programmatically. One API key, four ways in:
-
-- **[CLI](/tooling/cli)**: manage from your terminal
-- **[API](/tooling/api)**: typed HTTP endpoints with an [OpenAPI spec](https://api.openstatus.dev/openapi)
-- **[MCP server](/tooling/mcp-server)**: let Claude, ChatGPT, or Cursor run your monitoring
-- **[Terraform provider](/tooling/terraform)**: version monitors as HCL
-
-Read more about our [tooling](/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.
@@ -222,7 +222,7 @@ Every action in the dashboard (managing monitors, status pages, status reports,
Yes. Openstatus ships a remote [MCP server](/tooling/mcp-server) at `api.openstatus.dev/mcp` that connects **Claude Desktop**, **ChatGPT**, **Cursor**, and any [Model Context Protocol](https://modelcontextprotocol.io) client to your workspace.
-The assistant can list status pages, create and resolve status reports, and schedule maintenance windows. Every publishing tool requires the assistant to explicitly choose whether to notify subscribers (models can't quietly fan out an alert), and every call is recorded in the audit log under `actor_type = 'mcp'`.
+The assistant can list status pages, create and resolve status reports, and schedule maintenance windows. Every publishing tool requires the assistant to explicitly choose whether to notify subscribers (models can't quietly fan out an alert), and every mutation is recorded in the audit log under `actor_type = 'mcp'`.
</Details>
diff --git a/apps/web/src/content/pages/product/tooling/mcp-server.mdx b/apps/web/src/content/pages/product/tooling/mcp-server.mdx
index d62ccd31c..5c9ea91dc 100644
--- a/apps/web/src/content/pages/product/tooling/mcp-server.mdx
+++ b/apps/web/src/content/pages/product/tooling/mcp-server.mdx
@@ -12,7 +12,7 @@ faq:
- question: "Do I need an API key to connect an MCP client?"
answer: "No. The MCP server is an OAuth 2.1 authorization server: Claude, ChatGPT, Cursor, and other clients open a consent screen where you pick a workspace and read-only or read & write access, and tokens are issued and refreshed automatically. The x-openstatus-key header still works for CI and headless agents, with the same key the CLI, API, and Terraform use."
- question: "Can the assistant accidentally notify subscribers?"
- answer: "No. Every publishing tool requires the assistant to set notify: true | false explicitly — there's no default. Metadata-only edits like update_status_report can't notify at all. Every call lands in the audit log under actor_type = 'mcp', so you can see exactly what happened."
+ answer: "No. Every publishing tool requires the assistant to set notify: true | false explicitly — there's no default. Metadata-only edits like update_status_report can't notify at all. Every mutation lands in the audit log under actor_type = 'mcp', so you can see exactly what happened."
---
The openstatus MCP server connects Claude Desktop, ChatGPT, Cursor, and any other [Model Context Protocol](https://modelcontextprotocol.io) client to your workspace — so an AI assistant can read monitors, response logs, and audit history, and drive status pages, status reports, and maintenance windows directly from a conversation.
@@ -92,6 +92,6 @@ No. The MCP server is an OAuth 2.1 authorization server: Claude, ChatGPT, Cursor
<Details summary="Can the assistant accidentally notify subscribers?">
-No. Every publishing tool requires the assistant to set notify: true | false explicitly — there's no default. Metadata-only edits like update_status_report can't notify at all. Every call lands in the audit log under actor_type = 'mcp', so you can see exactly what happened.
+No. Every publishing tool requires the assistant to set notify: true | false explicitly — there's no default. Metadata-only edits like update_status_report can't notify at all. Every mutation lands in the audit log under actor_type = 'mcp', so you can see exactly what happened.
</Details>
diff --git a/apps/web/src/content/pages/use-case/agent.mdx b/apps/web/src/content/pages/use-case/agent.mdx
index 875ec0e3c..05036234b 100644
--- a/apps/web/src/content/pages/use-case/agent.mdx
+++ b/apps/web/src/content/pages/use-case/agent.mdx
@@ -12,7 +12,7 @@ faq:
- question: "Which MCP tools matter for incident response?"
answer: "The diagnostic loop uses get_monitor, get_monitor_status, get_monitor_summary, list_response_logs, and get_response_log. The communication loop uses list_status_pages, list_page_components, create_status_report, add_status_report_update, and resolve_status_report. The agent can also call list_audit_logs to see what humans or other agents already did."
- question: "Can the agent post a status report without a human in the loop?"
- answer: "Yes — but every mutation tool requires the agent to explicitly decide whether to notify subscribers, and every call is recorded in the audit log with the agent's API key as the actor. Read-only keys can investigate but cannot publish. Most teams start with notify_subscribers set to false and a human approving the first version, then graduate to fully autonomous reports once the agent has a track record."
+ answer: "Yes — but every mutation tool requires the agent to explicitly decide whether to notify subscribers, and each one is recorded in the audit log with the agent's API key as the actor. Read-only keys can investigate but cannot publish. Most teams start with notify_subscribers set to false and a human approving the first version, then graduate to fully autonomous reports once the agent has a track record."
- question: "How do I scope what the agent can do?"
answer: "Openstatus API keys carry scopes — read for investigation-only, write for mutations. Issue a read-only key for an agent that only diagnoses, or a write-scoped key for an agent that also files status reports. Scope enforcement happens before any DB lookup, so a read-only key never sees the write tools."
---
@@ -129,7 +129,7 @@ The agent keeps watching. When `get_monitor_status` flips green:
- **`add_status_report_update`** — post a "monitoring" or "identified" update with the latest diagnosis
- **`resolve_status_report`** — close the report when the monitor recovers
-Every call lands in the openstatus audit log with the API key as the actor. You can replay exactly what the agent did, when, and to what.
+Every mutation lands in the openstatus audit log with the API key as the actor. You can replay exactly what the agent did, when, and to what.
## Why this works on openstatus specifically
@@ -180,7 +180,7 @@ The diagnostic loop uses get_monitor, get_monitor_status, get_monitor_summary, l
<Details summary="Can the agent post a status report without a human in the loop?">
-Yes — but every mutation tool requires the agent to explicitly decide whether to notify subscribers, and every call is recorded in the audit log with the agent's API key as the actor. Read-only keys can investigate but cannot publish. Most teams start with notify_subscribers set to false and a human approving the first version, then graduate to fully autonomous reports once the agent has a track record.
+Yes — but every mutation tool requires the agent to explicitly decide whether to notify subscribers, and each one is recorded in the audit log with the agent's API key as the actor. Read-only keys can investigate but cannot publish. Most teams start with notify_subscribers set to false and a human approving the first version, then graduate to fully autonomous reports once the agent has a track record.
</Details>
diff --git a/apps/web/src/lib/metadata/shared-metadata.ts b/apps/web/src/lib/metadata/shared-metadata.ts
index 3a04ffdd2..cc6ccc4c3 100644
--- a/apps/web/src/lib/metadata/shared-metadata.ts
+++ b/apps/web/src/lib/metadata/shared-metadata.ts
@@ -5,9 +5,9 @@ import type { MDXData } from "../../content/utils";
export const TITLE = "openstatus";
export const HOMEPAGE_TITLE = "Free & Open Source Status Page ";
export const DESCRIPTION =
- "Ship your status page before your SOC 2 auditor asks for it. Open source, free to start, self-hostable.";
+ "Keep your status page in code. Let your agents update it. Open source, free to start, self-hostable.";
-export const OG_DESCRIPTION = "The status page for compliance-ready teams";
+export const OG_DESCRIPTION = "The status page for humans and agents";
export const BASE_URL =
process.env.NODE_ENV === "production"
diff --git a/apps/web/src/lib/metadata/structured-data.ts b/apps/web/src/lib/metadata/structured-data.ts
index e5c957b6f..c5b9b6159 100644
--- a/apps/web/src/lib/metadata/structured-data.ts
+++ b/apps/web/src/lib/metadata/structured-data.ts
@@ -185,7 +185,7 @@ export const getJsonLDProduct = (): WithContext<Product> => {
"@type": "Product",
name: "openstatus",
description:
- "The open-source status page and uptime monitoring platform trusted by growing teams.",
+ "The open-source status page and uptime monitoring platform built for infra as code. Declare monitors in code and let your agents update them.",
image: `${BASE_URL}/assets/logos/OpenStatus-Logo.svg`,
url: BASE_URL,
brand: {
@@ -213,7 +213,7 @@ export const getJsonLDSoftwareApplication =
name: "openstatus",
url: BASE_URL,
description:
- "The open-source status page and uptime monitoring platform trusted by growing teams.",
+ "The open-source status page and uptime monitoring platform built for infra as code. Declare monitors in code and let your agents update them.",
applicationCategory: "BusinessApplication",
applicationSubCategory: "Status Pages & Uptime Monitoring",
operatingSystem: "Web, Self-hosted",