Open-source status page, incident response and uptime monitoring
TypeScript alertingincident-managementmcpmcp-servermonitoringmonitoring-as-codeobservabilityon-callopen-sourcesrestatus-pagestatuspagesynthetic-monitoringterraformtinybirdtursouptimeuptime-checkeruptime-monitor
chore: compliance positioning (#1978)
Maximilian Kaske644a873a8456
diff --git a/apps/dashboard/src/data/plans.ts b/apps/dashboard/src/data/plans.tsindex f88d01d14..39040fa32 100644--- a/apps/dashboard/src/data/plans.ts+++ b/apps/dashboard/src/data/plans.ts@@ -17,33 +17,6 @@ export const config: Record<}[];}> = {- monitors: {- label: "Monitors",- features: [- {- value: "periodicity",- label: "Frequency",- },- {- value: "monitors",- label: "Number of monitors",- },- {- value: "multi-region",- label: "Multi-region monitoring",- },- { value: "regions", label: "Total regions" },- { value: "max-regions", label: "Regions per monitor" },- { value: "data-retention", label: "Data retention" },- { value: "response-logs", label: "Response Logs" },- { value: "otel", label: "OTel Exporter" },- {- value: "synthetic-checks",- label: "Synthetic API Checks",- monthly: true,- },- ],- },"status-pages": {label: "Status Pages",features: [@@ -94,6 +67,33 @@ export const config: Record<},],},+ monitors: {+ label: "Monitors",+ features: [+ {+ value: "periodicity",+ label: "Frequency",+ },+ {+ value: "monitors",+ label: "Number of monitors",+ },+ {+ value: "multi-region",+ label: "Multi-region monitoring",+ },+ { value: "regions", label: "Total regions" },+ { value: "max-regions", label: "Regions per monitor" },+ { value: "data-retention", label: "Data retention" },+ { value: "response-logs", label: "Response Logs" },+ { value: "otel", label: "OTel Exporter" },+ {+ value: "synthetic-checks",+ label: "Synthetic API Checks",+ monthly: true,+ },+ ],+ },notifications: {label: "Notifications",features: [diff --git a/apps/web/next.config.ts b/apps/web/next.config.tsindex 5a12cef93..44e62a1a4 100644--- a/apps/web/next.config.ts+++ b/apps/web/next.config.ts@@ -71,6 +71,21 @@ const nextConfig: NextConfig = {destination: "/status-page",permanent: true,},+ {+ source: "/api-monitoring",+ destination: "/uptime-monitoring",+ permanent: true,+ },+ {+ source: "/monitoring-as-code",+ destination: "/uptime-monitoring",+ permanent: true,+ },+ {+ source: "/private-locations",+ destination: "/uptime-monitoring",+ permanent: true,+ },{source: "/app/:path*",destination: "https://app.openstatus.dev/",diff --git a/apps/web/public/assets/landing/statuspage-meow.dark.png b/apps/web/public/assets/landing/statuspage-meow.dark.pngnew file mode 100644index 000000000..930fefea4Binary files /dev/null and b/apps/web/public/assets/landing/statuspage-meow.dark.png differdiff --git a/apps/web/public/assets/landing/statuspage-meow.png b/apps/web/public/assets/landing/statuspage-meow.pngnew file mode 100644index 000000000..56e218f31Binary files /dev/null and b/apps/web/public/assets/landing/statuspage-meow.png differdiff --git a/apps/web/src/app/(landing)/use-case/[slug]/page.tsx b/apps/web/src/app/(landing)/use-case/[slug]/page.tsxnew file mode 100644index 000000000..51acdef82--- /dev/null+++ b/apps/web/src/app/(landing)/use-case/[slug]/page.tsx@@ -0,0 +1,107 @@+import { CustomMDX } from "@/content/mdx";+import { getUseCasePages } from "@/content/utils";+import { BASE_URL, getPageMetadata } from "@/lib/metadata/shared-metadata";+import {+ createJsonLDGraph,+ getJsonLDBlogPosting,+ getJsonLDBreadcrumbList,+ getJsonLDFAQPage,+ getJsonLDHowTo,+ getJsonLDOrganization,+ getJsonLDWebPage,+} from "@/lib/metadata/structured-data";+import type { Metadata } from "next";+import Image from "next/image";+import { notFound } from "next/navigation";+import { ContentMetadata } from "../../content-metadata";+import { ContentPagination } from "../../content-pagination";++export const dynamicParams = false;++export async function generateStaticParams() {+ const posts = getUseCasePages();++ return posts.map((post) => ({+ slug: post.slug,+ }));+}++export async function generateMetadata({+ params,+}: {+ params: Promise<{ slug: string }>;+}): Promise<Metadata | undefined> {+ const { slug } = await params;+ const post = getUseCasePages().find((post) => post.slug === slug);+ if (!post) {+ return;+ }++ const metadata = getPageMetadata(post, "use-case");++ return metadata;+}++export default async function UseCase({+ params,+}: {+ params: Promise<{ slug: string }>;+}) {+ const { slug } = await params;+ const posts = getUseCasePages().sort(+ (a, b) =>+ b.metadata.publishedAt.getTime() - a.metadata.publishedAt.getTime(),+ );+ const postIndex = posts.findIndex((post) => post.slug === slug);+ const post = posts[postIndex];+ const previousPost = posts[postIndex - 1];+ const nextPost = posts[postIndex + 1];++ if (!post) {+ notFound();+ }++ const jsonLDGraph = createJsonLDGraph([+ getJsonLDOrganization(),+ getJsonLDWebPage(post),+ getJsonLDBlogPosting(post, "use-case"),+ getJsonLDBreadcrumbList([+ { name: "Home", url: BASE_URL },+ { name: "Use Cases", url: `${BASE_URL}/use-case` },+ { name: post.metadata.title, url: `${BASE_URL}/use-case/${slug}` },+ ]),+ getJsonLDHowTo(post),+ getJsonLDFAQPage(post),+ ]);++ return (+ <section className="prose dark:prose-invert max-w-none">+ <script+ type="application/ld+json"+ suppressHydrationWarning+ // biome-ignore lint/security/noDangerouslySetInnerHtml: jsonLd+ dangerouslySetInnerHTML={{+ __html: JSON.stringify(jsonLDGraph).replace(/</g, "\\u003c"),+ }}+ />+ <h1>{post.metadata.title}</h1>+ <ContentMetadata data={post} />+ {post.metadata.image ? (+ <div className="relative aspect-video w-full overflow-hidden border border-border">+ <Image+ src={post.metadata.image}+ alt={post.metadata.title}+ fill+ className="object-contain"+ />+ </div>+ ) : null}+ <CustomMDX source={post.content} />+ <ContentPagination+ previousPost={previousPost}+ nextPost={nextPost}+ prefix="/use-case"+ />+ </section>+ );+}diff --git a/apps/web/src/app/(landing)/use-case/page.tsx b/apps/web/src/app/(landing)/use-case/page.tsxnew file mode 100644index 000000000..d1bff7b29--- /dev/null+++ b/apps/web/src/app/(landing)/use-case/page.tsx@@ -0,0 +1,39 @@+import { getUseCasePages } from "@/content/utils";+import { defaultMetadata, ogMetadata } from "@/lib/metadata/shared-metadata";+import { twitterMetadata } from "@/lib/metadata/shared-metadata";+import type { Metadata } from "next";+import { ContentList } from "../content-list";++const TITLE = "Use Cases";+const DESCRIPTION =+ "Discover how teams use OpenStatus for compliance, open-source projects, crypto exchanges, and API infrastructure.";++export const metadata: Metadata = {+ ...defaultMetadata,+ title: TITLE,+ description: DESCRIPTION,+ alternates: {+ canonical: "/use-case",+ },+ openGraph: {+ ...ogMetadata,+ title: TITLE,+ description: DESCRIPTION,+ },+ twitter: {+ ...twitterMetadata,+ title: TITLE,+ description: DESCRIPTION,+ images: [`/api/og?title=${TITLE}&description=${DESCRIPTION}`],+ },+};++export default function UseCaseListPage() {+ const allUseCases = getUseCasePages();+ return (+ <div className="prose dark:prose-invert max-w-none">+ <h1>Use Cases</h1>+ <ContentList data={allUseCases} prefix="/use-case" withCategory />+ </div>+ );+}diff --git a/apps/web/src/app/api/search/route.ts b/apps/web/src/app/api/search/route.tsindex ab065bba5..665bc3efc 100644--- a/apps/web/src/app/api/search/route.ts+++ b/apps/web/src/app/api/search/route.ts@@ -71,6 +71,7 @@ function search(params: SearchParams) {...getPages("compare"),...getPages("product"),...getPages("guides"),+ ...getPages("use-case"),...getPages("unrelated"),home,];diff --git a/apps/web/src/app/sitemap.ts b/apps/web/src/app/sitemap.tsindex 8694a7288..aeed9f1ad 100644--- a/apps/web/src/app/sitemap.ts+++ b/apps/web/src/app/sitemap.ts@@ -7,6 +7,7 @@ import {getProductPages,getToolsPages,getUnrelatedPages,+ getUseCasePages,} from "@/content/utils";import type { MetadataRoute } from "next";@@ -21,6 +22,7 @@ const allPlaygrounds = getToolsPages().filter((tool) => tool.slug !== "checker-slug",);const allGuides = getGuides();+const allUseCases = getUseCasePages();export default function sitemap(): MetadataRoute.Sitemap {const blogs = allPosts.map((post) => ({@@ -81,6 +83,13 @@ export default function sitemap(): MetadataRoute.Sitemap {},];+ const useCases = allUseCases.map((useCase) => ({+ url: `https://www.openstatus.dev/use-case/${useCase.slug}`,+ lastModified: useCase.metadata.publishedAt,+ changeFrequency: "monthly" as const,+ priority: 0.8,+ }));+return [...home,...blogs,@@ -90,5 +99,6 @@ export default function sitemap(): MetadataRoute.Sitemap {...products,...playgrounds,...guides,+ ...useCases,];}diff --git a/apps/web/src/content/cmdk.tsx b/apps/web/src/content/cmdk.tsxindex 123537a50..4d99d3f19 100644--- a/apps/web/src/content/cmdk.tsx+++ b/apps/web/src/content/cmdk.tsx@@ -114,6 +114,12 @@ const CONFIG: ConfigSection[] = [heading: "Guides",page: "guides",},+ {+ type: "group",+ label: "Search in Use Cases...",+ heading: "Use Cases",+ page: "use-case",+ },{type: "item",label: "Go to About",diff --git a/apps/web/src/content/listing.ts b/apps/web/src/content/listing.tsindex ccbc28ba5..1013106c1 100644--- a/apps/web/src/content/listing.ts+++ b/apps/web/src/content/listing.ts@@ -5,6 +5,7 @@ import {getChangelogPosts,getComparePages,getGuides,+ getUseCasePages,} from "./utils";/**@@ -32,6 +33,8 @@ export function generateListingForPath(pathname: string): string | null {return generatePostsList(getComparePages(), "Comparisons");case "guides":return generatePostsList(getGuides(), "Guides");+ case "use-case":+ return generatePostsList(getUseCasePages(), "Use Cases");default:return null;}@@ -102,6 +105,7 @@ function generateRootListing(): string {{ title: "Changelog", posts: getChangelogPosts(), path: "/changelog" },{ title: "Comparisons", posts: getComparePages(), path: "/compare" },{ title: "Guides", posts: getGuides(), path: "/guides" },+ { title: "Use Cases", posts: getUseCasePages(), path: "/use-case" },];const content = sectionsdiff --git a/apps/web/src/content/pages/home.mdx b/apps/web/src/content/pages/home.mdxindex ce85c30e4..11fd550cd 100644--- a/apps/web/src/content/pages/home.mdx+++ b/apps/web/src/content/pages/home.mdx@@ -1,24 +1,24 @@----title: "The open-source status page with uptime monitoring"+title: "Ship your status page before your SOC 2 auditor asks for it"publishedAt: "2025-11-10"author: "openstatus"-description: "Openstatus helps you communicate openly during incidents. Share what's happening, keep users updated, and let your status page automatically populate real-time data from our uptime monitoring solution."+description: "The open-source status page trusted by growing teams. Communicate incidents, prove compliance readiness, and monitor uptime from 28 global regions."category: "product"faq:- question: "What is openstatus?"- answer: "Openstatus is an open-source uptime monitoring and status page platform. It monitors websites, APIs, and services from 28 regions globally across multiple cloud providers (Fly.io, Koyeb, Railway), helping teams detect downtime immediately and communicate incidents through branded status pages. Openstatus is bootstrapped, not VC-funded, and available as a managed SaaS or for self-hosting."+ 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."+ - 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?"answer: "The free plan includes one monitor, one status page with three page components, and a minimum check interval of 10 minutes. No credit card is required, and you can upgrade or cancel at any time."- question: "Who is behind openstatus?"- answer: "Openstatus is built by Thibault and Max, a bootstrapped two-person team. They share their journey openly — learn more on the about page."- - question: "How does uptime monitoring work?"- answer: "Openstatus pings your endpoints from multiple regions at your configured interval to calculate uptime and response times. It validates responses using assertions (status codes, headers, body content) and alert thresholds. Results appear on your dashboard and automatically reflect on your status page. You can also export metrics to OpenTelemetry."+ answer: "Openstatus is built by Thibault and Max, a bootstrapped two-person team. We're profitable and self-funded — we'll be here when your next audit comes around."- question: "What regions does openstatus monitor from?"answer: "Openstatus monitors from 28 regions worldwide: 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), and Oceania (Sydney)."- question: "Can I self-host openstatus?"answer: "Yes. Openstatus is fully open source and can be self-hosted using its 8.5MB Docker image. You can also deploy private monitoring locations behind your firewall for internal services. The source code is available on GitHub."- - question: "How can I contribute to openstatus?"- answer: "Star the project on GitHub, report bugs, suggest features, contribute code, or become a paid user. You can also spread the word or join the Discord community."---<div className="space-x-2">@@ -30,19 +30,23 @@ faq:/></div>-<Image src="/assets/landing/dashboard.png" alt="dashboard monitor overview" priority />+<Image src="/assets/landing/statuspage-meow.png" alt="statuspage" priority />-## Trusted by teams who value transparency+## Trusted by teams who ship transparency<Grid cols={4}>- <a href="https://cal.com">Cal.com</a>- <a href="https://documenso.com">Documenso</a>- <a href="https://tigrisdata.com">TigrisData</a>- <a href="https://midday.ai">Midday</a>- <a href="https://openpanel.dev">OpenPanel</a>- <a href="https://getprobo.com">Probo</a>- <a href="https://hanko.io">Hanko</a>- <a href="https://superwall.com">Superwall</a>+ <a href="https://status.cal.com">Cal.com</a>+ <a href="https://status.documenso.com">Documenso</a>+ <a href="https://status.whitebit.com">WhiteBIT</a>+ <a href="https://status.midday.ai">Midday</a>+ <a href="https://status.openpanel.dev">OpenPanel</a>+ <a href="https://probostatus.com">Probo</a>+ <a href="https://status.hanko.io">Hanko</a>+ <a href="https://status.superwall.com">Superwall</a>+ <a href="https://status.streamelements.com/">StreamElements</a>+ <a href="https://status.smplrspace.com">Smplrspace</a>+ <a href="https://passboltuptime.com">Passbolt</a>+ <a href="https://twenty-status.com">TwentyCRM</a></Grid>## Beautiful, open-source status pages@@ -72,7 +76,7 @@ Get a real picture with **28 regions** across multiple clouds. Validate your API- **Integrations**: OpenTelemetry export, notification channels (email, Slack, Discord, etc.)- Check all regions in our [global speed checker](/play/checker)-Read more about [uptime monitoring](/uptime-monitoring), [API monitoring](/api-monitoring), [monitoring as code](/monitoring-as-code), and [private locations](/private-locations).+Read more about [uptime monitoring](/uptime-monitoring).---@@ -108,12 +112,34 @@ Check your website's latency<Details summary="What is openstatus?">-Openstatus is an open-source uptime monitoring and status page platform. It monitors websites, APIs, and services from **28 regions** globally across multiple cloud providers (Fly.io, Koyeb, Railway), helping teams detect downtime immediately and communicate incidents through branded status pages.+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 is bootstrapped, not VC-funded, and 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?">++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.++With openstatus, every status report and update is **timestamped** and documented automatically — giving you an auditable trail of how you communicate during incidents.++</Details>++<Details summary="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++You can be SOC 2-ready in minutes, not weeks.++</Details>+<Details summary="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`. Check the pricing table for a full comparison.@@ -126,6 +152,8 @@ No credit card required — upgrade or cancel at any time.Openstatus is built by [Thibault](https://bsky.app/profile/thibaultleouay.dev) and [Max](https://x.com/mxkaske) — a bootstrapped two-person team building in public.+We're profitable and self-funded — we'll be here when your next audit comes around.+Read more on [our about page](/about).<Grid>@@ -136,17 +164,6 @@ Read more on [our about page](/about).</Details>--<Details summary="How does uptime monitoring work?">--Openstatus pings your endpoints from multiple regions at your configured interval. Each check validates the response using **assertions** (status codes, headers, body content) and **alert thresholds**. Response time data — including timing phases like DNS, connect, and TTFB — is collected and displayed on your dashboard.--When a check fails, you get notified immediately via your chosen channel (email, Slack, Discord, PagerDuty, and more). Your status page reflects the current state automatically.--Try the [Speed Checker](/play/checker) to see real-time data from all regions.--</Details>-<Details summary="What regions does openstatus monitor from?">Openstatus monitors from **28 regions worldwide** across all continents:@@ -189,16 +206,3 @@ Yes. Openstatus is fully open source and can be self-hosted using its **8.5MB DoThe source code is available on [GitHub](https://openstatus.dev/github).</Details>--<Details summary="How can I contribute to openstatus?">--There are many ways to support the project:--- **Star on GitHub**: Show your support and help others discover it.-- **Spread the word**: Tell your team or write about your experience.-- **Report bugs**: Found something broken? [Open an issue](https://openstatus.dev/github).-- **Suggest features**: Have an idea? Let us know on [Discord](https://openstatus.dev/discord) or [GitHub](https://openstatus.dev/github).-- **Contribute code**: Pull requests are welcome.-- **Become a paid user**: The best way to sustain an indie project.--</Details>\ No newline at end of filediff --git a/apps/web/src/content/pages/product/api-monitoring.mdx b/apps/web/src/content/pages/product/api-monitoring.mdxdeleted file mode 100644index 445d37c0f..000000000--- a/apps/web/src/content/pages/product/api-monitoring.mdx+++ /dev/null@@ -1,95 +0,0 @@-----title: "API Monitoring"-publishedAt: "2025-11-10"-author: "openstatus"-description: "Monitor REST, GraphQL, and webhook endpoints from 28 global regions. Validate status codes, headers, and response bodies with assertions and alert thresholds. Open source."-category: "Product"-faq:- - question: "What types of API endpoints can I monitor?"- answer: "You can monitor any HTTP/HTTPS endpoint including REST APIs, GraphQL APIs, webhooks, and third-party service endpoints. OpenStatus supports all HTTP methods (GET, POST, PUT, DELETE, etc.) and custom headers for authentication."- - question: "How do assertions work in API monitoring?"- answer: "Assertions let you validate API responses beyond just checking if the endpoint is reachable. You can validate status codes (e.g., expect 200), check for specific text in response bodies, or verify header values. This ensures your API returns correct data, not just any response."- - question: "What's the difference between internal monitoring tools and OpenStatus?"- answer: "Internal tools like Grafana or Signoz monitor from inside your infrastructure and see your services as your servers see them. OpenStatus monitors from external locations worldwide, showing you what your customers actually experience including network issues, CDN problems, and geographic latency."- - question: "Can I export monitoring data to my existing observability stack?"- answer: "Yes, OpenStatus supports OpenTelemetry (OTLP) export. You can send monitoring metrics to your existing tools like Grafana, Honeycomb, or Datadog, allowing you to combine external monitoring data with your internal metrics and set custom alerts."------## Why monitor your API from an external providers?--Internally you might already have a Grafana, or Signoz deployed. They are working great to monitor your internal metrics, but they are not able to monitor from an external point of view.--With openstatus you can monitor your API from multiple regions around the world, and be sure that your customers are able to reach your API.--<Grid>-<div>--**Monitoring Dashboard**--<Image src="/assets/landing/dashboard.png" alt="dashboard monitor charts" />--</div>-<div>--**Response Logs**--<Image src="/assets/landing/dashboard-logs.png" alt="dashboard monitor logs" />--</div>-</Grid>--## Why choose openstatus for API monitoring?--### Assertions--Validating your response can be important. You can do **status code**, **header** or **body text** assertions. Read more [in the docs](https://docs.openstatus.dev/reference/http-monitor/#assertions).--### Thresholds--You can set a **degraded at** and **timeout** threshold whenever required. We will send you a notification whenever the responses exceed the thresholds.--### Open Telemetry--When needed, you can export to your **OTLP endpoint** the metrics for every request we do. Access the data and set yourself an **alert channel** in Grafana, Honeycomb etc.. Read more [in our guide](https://docs.openstatus.dev/guides/how-to-export-metrics-to-otlp-endpoint/).--### Private locations--You can **deploy our probes** on your own VPC, [Cloudflare Containers](https://docs.openstatus.dev/guides/how-to-deploy-probes-cloudflare-containers/) and more. It is **8.5MB small** and fits even on a [Raspberry Pi 3](/blog) with ease. Read more [in the docs](https://docs.openstatus.dev/tutorial/how-to-create-private-location/).--### CLI--You can manage or trigger your monitors via CLI. We provide a simple [GitHub Action](https://github.com/marketplace/actions/openstatus-synthetics-ci) to run it in your **CI/CD**.--```-+------------------------------------------------------------------------------------------+-| dwightschrute@computer ~ > openstatus |-| |-| NAME: |-| OpenStatus - This is OpenStatus Command Line Interface |-| |-| USAGE: |-| OpenStatus [global options] [command [command options]] [arguments...] |-| |-| VERSION: |-| v0.0.7 |-| |-| COMMANDS: |-| monitors Manage your monitors |-| run, r Run your synthetics tests defined in your configuration file |-| whoami, w Get your current workspace Information |-| help, h Shows a list of commands or help for one command |-| |-| GLOBAL OPTIONS: |-| --help, -h show help |-| --version, -v print the version |-| |-+------------------------------------------------------------------------------------------+-```-------Check your website's latency--<ButtonLink href="/play/checker">Global Speed Checker</ButtonLink>-----diff --git a/apps/web/src/content/pages/product/monitoring-as-code.mdx b/apps/web/src/content/pages/product/monitoring-as-code.mdxdeleted file mode 100644index 4cb05e5f9..000000000--- a/apps/web/src/content/pages/product/monitoring-as-code.mdx+++ /dev/null@@ -1,88 +0,0 @@-----title: "Monitoring as Code"-publishedAt: "2025-11-10"-author: "Maximilian Kaske"-description: "Define your monitors as YAML configuration files, manage them with the OpenStatus CLI, and automate deployments with GitHub Actions. Version control your monitoring setup."-category: "Product"-howto:- totalTime: "PT15M"- steps:- - name: "Create a YAML configuration file"- text: "Create a monitoring configuration file (e.g., openstatus.yaml) in your repository. Define your monitors with regions, frequency, and request details using our YAML schema."- url: "#yaml--cli"- - name: "Install the OpenStatus CLI"- text: "Install the OpenStatus CLI tool to your local environment or CI/CD pipeline. Authenticate with your API key to connect to your workspace."- url: "https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/"- - name: "Apply your configuration"- text: "Run 'openstatus monitors apply' to sync your YAML configuration with OpenStatus. The CLI will create or update monitors based on your config file."- url: "#yaml--cli"- - name: "Commit and version control"- text: "Commit your monitoring configuration to git. All changes to your monitors are now tracked, reviewable, and can be rolled back just like your application code."- url: "#what-are-the-benefits-of-monitoring-as-code"-faq:- - question: "Should I use YAML with CLI or Terraform for monitoring as code?"- answer: "Use YAML + CLI for simplicity and if you're not already using Terraform. It's lightweight and easy to get started. Choose Terraform if you're managing infrastructure as code and want to integrate monitoring into your existing Terraform workflows for unified state management."- - question: "Can I manage monitors both via UI and via code?"- answer: "Yes, but we recommend choosing one primary method to avoid conflicts. If you apply a YAML config, it will sync the monitors defined in that file. Monitors created only in the UI won't be affected unless you add them to your YAML config."- - question: "How do I handle sensitive data like API tokens in my YAML config?"- answer: "Never commit tokens directly to git. Use environment variables or secret management tools. In CI/CD, store tokens as encrypted secrets. For local development, use .env files (and add them to .gitignore) or reference secrets from your secret manager."- - question: "What happens when I apply changes to an existing monitor?"- answer: "The CLI updates the existing monitor with your new configuration. Historical monitoring data is preserved. If you change the monitor name, it will create a new monitor instead of updating, so use unique identifiers consistently."------## What are the benefits of monitoring as code?--When you set your monitoring from an external providers. You can set and forget it easily, with monitoring as code your monitoring lives in your git repository. All your team knows about it.--**Version controlling** the changes helps you keep track changes over time, review the monitors or roll back to previous configs.--## Why choose openstatus for uptime monitoring as code?--### YAML + CLI--We use `YAML` to define your monitoring configuration. `YAML` is a human friendly data serialization standard that can be used in conjunction with all programming languages and is often used to write configuration files.--```yaml-# yaml-language-server: $schema=https://www.openstatus.dev/schema.json-uptime-monitor:- name: "Graphql"- description: "GitHub GraphQL API"- frequency: "10m"- active: true- regions:- - iad- - ams- - syd- - jnb- - gru- retry: 3- kind: http- request:- url: https://api.github.com/graphql- method: POST- headers:- User-Agent: OpenStatus- Authorization: Bearer YOUR_TOKEN_HERE- body: |- {- "query": "query { viewer { login }}"- }-```--Once set, apply your changes via [CLI](https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/):--```bash-openstatus monitors apply-```--Check our [GitHub repository](https://github.com/openstatusHQ/cli-template) to see the `YAML` templates of how to monitor **MCP**, **GraphQL**,... endpoints.--### Terraform Provider--You can define monitors as **Terraform resources**, integrate with your existing IaC setup, and let Terraform handle the state management.--Check out the [Terraform Provider](https://registry.terraform.io/providers/openstatusHQ/openstatus/latest) on the Terraform Registry.--### Team Collaboration--We are not limiting our paid plans to any number of members. Let everyone in your team update your monitors and check the responses in the dashboard. Read more [about api monitoring](/api-monitoring).diff --git a/apps/web/src/content/pages/product/private-locations.mdx b/apps/web/src/content/pages/product/private-locations.mdxdeleted file mode 100644index 5feff3354..000000000--- a/apps/web/src/content/pages/product/private-locations.mdx+++ /dev/null@@ -1,64 +0,0 @@-----title: "Private Locations"-publishedAt: "2025-11-10"-author: "Thibault Le Ouay Ducasse"-description: "Deploy a lightweight 8.5MB Docker image to monitor internal services behind your firewall. Check APIs and endpoints not exposed to the public internet from your own infrastructure."-category: "Product"-howto:- totalTime: "PT10M"- steps:- - name: "Create a private location in OpenStatus"- text: "In your OpenStatus dashboard, create a new private location and generate an API key. This key will authenticate your probe with the OpenStatus platform."- url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"- - name: "Deploy the Docker container"- text: "Pull the private location Docker image (ghcr.io/openstatushq/private-location:latest) and run it with your API key in your infrastructure, VPC, or cloud provider."- url: "#docker-container"- - name: "Verify the connection"- text: "Check your OpenStatus dashboard to confirm the private location is connected and receiving updates. The probe will automatically sync with your monitors every few minutes."- url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"- - name: "Assign monitors to the private location"- text: "Update your monitors to use the private location region. The probe will now run checks from inside your network on the defined schedule."- url: "https://docs.openstatus.dev/tutorial/how-to-create-private-location/"-faq:- - question: "Why is the Docker image only 8.5MB?"- answer: "We keep it minimal by excluding browser-based checks and bundling only the HTTP monitoring engine. This allows deployment on resource-constrained devices like Raspberry Pis while maintaining full API monitoring capabilities."- - question: "Can I run multiple private locations in different networks?"- answer: "Yes, you can deploy as many private location probes as needed across different networks, VPCs, or regions. Each gets its own API key and appears as a separate monitoring region in your dashboard."- - question: "What platforms support the private location Docker image?"- answer: "The image supports both ARM64 and AMD64 architectures, running on any Docker-compatible platform including cloud providers (AWS, GCP, Azure), Cloudflare Containers, Kubernetes, Raspberry Pi, and standard Linux servers."- - question: "How does the probe communicate with OpenStatus?"- answer: "The probe makes outbound connections to OpenStatus to fetch monitor configurations and send results. It doesn't require inbound connections or firewall changes, making it safe to run in restricted networks."------Sometimes the services you want to monitor are not accessible from the outside, you want to be able to monitor from your own network.--## Why private locations are important?--Private locations let you monitor internal or restricted services that aren’t reachable from the public internet. They run checks from inside your own network or infrastructure, giving you visibility into systems behind firewalls, or VPCs.--## Why choose openstatus for private locations?--### Deploy everywhere--Simply **deploy our probes** to your favorite **cloud provider**, your own **server** or on your own **virtual private cloud** (VPC).--The docker image is only **8.5MB** small and should easily fit on your infrastructure whether ARM64 or AMD64. We don't provide browser checks and can keep it this small.--- [Cloudflare Containers](https://docs.openstatus.dev/guides/how-to-deploy-probes-cloudflare-containers/)-- [Raspberry Pi](/blog/deploy-private-locations-raspberry-pi)--### Docker Container--```bash-docker pull ghcr.io/openstatushq/private-location:latest-```--Run the docker container. It will start **listening to the changes** of your monitors every few minutes and run the **scheduler** for each frequency defined.--```bash-docker run -d \- --name openstatus-private-location \- --restart=always \- -e OPENSTATUS_KEY=$OPENSTATUS_KEY \- ghcr.io/openstatushq/private-location:latest-```diff --git a/apps/web/src/content/pages/product/uptime-monitoring.mdx b/apps/web/src/content/pages/product/uptime-monitoring.mdxindex 9a670c054..c6818a530 100644--- a/apps/web/src/content/pages/product/uptime-monitoring.mdx+++ b/apps/web/src/content/pages/product/uptime-monitoring.mdx@@ -15,6 +15,12 @@ faq:answer: "Yes, you can configure monitors to automatically update your status page based on monitoring results. When assertions fail or thresholds are exceeded, the status page can reflect degraded or down status without manual intervention."- question: "How do thresholds and assertions work together?"answer: "Assertions validate response correctness (status code, headers, body content) while thresholds define performance boundaries (degraded latency, timeout). Both can trigger alerts - assertions catch functional failures, thresholds catch performance degradation."+ - question: "What types of API endpoints can I monitor?"+ answer: "You can monitor any HTTP/HTTPS endpoint including REST APIs, GraphQL APIs, webhooks, and third-party service endpoints. Openstatus supports all HTTP methods (GET, POST, PUT, DELETE, etc.) and custom headers for authentication."+ - question: "Should I use YAML with CLI or Terraform for monitoring as code?"+ answer: "Use YAML + CLI for simplicity and if you're not already using Terraform. It's lightweight and easy to get started. Choose Terraform if you're managing infrastructure as code and want to integrate monitoring into your existing Terraform workflows for unified state management."+ - question: "Can I run private monitoring locations in different networks?"+ answer: "Yes, you can deploy as many private location probes as needed across different networks, VPCs, or regions. Each gets its own API key and appears as a separate monitoring region in your dashboard. The Docker image is only 8.5MB and supports ARM64 and AMD64."---```@@ -57,8 +63,6 @@ faq:Uptime monitoring is your first line of defense to ensure your service is available for your customers. By monitoring your service from multiple regions around the world, you can be sure that your customers are able to reach your service.--<Grid><div>@@ -86,11 +90,27 @@ Check all regions in the [global speed checker](/play/checker).### Multi Cloud-You should avoid monitoring your services from the same cloud providers you use for those services. That’s why our probes are deployed across three different cloud providers:+You should avoid monitoring your services from the same cloud providers you use for those services. That's why our probes are deployed across three different cloud providers:- **Fly.io**-- **Koyeb**-- **Railway**+- **Koyeb**+- **Railway**++### API Monitoring++Monitor any HTTP/HTTPS endpoint including REST APIs, GraphQL APIs, webhooks, and third-party service endpoints. Openstatus supports all HTTP methods and custom headers for authentication.++#### Assertions++Validating your response can be important. You can do **status code**, **header** or **body text** assertions. Read more [in the docs](https://docs.openstatus.dev/reference/http-monitor/#assertions).++#### Thresholds++You can set a **degraded at** and **timeout** threshold whenever required. We will send you a notification whenever the responses exceed the thresholds.++#### Open Telemetry++When needed, you can export to your **OTLP endpoint** the metrics for every request we do. Access the data and set yourself an **alert channel** in Grafana, Honeycomb etc. Read more [in our guide](https://docs.openstatus.dev/guides/how-to-export-metrics-to-otlp-endpoint/).### Notification channels@@ -107,13 +127,68 @@ We support:Automatically update your status page based on your uptime monitoring results. Push reports and communicate with your users during incidents. You can choose to **share response details** on your status page. Read more [about status pages](/status-page).-### CLI+### Monitoring as Code++The best way to **version** your monitor changes is via the openstatus CLI and its **`YAML` config**. Additionally, we provide a [Terraform Provider](https://registry.terraform.io/providers/openstatusHQ/openstatus/latest).++```yaml+# yaml-language-server: $schema=https://www.openstatus.dev/schema.json+uptime-monitor:+ name: "Graphql"+ description: "GitHub GraphQL API"+ frequency: "10m"+ active: true+ regions:+ - iad+ - ams+ - syd+ - jnb+ - gru+ retry: 3+ kind: http+ request:+ url: https://api.github.com/graphql+ method: POST+ headers:+ User-Agent: OpenStatus+ Authorization: Bearer YOUR_TOKEN_HERE+ body: |+ {+ "query": "query { viewer { login }}"+ }+```-You can manage or trigger your monitors via CLI. We provide a simple [GitHub Action](https://github.com/marketplace/actions/openstatus-synthetics-ci) to run it in your **CI/CD**.+Once set, apply your changes via [CLI](https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/):++```bash+openstatus monitors apply+```++Check our [GitHub repository](https://github.com/openstatusHQ/cli-template) to see the `YAML` templates of how to monitor **MCP**, **GraphQL**,... endpoints. We also provide a simple [GitHub Action](https://github.com/marketplace/actions/openstatus-synthetics-ci) to run it in your **CI/CD**.++### Private Locations++Sometimes the services you want to monitor are not accessible from the outside. Simply **deploy our probes** to your favorite **cloud provider**, your own **server** or on your own **virtual private cloud** (VPC).++The docker image is only **8.5MB** small and should easily fit on your infrastructure whether ARM64 or AMD64.++```bash+docker pull ghcr.io/openstatushq/private-location:latest+```++```bash+docker run -d \+ --name openstatus-private-location \+ --restart=always \+ -e OPENSTATUS_KEY=$OPENSTATUS_KEY \+ ghcr.io/openstatushq/private-location:latest+```-### Monitoring as code+You can read more here:-The best way to **version** your monitor changes is via the openstatus CLI and its **`YAML` config**. Additionally, we provide you a [Terraform](https://registry.terraform.io/providers/openstatusHQ/openstatus/latest). Read more [about monitoring as code](/monitoring-as-code)+- [Cloudflare Containers guide](https://docs.openstatus.dev/guides/how-to-deploy-probes-cloudflare-containers/)+- [Raspberry Pi deployment](/blog/deploy-private-locations-raspberry-pi)+- [Private location docs](https://docs.openstatus.dev/tutorial/how-to-create-private-location/)<Grid><div>diff --git a/apps/web/src/content/pages/unrelated/about.mdx b/apps/web/src/content/pages/unrelated/about.mdxindex ce41bdf17..7b2a58c06 100644--- a/apps/web/src/content/pages/unrelated/about.mdx+++ b/apps/web/src/content/pages/unrelated/about.mdx@@ -2,11 +2,13 @@title: "About openstatus"publishedAt: "2025-11-10"author: "openstatus"-description: "openstatus is built by a small team of passionate developers, committed to creating the best open-source status page and uptime monitoring solution."+description: "Openstatus is built by Thibault and Max — a bootstrapped, profitable two-person team building the open-source status page for teams who ship transparency."category: "company"faq:- question: "What is openstatus?"- answer: "Openstatus is an open-source uptime monitoring and status page platform founded in 2023 by Thibault Le Ouay Ducasse and Maximilian Kaske. It monitors websites, APIs, and services from 28 regions globally across multiple cloud providers (Fly.io, Koyeb, Railway). Openstatus is bootstrapped, not VC-funded, and available both as a managed SaaS and for self-hosting."+ answer: "Openstatus is an open-source status page and uptime monitoring platform founded in 2023 by Thibault Le Ouay Ducasse and Maximilian Kaske. It monitors websites, APIs, and services from 28 regions globally across multiple cloud providers. Openstatus is bootstrapped, profitable, and available both as a managed SaaS and for self-hosting."+ - question: "Why is openstatus bootstrapped?"+ answer: "We're self-funded because it keeps us aligned with our customers, not investors. No VC pressure means we build features that matter to you, not features that look good on a pitch deck. We'll be here when your next SOC 2 audit comes around."---<Grid cols={3}>@@ -39,20 +41,18 @@ faq:## Our story-We **met on Twitter in 2023**, after couple of months of DM. We started to work on openstatus and were driven by these goals:+We met on Twitter in 2023 and started building openstatus together. What began as an **open-source** side project driven by curiosity grew into a real business with real impact.-- Build something useful **for other developers**-- A real-world project with all the **latest hot technologies**-- Be **open-source**+Along the way, we've learned that **boring, reliable tech** beats chasing trends every time. We're committed to building openstatus for the long term.-In 2025 most of it remains true but building with the latest hot technologies was a mistake we are afficionado of the **boring tech**.+## Built to last, not to flip-## Our values+We're **profitable and self-funded**. No VC pressure, no growth-at-all-costs. This matters for you because:-We are a small team of 2 people, we are a **small company**. We are **not VC funded**. We are not looking for investors. We want to keep our freedom and **build a substainable business** while working on features that provides the best value to our users.--We also want to be **transparent** about our business. We are not going to hide our ups and downs. We are going to share our journey with you.+- **We build for customers, not investors.** Every feature ships because it solves a real problem, not because it looks good on a pitch deck.+- **We're not going anywhere.** When your SOC 2 audit comes around next year, we'll still be here. And the year after that.+- **We stay lean and fast.** Two people, no bureaucracy. You can talk to the people who write the code.## Our mission-Let's build the best open-source status page with uptime monitoring. **We are aiming to connect the dot between status page and monitoring with incidents.**+We're building the best open-source status page — connecting monitoring, incident communication, and compliance into a single platform. **Transparent by default**, for teams who believe their users deserve to know what's happening.diff --git a/apps/web/src/content/pages/unrelated/pricing.mdx b/apps/web/src/content/pages/unrelated/pricing.mdxindex e7d19c0f2..ccb70bc9d 100644--- a/apps/web/src/content/pages/unrelated/pricing.mdx+++ b/apps/web/src/content/pages/unrelated/pricing.mdx@@ -8,17 +8,6 @@ category: "company"| Features comparison | $0/month - Hobby |$30/month - Starter | $100/month - Pro || --- | --- | --- | --- |-| [Monitors](/uptime-monitoring) | | | |-| Check Interval | 10m | 1m | 30s |-| Number of monitors | 1 | 20 | 50 |-| Multi-region monitoring | + | + | + |-| Total regions | 6 | 28 | 28 |-| Regions per monitor | 6 | 6 | 28 |-| Data retention | 14 days | 3 months | 12 months |-| Response logs | | + | + |-| [Private locations](/private-locations) | | | + |-| OTel Exporter | | | + |-| Number of on-demand checks | 30/mo. | 100/mo. | 300/mo. || [Status Pages](/status-page) | | | || Number of status pages | 1 | 1 +$20/mo./each | 5 +$20/mo./each || Number of components | 3 | 20 | 50 |@@ -31,8 +20,19 @@ category: "company"| **Audience** | | | || Password Protection | | + | + || Email Authentification | | $100/mo. | $100/mo. |+| [Monitors](/uptime-monitoring) | | | |+| Check Interval | 10m | 1m | 30s |+| Number of monitors | 1 | 20 | 50 |+| Multi-region monitoring | + | + | + |+| Total regions | 6 | 28 | 28 |+| Regions per monitor | 6 | 6 | 28 |+| Data retention | 14 days | 3 months | 12 months |+| Response logs | | + | + |+| Private locations | | | + |+| OTel Exporter | | | + |+| Number of on-demand checks | 30/mo. | 100/mo. | 300/mo. || **Alerts** | | | |-| Slack | Discord | Email | Webhook |+| Slack, Discord, Email, Webhook | + | + | + || WhatsApp | | + | + || SMS | | + | + || PagerDuty | | + | + |diff --git a/apps/web/src/content/pages/use-case/api-providers.mdx b/apps/web/src/content/pages/use-case/api-providers.mdxnew file mode 100644index 000000000..ae6174d20--- /dev/null+++ b/apps/web/src/content/pages/use-case/api-providers.mdx@@ -0,0 +1,66 @@+---+title: "Status Pages for API Infrastructure"+publishedAt: "2026-03-13"+author: "openstatus"+description: "Your API consumers expect transparency. Give them a branded status page with real-time uptime data, incident history, and subscription channels — powered by monitoring from 28 regions."+category: "API Infrastructure"+faq:+ - question: "Why do API providers need a public status page?"+ answer: "Your API consumers build their products on top of your infrastructure. When your API is down, their products are down. A public status page reduces support tickets, builds trust, and shows enterprise customers you take reliability seriously."+ - question: "Can I show per-endpoint status?"+ answer: "Yes. You can create separate page components for each API endpoint or service. Group them by product area, region, or any logical structure. Each component shows its own uptime data independently."+ - question: "Can I use monitoring as code to manage monitors?"+ answer: "Yes. Define your monitors as YAML configuration and manage them with the openstatus CLI or Terraform provider. Version control your monitoring setup alongside your API code."+ - question: "How do API consumers subscribe to updates?"+ answer: "Your consumers can subscribe via email, RSS/Atom feeds, or JSON feeds. Many API providers embed the JSON feed into their own dashboards to show upstream status to their users."+---++## Why API providers need a status page++Your API consumers build their products on top of your infrastructure. When your API degrades, their products degrade. They need to know — **immediately**.++A status page is the standard way API providers communicate reliability. If you don't have one, enterprise customers will ask why.++## What API infrastructure teams need++### Per-endpoint visibility++Create separate **page components** for each API endpoint or service. Group by product area, region, or environment. Your consumers see exactly which services are affected.++### Real-time monitoring data++Attach your monitors directly to status page components. Uptime data updates automatically — no manual status changes needed for detected incidents.++### Monitoring as Code++Define monitors as **YAML config** and manage them with the CLI or **Terraform provider**. Version control your monitoring alongside your API code. Deploy changes through CI/CD.++```yaml+uptime-monitor:+ name: "REST API"+ frequency: "1m"+ regions: [iad, ams, sin, syd]+ request:+ url: https://api.yourservice.com/health+ method: GET+```++### Assertions and thresholds++Validate responses beyond status codes. Check **headers**, **body content**, and **response times**. Set **degraded** and **timeout** thresholds to catch performance issues before they become outages.++### Subscriber channels++Let your API consumers subscribe via **email**, **RSS/Atom**, or **JSON** feeds. The JSON feed is particularly useful for consumers who want to embed your status into their own dashboards.++### Custom domain++Host on `status.yourapi.com`. Your consumers expect it.++---++Give your API consumers the transparency they expect++<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>++---diff --git a/apps/web/src/content/pages/use-case/compliance.mdx b/apps/web/src/content/pages/use-case/compliance.mdxnew file mode 100644index 000000000..1bf0211d1--- /dev/null+++ b/apps/web/src/content/pages/use-case/compliance.mdx@@ -0,0 +1,75 @@+---+title: "SOC 2-Ready Status Page in 10 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: "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."+ - 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?"+ answer: "Yes. openstatus handles the incident communication side of compliance while Vanta or Drata manage the broader audit automation. Your status page URL and incident history can be referenced in your compliance platform as evidence of your communication controls."+ - question: "How quickly can I be compliant?"+ answer: "You can have a branded status page with custom domain, incident history, and subscriber notifications live in under 10 minutes. Every paid plan includes everything you need for SOC 2 incident communication compliance."+---++## 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?"_++A status page is the most efficient answer. It provides **timestamped, documented evidence** that you proactively inform users about outages, maintenance, and degraded performance.++## What auditors look for++When reviewing your incident communication controls, SOC 2 auditors typically verify:++- **Proactive notification**: Do you inform stakeholders before they have to ask?+- **Documented timeline**: Can you show when an incident was detected, communicated, and resolved?+- **Subscriber management**: Do affected parties have a way to receive updates?+- **Consistent process**: Is your incident communication repeatable and reliable?++Openstatus checks every box automatically.++## How openstatus helps++### Incident history as audit evidence++Every status report you publish — from initial detection to resolution — is **timestamped and stored**. Your auditor gets a complete trail of how you communicated each incident without you maintaining separate documentation.++### Subscriber notifications++Stakeholders can subscribe via **email**, **RSS/Atom**, or **JSON feeds**. When you post an update, subscribers are notified automatically. This proves you proactively communicate — exactly what auditors want to see.++### Maintenance windows++Planned maintenance shows auditors you communicate **proactively**, not just reactively. Schedule maintenance windows and notify subscribers before any planned downtime.++### Branded custom domain++Host your status page on your own domain (e.g., `status.yourcompany.com`). This keeps the experience professional and consistent with your brand — important when auditors or enterprise customers visit.++### Password protection++For internal services or client-specific deployments, protect your status page with **password protection** or **magic link authentication**. Control who sees what without maintaining separate systems.++## Get SOC 2-ready in minutes++1. [Create your account](https://app.openstatus.dev) — free to start+2. Set up your status page with your brand and custom domain+3. Add your monitors or external service components+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.++---++Ready to check the compliance box?++<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>++---diff --git a/apps/web/src/content/pages/use-case/crypto.mdx b/apps/web/src/content/pages/use-case/crypto.mdxnew file mode 100644index 000000000..fd1806b1e--- /dev/null+++ b/apps/web/src/content/pages/use-case/crypto.mdx@@ -0,0 +1,56 @@+---+title: "Status Pages for Crypto Exchanges and DeFi Protocols"+publishedAt: "2026-03-13"+author: "openstatus"+description: "Keep your traders and users informed during outages. Monitor exchange APIs, wallet services, and blockchain nodes from 28 global regions with a branded, trustworthy status page."+category: "Crypto"+faq:+ - question: "Why do crypto platforms need a status page?"+ answer: "Downtime in crypto means lost trades and lost trust. A status page gives your users a single source of truth during incidents — reducing support tickets, preventing panic, and demonstrating operational maturity to institutional partners."+ - question: "Can I monitor blockchain RPC endpoints?"+ answer: "Yes. Openstatus monitors any HTTP/HTTPS endpoint. You can monitor RPC nodes, REST APIs, WebSocket endpoints, and more with custom assertions to validate response correctness."+ - question: "Do you support custom domains?"+ answer: "Yes. Host your status page on your own domain (e.g., status.exchange.com) to maintain brand trust. Custom domains are available on paid plans."+ - question: "Can I protect my status page for institutional clients?"+ answer: "Yes. Use password protection or magic link authentication to create private status pages for institutional partners or internal teams."+---++## Why crypto platforms need a status page++When your exchange goes down, users don't wait — they panic. A status page is the difference between **"we're handling it"** and **"are they exit scamming?"**++For institutional partners, a status page signals operational maturity. For retail users, it builds trust.++## Built for always-on platforms++### 28 global regions++Monitor your APIs from regions that match your user base. Detect regional outages before your users report them.++### API monitoring with assertions++Validate that your endpoints return correct data — not just that they respond. Check status codes, headers, and response bodies to catch silent failures.++### Instant alerts++Get notified via **Slack**, **Discord**, **PagerDuty**, **OpsGenie**, **SMS**, or **webhook** the moment something degrades. Route alerts to your on-call team.++### Branded status page++Host on your own domain. Customize with your brand. Show your users you take reliability seriously.++### Subscriber notifications++Let users subscribe for email updates. When you push a status report, they're informed automatically — reducing support load during incidents.++### Password-protected pages++Create private status pages for institutional partners or internal operations teams with **password protection** or **magic link authentication**.++---++Keep your users informed, not panicking++<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>++---diff --git a/apps/web/src/content/pages/use-case/open-source.mdx b/apps/web/src/content/pages/use-case/open-source.mdxnew file mode 100644index 000000000..967e1bae7--- /dev/null+++ b/apps/web/src/content/pages/use-case/open-source.mdx@@ -0,0 +1,56 @@+---+title: "Status Pages for Open-Source Projects"+publishedAt: "2026-03-13"+author: "openstatus"+description: "Give your open-source community a transparent view of service health. Free status page with uptime monitoring, incident history, and community-friendly subscriptions."+category: "Open Source"+faq:+ - question: "Is openstatus free for open-source projects?"+ answer: "Yes. The free plan includes one monitor, one status page with three components, and monitoring from up to 6 regions. For larger projects, paid plans start at $30/month with 20 monitors and custom domains."+ - question: "Can I self-host openstatus?"+ answer: "Yes. Openstatus is fully open source (MIT license) and can be self-hosted. The checker runs as an 8.5MB Docker image. You can also use the managed SaaS and keep the monitoring infrastructure off your plate."+ - question: "How do open-source projects use openstatus?"+ answer: "Projects like Cal.com, Documenso, Hanko, and OpenPanel use openstatus to give their communities transparent uptime data. They monitor APIs and services, publish incidents, and let contributors and users subscribe for updates."+ - question: "Can contributors subscribe to status updates?"+ answer: "Yes. Your community can subscribe via email, RSS/Atom feeds, or JSON feeds. When you publish a status report or schedule maintenance, subscribers are notified automatically."+---++## Why open-source projects need a status page++Your users and contributors rely on your services — APIs, documentation sites, package registries, demo instances. When something goes down, they need to know **what's happening** and **when it'll be back**.++A status page turns "is it down for everyone or just me?" into a clear answer.++## Trusted by the open-source community++Teams like **Cal.com**, **Documenso**, **Hanko**, **OpenPanel**, and **Probo** use openstatus to keep their communities informed.++## Why openstatus fits open-source++### Open source itself++Openstatus is fully open source. You can inspect the code, contribute, self-host, or use the managed SaaS. No vendor lock-in.++### Free tier that works++The free plan gives you a real status page with uptime monitoring — not a trial. One monitor, one status page, 6 regions. Enough for most projects to get started.++### Transparent by default++Public status pages with uptime data, incident history, and response times. Your community sees exactly what's happening — matching the transparency ethos of open source.++### Community subscriptions++Let your users subscribe via **email**, **RSS/Atom**, or **JSON**. When you push a status report, they know. No manual pinging in Discord.++### Theme Store++Make your status page match your project's brand with [community themes](https://themes.openstatus.dev). Contribute your own theme back to the store.++---++Give your community the transparency they deserve++<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>++---diff --git a/apps/web/src/content/utils.ts b/apps/web/src/content/utils.tsindex 346f0f3e8..503aaf850 100644--- a/apps/web/src/content/utils.ts+++ b/apps/web/src/content/utils.ts@@ -111,6 +111,13 @@ export function getGuides(): MDXData[] {);}+export function getUseCasePages(): MDXData[] {+ return getMDXDataFromDir(+ path.join(process.cwd(), "src", "content", "pages", "use-case"),+ "/use-case",+ );+}+export function getUnrelatedPages(): MDXData[] {return getMDXDataFromDir(path.join(process.cwd(), "src", "content", "pages", "unrelated"),@@ -172,6 +179,7 @@ export const PAGE_TYPES = ["compare","tools","guides",+ "use-case","all",] as const;@@ -193,6 +201,8 @@ export function getPages(type: PageType) {return getToolsPages();case "guides":return getGuides();+ case "use-case":+ return getUseCasePages();case "all":return [...getBlogPosts(),@@ -202,6 +212,7 @@ export function getPages(type: PageType) {...getComparePages(),...getToolsPages(),...getGuides(),+ ...getUseCasePages(),];default:throw new Error(`Unknown page type: ${type}`);diff --git a/apps/web/src/data/content.ts b/apps/web/src/data/content.tsindex 38a90f2f5..ce31eb099 100644--- a/apps/web/src/data/content.ts+++ b/apps/web/src/data/content.ts@@ -1,7 +1,10 @@import {+ getBlogPosts,+ getChangelogPosts,getComparePages,getProductPages,getToolsPages,+ getUseCasePages,} from "@/content/utils";import type { Region } from "@openstatus/regions";@@ -42,16 +45,26 @@ const resourcesFooterSection = {label: "OSS Friends",href: "/oss-friends",},- {- label: "Marketing V1",- href: "https://v1.openstatus.dev",- },],};+const useCases = getUseCasePages();++const useCasesSection = {+ label: "Use Cases",+ items: useCases.map((page) => ({+ label: page.metadata.title,+ href: `/use-case/${page.slug}`,+ })),+};+const resourcesHeaderSection = {label: "Resources",items: [+ {+ label: "Use Cases",+ href: "/use-case",+ },{label: "Docs",href: "https://docs.openstatus.dev",@@ -105,6 +118,34 @@ const companySection = {],};+const blogSection = {+ label: "Blog",+ items: getBlogPosts()+ .sort(+ (a, b) =>+ b.metadata.publishedAt.getTime() - a.metadata.publishedAt.getTime(),+ )+ .slice(0, 6)+ .map((post) => ({+ label: post.metadata.title,+ href: `/blog/${post.slug}`,+ })),+};++const changelogSection = {+ label: "Changelog",+ items: getChangelogPosts()+ .sort(+ (a, b) =>+ b.metadata.publishedAt.getTime() - a.metadata.publishedAt.getTime(),+ )+ .slice(0, 6)+ .map((post) => ({+ label: post.metadata.title,+ href: `/changelog/${post.slug}`,+ })),+};+const compareSection = {label: "Compare",items: getComparePages()@@ -112,7 +153,7 @@ const compareSection = {label: page.metadata.title,href: `/compare/${page.slug}`,}))- .slice(0, 7),+ .slice(0, 6),};const toolsSection = {@@ -138,10 +179,6 @@ const toolsSection = {label: "All Status Codes",href: "https://openstat.us",},- {- label: "Vercel Edge Ping",- href: "https://light.openstatus.dev",- },],};@@ -157,7 +194,7 @@ const communitySection = {href: "https://openstatus.dev/github",},{- label: "X",+ label: "Twitter",href: "https://openstatus.dev/twitter",},{@@ -219,9 +256,12 @@ export const headerLinks = [productsSection, resourcesHeaderSection];export const footerLinks = [productsSection,+ useCasesSection,resourcesFooterSection,companySection,compareSection,+ blogSection,+ changelogSection,toolsSection,communitySection,];diff --git a/apps/web/src/lib/metadata/shared-metadata.ts b/apps/web/src/lib/metadata/shared-metadata.tsindex b5c9c067f..1d3a32593 100644--- a/apps/web/src/lib/metadata/shared-metadata.ts+++ b/apps/web/src/lib/metadata/shared-metadata.ts@@ -3,12 +3,12 @@ import type { Metadata } from "next";export const TITLE = "openstatus";export const HOMEPAGE_TITLE =- "openstatus - Open-Source Status Page & Uptime Monitoring";+ "openstatus - The open-source status page trusted by growing teams";export const DESCRIPTION =- "Monitor your services globally and showcase uptime with a status page. Get started for free with our open-source status page and uptime monitoring solution.";+ "Ship your status page before your SOC 2 auditor asks for it. Communicate incidents, prove compliance readiness, and monitor uptime from 28 global regions. Open source and free to start.";export const OG_DESCRIPTION =- "Open-source status page and uptime monitoring system";+ "The open-source status page for compliance-ready teams";export const BASE_URL =process.env.NODE_ENV === "production"diff --git a/apps/web/src/styles/globals.css b/apps/web/src/styles/globals.cssindex 4b0e9af65..9eb8784ba 100644--- a/apps/web/src/styles/globals.css+++ b/apps/web/src/styles/globals.css@@ -185,24 +185,23 @@}.prose h1 {- @apply text-3xl text-foreground font-medium tracking-tight my-4 relative;+ @apply text-balance text-3xl text-foreground font-medium tracking-tight my-6 relative;}-.prose h2 {- @apply text-2xl text-foreground font-medium tracking-tight my-4 relative;+ @apply text-2xl text-foreground font-medium tracking-tight my-6 relative;}.prose h3 {- @apply text-xl text-foreground font-medium tracking-tight my-4 relative;+ @apply text-xl text-foreground font-medium tracking-tight my-6 relative;}.prose h4 {- @apply text-lg text-foreground font-medium tracking-tight my-4 relative;+ @apply text-lg text-foreground font-medium tracking-tight my-6 relative;}.prose hr {- @apply my-4 border-border;+ @apply my-6}.prose strong {