{"category":{"slug":"self-hosted-status-pages","label":"Self-hosted status page tools"},"methodology_url":"https://www.orbator.io/ai-index/methodology","license":"Free to use with attribution to orbator.io","date":"2026-08-10","engine":null,"available_dates":["2026-08-10","2026-08-09","2026-07-29","2026-07-25","2026-07-22","2026-07-05","2026-07-04","2026-06-17","2026-06-16"],"policy":{"quotable_engines":["anthropic","openai","gemini"],"max_excerpt_chars":400,"full_text_public":false,"customer_runs_public":false,"full_text_retention":"retained at least 24 months, then operator review","notes":["Only Index category runs are archived publicly — customer scans never appear.","The quotable unit is a short excerpt of at most 400 characters, never the full answer.","Engines outside the verbatim allowlist are recorded as having answered, with the excerpt withheld under their terms.","Prompt intent is published; the prompt text itself is not."]},"status":"ok","count":7,"limit":50,"truncated":false,"engines":[{"engine":"anthropic","count":7,"withheld":false,"answers":[{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"alternatives","excerpt":"## Open-Source Status Page Alternatives to Hosted Services (like Atlassian Statuspage)\n\nIf you're looking to move away from hosted services like Atlassian Statuspage, Status.io, or Statuspal, there's a solid ecosystem of open-source, self-hostable tools. Here's a breakdown of the main options:\n\n### Actively Maintained / Modern Options\n\n**OpenStatus** is the standout newer entrant in this space. It","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":65,"end":85,"name":"Atlassian Statuspage"},{"start":145,"end":165,"name":"Atlassian Statuspage"},{"start":167,"end":176,"name":"Status.io"},{"start":181,"end":190,"name":"Statuspal"},{"start":340,"end":350,"name":"OpenStatus"}]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"alternatives","excerpt":"Here's a solid roundup of lightweight, self-hosted status page tools that let indie developers avoid recurring SaaS fees:\n\n## Top Picks for Indie Devs\n\n**Uptime Kuma** — The community favorite by far. At 61,000+ GitHub stars, it is one of the most-starred tools in the self-hosting ecosystem, and the resource cost is negligible: it runs in roughly 50 MB of RAM. It supports HTTP, HTTPS, TCP, DNS, Do","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":154,"end":165,"name":"Uptime Kuma"}]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"best_in_category","excerpt":"Here's a rundown of the strongest self-hosted status page options for a SaaS product that wants to keep everything in-house, based on current 2026 comparisons:\n\n## Top picks\n\n**Uptime Kuma** — The most popular self-hosted option by far. Uptime Kuma is a self-hosted status page tool with over 85,000 GitHub stars on its project repository. It combines monitoring with status pages, offering a modern,","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":177,"end":188,"name":"Uptime Kuma"},{"start":237,"end":248,"name":"Uptime Kuma"}]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"best_in_category","excerpt":"Based on current comparisons, here are the top open-source status page tools for displaying uptime and incident history:\n\n## Top Picks\n\n**1. Uptime Kuma**\nThe most commonly recommended self-hosted option. Uptime Kuma supports over 90 monitor types (HTTP, TCP, ping, DNS, cron jobs, and more) alongside notification channels including Slack, Discord, Telegram, PagerDuty, and email, and its interface","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":141,"end":152,"name":"Uptime Kuma"},{"start":205,"end":216,"name":"Uptime Kuma"},{"start":334,"end":339,"name":"Slack"},{"start":341,"end":348,"name":"Discord"},{"start":350,"end":358,"name":"Telegram"},{"start":360,"end":369,"name":"PagerDuty"}]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"comparison","excerpt":"Here's how the self-hosted status page landscape breaks down by scale, with a few tools that genuinely span both ends.\n\n## What \"scaling\" actually means here\n\nFor a startup, you mostly need: a status page live in an afternoon, minimal infra, low maintenance. For an enterprise, you need: multi-team RBAC, SSO, audit trails, private/internal status pages, subscriber notifications at volume, API/Terra","excerpt_withheld":false,"withheld_reason":null,"highlights":[]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"problem_solving","excerpt":"# Self-Hosting an Auto-Updating Status Page\n\nThe good news: several open-source tools handle both the monitoring *and* the status page in one package, so checks and status updates aren't separate systems you have to wire together manually. Here's how to approach it.\n\n## Option 1: All-in-one tools (easiest — monitoring + status page combined)\n\n**Uptime Kuma** is the most popular choice for a reason","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":347,"end":358,"name":"Uptime Kuma"}]},{"engine":"anthropic","answered_on":"2026-08-10","prompt_intent":"recommendation","excerpt":"## Top pick: OpenStatus\n\n**OpenStatus** stands out as the best fit for your needs. It's open source and self-hostable under AGPL-3.0, and features beautiful, customizable status pages with custom domains, password protection, maintenance windows, and subscriber notifications via email and RSS.\n\nIt's also actively maintained — if you want an open source status page that feels modern rather than a 2","excerpt_withheld":false,"withheld_reason":null,"highlights":[{"start":13,"end":23,"name":"OpenStatus"},{"start":27,"end":37,"name":"OpenStatus"}]}]}]}