Skip to content

Open-source status page, incident response and uptime monitoring

chore: improve web content (#1867)

Maximilian Kaskeabcb6acd4562
diff --git a/apps/web/public/llms.txt b/apps/web/public/llms.txt
index 325ba3f08..745aee784 100644
--- a/apps/web/public/llms.txt
+++ b/apps/web/public/llms.txt
@@ -1,18 +1,63 @@
# openstatus
-OpenStatus is an open-source status page platform with global monitoring (HTTP, TCP, DNS).
+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.
-## Features
+## Who it's for
-- Uptime Monitoring: Monitor the availability and performance of your services globally.
-- Status Page: Create a custom status page to display the status of your services.
-- Monitoring as Code: Define your monitoring checks using YAML.
-- Alerting: Configure email, Slack, or other notification channels for alerts.
-- CLI: Manage openstatus using a command-line interface.
-- SDK: Integrate openstatus into your applications with our [SDK](https://jsr.io/@openstatus/sdk-node).
+- 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)
+- Organizations that require self-hosted monitoring behind a firewall (private locations)
+- Open-source projects and startups looking for a free or affordable monitoring solution
-## Documentation
+## Pricing
+- **Hobby** — $0/month: 1 monitor, 6 regions, 10m check interval, 1 status page, 3 page components, 14-day data retention
+- **Starter** — $30/month: 20 monitors, 28 regions, 1m check interval, 1 status page, 20 components, 3-month retention, subscribers, custom domain, WhatsApp/SMS/PagerDuty alerts
+- **Pro** — $100/month: 50 monitors, 28 regions, 30s check interval, 5 status pages, 50 components, 12-month retention, private locations, OTel exporter, 20 notification channels
+
+Pricing is available in USD, EUR, and INR.
+
+## Key Features
+
+- **28-region monitoring**: Parallel checks across Europe, North America, South America, Asia, Africa, and Oceania — no round-robin, all regions fire simultaneously
+- **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, SSH)
+- **API Monitoring**: Assertions, thresholds, status code checks, header and body validation
+- **Monitoring as Code**: Define monitors in YAML, manage via CLI or GitHub Actions
+- **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 available on JSR (@openstatus/sdk-node)
+- **Open-source**: AGPL-3.0-licensed, self-hostable, 8k+ GitHub stars
+
+## Key Differentiators
+
+- Open-source and bootstrapped (no VC funding)
+- Parallel scheduling strategy — all selected regions check simultaneously (vs. round-robin competitors)
+- Unlimited team members on paid plans
+- Status page subscribers included (not a paid add-on)
+- Private status pages included in team plan (not an additional charge)
+- Self-hosting option with full feature parity
+
+## Comparisons
+
+- [openstatus vs BetterStack](https://www.openstatus.dev/compare/betterstack)
+- [openstatus vs Checkly](https://www.openstatus.dev/compare/checkly)
+- [openstatus vs UptimeRobot](https://www.openstatus.dev/compare/uptime-robot)
+- [openstatus vs Uptime Kuma](https://www.openstatus.dev/compare/uptime-kuma)
+
+## Links
+
+- [About](https://www.openstatus.dev/about)
+- [Pricing](https://www.openstatus.dev/pricing)
+- [Changelog](https://www.openstatus.dev/changelog)
+- [Global Speed Checker](https://www.openstatus.dev/play/checker)
+- [Theme Store](https://themes.openstatus.dev)
+- [Dashboard](https://app.openstatus.dev)
- [Documentation](https://docs.openstatus.dev/)
- [Documentation llms docs](https://docs.openstatus.dev/llms.txt)
- [Documentation llms docs full](https://docs.openstatus.dev/llms-full.txt)
+- [GitHub](https://github.com/openstatushq/openstatus)
+- [SDK](https://jsr.io/@openstatus/sdk-node)
+- [API](https://api.openstatus.dev/openapi)
diff --git a/apps/web/src/content/pages/compare/betterstack.mdx b/apps/web/src/content/pages/compare/betterstack.mdx
index f71ee5192..108bc9120 100644
--- a/apps/web/src/content/pages/compare/betterstack.mdx
+++ b/apps/web/src/content/pages/compare/betterstack.mdx
@@ -2,10 +2,25 @@
title: "BetterStack Alternative"
publishedAt: "2025-11-10"
author: "Thibault Le Ouay Ducasse"
-description: "Open-source uptime monitoring. Learn how OpenStatus compares to BetterStack."
-category: "Company"
+description: "Open-source uptime monitoring. Learn how openstatus compares to BetterStack."
+category: "company"
+faq:
+ - question: "Is openstatus a good BetterStack alternative?"
+ answer: "Yes. Openstatus offers uptime monitoring from 28 regions (vs. BetterStack's 4), an open-source codebase, parallel check scheduling, and unlimited status page subscribers — all included in the base price. BetterStack charges extra for private status pages ($42/mo.) and subscriber tiers ($42/mo. per 1000). Openstatus is also bootstrapped and self-hostable."
+ - question: "How does openstatus pricing compare to BetterStack?"
+ answer: "Openstatus starts free (Hobby plan) and paid plans begin at $30/month (Starter) and $100/month (Pro). Private status pages and unlimited subscribers are included. BetterStack's equivalent features require paid add-ons on top of their base price."
+ - question: "Does openstatus support as many monitoring regions as BetterStack?"
+ answer: "Openstatus monitors from 28 regions worldwide. BetterStack uses approximately 4 regions. Openstatus also uses a parallel scheduling strategy — all selected regions fire simultaneously — whereas BetterStack uses round-robin scheduling."
+ - question: "Can I self-host openstatus instead of using the cloud service?"
+ answer: "Yes. Openstatus is open-source (AGPL-3.0 license) and fully self-hostable. BetterStack is a closed-source SaaS product with no self-hosting option."
---
+Openstatus and BetterStack are both uptime monitoring platforms with status pages. Openstatus is open-source, bootstrapped, and built for teams that want global coverage and transparent pricing. BetterStack is a VC-backed, closed-source SaaS with a broader product suite including log management.
+
+The most significant technical difference is scheduling strategy: openstatus checks all selected regions **simultaneously** (parallel), giving you a true global picture of availability at each check interval. BetterStack uses **round-robin** scheduling, cycling through regions one at a time.
+
+## Feature Comparison
+
| Feature | openstatus | BetterStack |
| --- | --- | --- |
| Open-source | + | - |
@@ -16,5 +31,18 @@ category: "Company"
| OpenTelemetry exporter | + | - |
| GitHub Action | + | - |
| CLI to trigger checks | + | - |
-| Private status page | included in team plan | additional $42/mo. |
-| Status page subscribers | Unlimited | additional $42/mo. per 1000 |
+| Team members | unlimited | restricted |
+| Password-protected status page | included in team plan | additional $42/mo. |
+
+## When to Choose openstatus
+
+- You want monitoring from **28 regions** with parallel checks
+- You prefer **open-source** software or need to self-host
+- You want **predictable pricing** without subscriber or feature add-ons
+- You need **OpenTelemetry export** or CI/CD integration via GitHub Actions
+
+## When to Choose BetterStack
+
+- You need **incident escalation** workflows
+- You want a single platform for uptime monitoring **and** log management
+- You prefer a mature, closed-source SaaS with dedicated support tiers
diff --git a/apps/web/src/content/pages/compare/checkly.mdx b/apps/web/src/content/pages/compare/checkly.mdx
index d7b5e3d61..f16f21787 100644
--- a/apps/web/src/content/pages/compare/checkly.mdx
+++ b/apps/web/src/content/pages/compare/checkly.mdx
@@ -2,13 +2,47 @@
title: "Checkly Alternative"
publishedAt: "2025-11-10"
author: "Thibault Le Ouay Ducasse"
-description: "Open-source uptime monitoring. Learn how OpenStatus compares to Checkly."
-category: "Company"
+description: "Open-source uptime monitoring. Learn how openstatus compares to Checkly."
+category: "company"
+faq:
+ - question: "Is openstatus a good Checkly alternative?"
+ answer: "It depends on your use case. Openstatus is focused on uptime monitoring and status pages — it excels at HTTP, TCP, and DNS checks from 28 global regions. Checkly is focused on synthetic monitoring with browser-based checks using Playwright. If you need uptime monitoring with a public status page, openstatus is the stronger choice. If you need end-to-end browser testing as monitoring, Checkly is more suitable."
+ - question: "Does openstatus have more monitoring regions than Checkly?"
+ answer: "Yes. Openstatus monitors from 28 regions worldwide. Checkly uses approximately 19 regions. Openstatus also checks all regions simultaneously (parallel scheduling) rather than cycling through them."
+ - question: "Does openstatus include a status page?"
+ answer: "Yes. Openstatus includes branded status pages with custom domains, maintenance windows, and subscriber notifications on all plans. Checkly does not offer a built-in public status page product."
+ - question: "Is openstatus open-source?"
+ answer: "Yes. Openstatus is AGPL-3.0-licensed and fully self-hostable. Checkly is a closed-source SaaS product."
---
-| Feature | OpenStatus | Checkly |
+Openstatus and Checkly take different approaches to monitoring. Openstatus focuses on **uptime monitoring** — checking whether your endpoints are reachable and performant from 28 global regions — and pairs this with **status pages** for incident communication. Checkly focuses on **synthetic monitoring** using Playwright and Puppeteer to run full browser-based end-to-end checks.
+
+If your primary need is knowing when your API or website goes down and communicating that to users, openstatus is the more direct fit. If you need to verify complex user flows (login, checkout, search) are working correctly, Checkly's browser testing approach is more powerful.
+
+## Feature Comparison
+
+| Feature | openstatus | Checkly |
| --- | --- | --- |
| Multi-region | 28 | 19 |
| Status Page | + | ? |
-| Open Source | + | - |
+| Open-source | + | - |
| Bootstrap | + | - |
+| Monitoring as code | + (YAML + CLI) | + (JavaScript) |
+| Browser checks (Playwright) | - | + |
+| OpenTelemetry exporter | + | + |
+| GitHub Action | + | + |
+| Team members | unlimited | restricted |
+
+## When to Choose openstatus
+
+- You need uptime monitoring **with a status page** for incident communication
+- You want **28 regions** with parallel scheduling
+- You prefer **open-source** software or need to self-host
+- You want HTTP/TCP/DNS monitoring with **assertions and thresholds**
+- You need **predictable, low-cost pricing** for a small team
+
+## When to Choose Checkly
+
+- You need **browser-based synthetic monitoring** with Playwright
+- You want to monitor **complex user flows** (checkout, authentication, search)
+- You already use JavaScript-based monitoring-as-code workflows
diff --git a/apps/web/src/content/pages/compare/uptime-kuma.mdx b/apps/web/src/content/pages/compare/uptime-kuma.mdx
index 51a9ca385..289735023 100644
--- a/apps/web/src/content/pages/compare/uptime-kuma.mdx
+++ b/apps/web/src/content/pages/compare/uptime-kuma.mdx
@@ -2,18 +2,48 @@
title: "Uptime Kuma Alternative"
publishedAt: "2025-11-10"
author: "Thibault Le Ouay Ducasse"
-description: "Open-source uptime monitoring. Learn how OpenStatus compares to Uptime Kuma."
-category: "Company"
+description: "Open-source uptime monitoring. Learn how openstatus compares to Uptime Kuma."
+category: "company"
+faq:
+ - question: "Is openstatus a good Uptime Kuma alternative?"
+ answer: "Yes, especially if you want managed cloud hosting or global multi-region monitoring. Both are open-source, but openstatus is available as a SaaS (no server to maintain) and monitors from 28 regions worldwide. Uptime Kuma is self-hosted only and checks from a single server location."
+ - question: "What is the main difference between openstatus and Uptime Kuma?"
+ answer: "The main difference is hosting model and monitoring coverage. Uptime Kuma is self-hosted only — you run it on your own server and it monitors from that single location. Openstatus is available as a managed SaaS or self-hosted, and checks from 28 regions across multiple cloud providers simultaneously."
+ - question: "Is openstatus free like Uptime Kuma?"
+ answer: "Openstatus has a free Hobby plan (1 monitor, 6 regions, 1 status page) with no credit card required. Uptime Kuma is fully free and open-source but requires you to provision, host, and maintain your own server."
+ - question: "Does openstatus support self-hosting like Uptime Kuma?"
+ answer: "Yes. Openstatus is AGPL-3.0-licensed and can be self-hosted. You also get the option to use the managed cloud service without managing any infrastructure."
---
-| Feature | OpenStatus | Uptime Kuma |
+Openstatus and Uptime Kuma are both open-source uptime monitoring tools, making this a comparison between two projects with shared values but different architectures. The fundamental difference is the **hosting model**: Uptime Kuma is self-hosted only — you run it on your own server and it monitors from that single location. Openstatus is available both as a **managed SaaS** and for self-hosting, and checks from **28 regions worldwide**.
+
+If you want zero infrastructure responsibility and global multi-region checks, openstatus is the natural choice. If you want a completely free, self-managed tool with full control and no external dependencies, Uptime Kuma is a solid option.
+
+## Feature Comparison
+
+| Feature | openstatus | Uptime Kuma |
| --- | --- | --- |
-| Open Source | + | + |
-| Self-hosted or cloud-based | + | Self-hosted only |
-| Bootstrap | Talk directly to the founder | - |
-| Multi-cloud | 3 cloud providers | Single server |
-| Global (28 regions) | 28 | 1 |
-| Monitor your endpoints globally | + | Single location |
-| OTel Export | Export synthetic checks to OTel | - |
-| GitHub Action | Trigger via CI/CD | - |
-| Team members | Unlimited | Unlimited |
+| Open-source | + | + |
+| Self-hosted or cloud-based | both | self-hosted only |
+| Multi-cloud | 3 cloud providers | single server |
+| Multi-region (global) | 28 regions | 1 (your server location) |
+| OTel Export | + | - |
+| GitHub Action | + | - |
+| Team members | unlimited | unlimited |
+| Managed SaaS option | + | - |
+| Monitoring as code | + | - |
+
+## When to Choose openstatus
+
+- You want **managed SaaS** with no infrastructure to maintain
+- You need **28-region global monitoring** from multiple cloud providers
+- You want **monitoring as code** via YAML and GitHub Actions
+- You need **OpenTelemetry export** or a tightly integrated status page
+- You want to **talk to the founders** directly (bootstrapped, small team)
+
+## When to Choose Uptime Kuma
+
+- You want **completely free** monitoring with no usage limits
+- You are comfortable **running your own server**
+- You need monitoring **behind a firewall** with no external SaaS dependency
+- You prefer a **single-location** check from your own infrastructure
diff --git a/apps/web/src/content/pages/compare/uptime-robot.mdx b/apps/web/src/content/pages/compare/uptime-robot.mdx
index f7cc3950b..d44de9987 100644
--- a/apps/web/src/content/pages/compare/uptime-robot.mdx
+++ b/apps/web/src/content/pages/compare/uptime-robot.mdx
@@ -3,15 +3,46 @@ title: "UptimeRobot Alternative"
publishedAt: "2025-11-10"
author: "Maximilian Kaske"
description: "Open-source uptime monitoring. Learn how openstatus compares to UptimeRobot."
-category: "Company"
+category: "company"
+faq:
+ - question: "Is openstatus a good UptimeRobot alternative?"
+ answer: "Yes. Openstatus monitors from 28 global regions simultaneously (UptimeRobot checks from a single location at a time), is open-source and self-hostable, includes unlimited team members on paid plans, and supports OpenTelemetry export and CI/CD integration via GitHub Actions — none of which UptimeRobot offers."
+ - question: "How does openstatus pricing compare to UptimeRobot?"
+ answer: "Openstatus starts free and paid plans begin at $30/month with unlimited team members. UptimeRobot charges an additional $19 per seat for team members, which adds up quickly for larger teams."
+ - question: "Does openstatus monitor from more regions than UptimeRobot?"
+ answer: "Yes. Openstatus checks from 28 regions worldwide across multiple cloud providers. UptimeRobot does not offer meaningful multi-region monitoring."
+ - question: "Can I self-host openstatus?"
+ answer: "Yes. Openstatus is open-source (AGPL-3.0 license) and self-hostable. UptimeRobot is a closed-source SaaS with no self-hosting option."
---
-| Feature | OpenStatus | UptimeRobot |
+Openstatus and UptimeRobot are both uptime monitoring tools, but they differ significantly in architecture and capabilities. Openstatus is open-source, monitors from 28 regions **simultaneously**, and includes status pages and developer tooling. UptimeRobot is a long-established closed-source SaaS that checks from a single location at a time with a simpler feature set.
+
+For teams that need global monitoring coverage, CI/CD integration, or a public status page, openstatus is the stronger choice. UptimeRobot remains a simple, well-known option for basic single-location availability checks.
+
+## Feature Comparison
+
+| Feature | openstatus | UptimeRobot |
| --- | --- | --- |
-| Open Source | + | - |
+| Open-source | + | - |
| Bootstrap | + | - |
-| Multi-cloud | 3 | ? |
+| Multi-cloud | 3 providers | - |
| Multi-region | 28 | - |
-| OTel Export | Export synthetic checks to OTel | - |
-| GitHub Action | Trigger via CI/CD | - |
-| Team members | Unlimited | additional $19/seat |
+| OTel Export | + | - |
+| GitHub Action | + | - |
+| Team members | unlimited | additional $19/seat |
+| Status Page | + | + (basic) |
+| Monitoring as code | + | - |
+
+## When to Choose openstatus
+
+- You need **multi-region monitoring** from 28 global locations
+- You want a **status page** tightly integrated with your monitors
+- You need **team collaboration** without per-seat charges
+- You want **open-source** software or CI/CD integration
+- You need **OpenTelemetry export** or monitoring as code
+
+## When to Choose UptimeRobot
+
+- You want a **familiar, well-established** tool with a long track record
+- Single-location monitoring is **sufficient for your use case**
+- You need **many monitors on the free tier** — UptimeRobot's free plan includes up to 50 monitors
diff --git a/apps/web/src/content/pages/home.mdx b/apps/web/src/content/pages/home.mdx
index bb9787869..4d5e706e1 100644
--- a/apps/web/src/content/pages/home.mdx
+++ b/apps/web/src/content/pages/home.mdx
@@ -3,18 +3,22 @@ title: "The open-source status page with uptime monitoring"
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."
-category: "Product"
+category: "product"
faq:
- - question: "What are the free limits?"
- answer: "As free user you will start with a total of one monitor and one status page (incl. three page components) as well as cron jobs of min. 10m. You can upgrade to a paid plan at any time. No credit card is required to sign up and you can cancel at any time."
- - question: "Who are we?"
- answer: "We are Thibault and Max and we take you with us on our journey. Read more on our about page at https://www.openstatus.dev/about."
- - question: "How does it work?"
- answer: "We ping your endpoints from multiple regions to calculate uptime and display the current status on your status page. We also collect response time data like headers and timing phases and display it on your dashboard."
- - question: "What regions do we support?"
- answer: "We support monitoring from 28 regions worldwide across all continents: Europe (Amsterdam, Stockholm, Paris, Frankfurt, London), North America (Dallas, New Jersey, Los Angeles, San Jose, Chicago, Toronto), South America (São Paulo), Asia (Mumbai, Tokyo, Singapore), Africa (Johannesburg), and Oceania (Sydney)."
- - question: "How can I help?"
- answer: "There are many ways you can help us: Spread the word by telling your friends and colleagues about OpenStatus, report bugs if you find them, suggest new features, contribute to the project if you are a developer, become a paid user if you are a business, or star our project on GitHub."
+ - 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."
+ - 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."
+ - 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">
@@ -102,17 +106,25 @@ Check your website's latency
## FAQs
-<Details summary="What are the free limits?">
+<Details summary="What is openstatus?">
-As free user you will start with a total of **one monitor** and **one status page (incl. three page components)** as well as cron jobs of min. `10m`. You can upgrade to a paid plan at any time. Check the pricing table for more details.
+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.
-No credit card is required to sign up and you can cancel at any time.
+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="Who are we?">
+<Details summary="What does the free plan include?">
-We are [Thibault](https://bsky.app/profile/thibaultleouay.dev) and [Max](https://x.com/mxkaske) and we take you with us on our journey.
+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.
+
+No credit card required — upgrade or cancel at any time.
+
+</Details>
+
+<Details summary="Who is behind openstatus?">
+
+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.
Read more on [our about page](/about).
@@ -125,17 +137,19 @@ Read more on [our about page](/about).
</Details>
-<Details summary="How does it work?">
+<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.
-We ping your endpoints from multiple regions to calculate uptime and display the current status on your status page. We also collect response time data like headers and timing phases and display it 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 out the [Speed Checker](/play/checker).
+Try the [Speed Checker](/play/checker) to see real-time data from all regions.
</Details>
-<Details summary="What regions do we support?">
+<Details summary="What regions does openstatus monitor from?">
-We support **monitoring from 28 regions worldwide** across all continents:
+Openstatus monitors from **28 regions worldwide** across all continents:
**Europe**
@@ -165,15 +179,26 @@ Sydney 🇦🇺
</Details>
-<Details summary="How can I help?">
+<Details summary="Can I self-host openstatus?">
+
+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 to check internal services not exposed to the internet.
+
+- [Self-hosting the full openstatus stack](https://docs.openstatus.dev/guides/self-hosting-openstatus/)
+- [Self-hosting the status page only](https://docs.openstatus.dev/guides/self-host-status-page-only/)
+
+The source code is available on [GitHub](https://openstatus.dev/github).
+
+</Details>
+
+<Details summary="How can I contribute to openstatus?">
-There are many ways you can help us:
+There are many ways to support the project:
-- **Spread the word**: Tell your friends and colleagues about OpenStatus. The more people use it, the more we can improve it.
-- **Report bugs**: If you find a bug, please report it.
-- **Suggest features**: If you have an idea for a new feature, please let us know.
-- **Contribute**: If you are a developer, you can contribute to the project.
-- **Become a paid user**: If you are a business, you can become a paid user.
-- **Star our project**: If you like our project, you can star it on [GitHub](https://openstatus.dev/github).
+- **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 file
diff --git a/apps/web/src/content/pages/unrelated/about.mdx b/apps/web/src/content/pages/unrelated/about.mdx
index 48baf493f..ce41bdf17 100644
--- a/apps/web/src/content/pages/unrelated/about.mdx
+++ b/apps/web/src/content/pages/unrelated/about.mdx
@@ -4,6 +4,9 @@ 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."
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."
---
<Grid cols={3}>