openstatus

openstatusHQAGPL-3.0活跃维护

开源的状态页与可用性监控平台,支持故障事件响应和告警通知,帮 SRE 团队对外透明展示服务健康度。

Open-source status page, incident response and uptime monitoring

暂无版本9,257star +8 / 7 天809fork同步于 2026-11-10 17:31 UTC

怎么上手

由 README 提炼,执行前请确认
cp .env.docker.example .env.docker
docker compose up -d
硬件要求按 README 说明

README 未说明显存或 GPU 要求;自托管通过 Docker 运行,private-location 为单个 8.5MB Docker 镜像,手动部署需 Node.js、pnpm 与 Turso CLI。

有 Docker 镜像
下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

开源状态页、事故响应与可用性监控平台,用 YAML 或 Terraform 声明监控项

开源的状态页与可用性监控平台,支持故障事件响应和告警通知,帮 SRE 团队对外透明展示服务健康度。

核心能力

  • 用 YAML 或 Terraform 声明监控项、状态页与通知渠道
  • 提供 CLI、Terraform、MCP server 与类型化 API 统一操作
  • 在 Slack 或 AI agent 中声明、更新和解决事故
  • 28 个全球区域跨 3 家云厂商并行探测
  • 状态页支持自定义域名、密码保护与维护窗口

容易踩的坑

Docker 启动后仪表盘在 3002、状态页在 3003 端口,别访问错;手动部署需先安装 Turso CLI 并配置环境变量与数据库;自托管涉及 libSQL 与 Tinybird Local 等多个服务组件。

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

0 个版本

暂无 release 数据(可能没有发版,或尚未同步)。

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    About openstatus

    openstatus is the open-source status page, incident response and uptime monitoring platform built for infra as code. Run incidents from Slack or your AI agent. Declare monitors and status pages in code. Let your agents update them.

    Monitors, status pages, and notification channels are declared in YAML or Terraform, applied from the CLI or CI, and operable from Claude, ChatGPT, or Cursor over MCP. Available as a managed service or self-hosted.

    Why openstatus?

    • Infra as code — monitors, status pages, and notifications in YAML or Terraform, applied from the CLI or CI
    • Built for humans and agents — MCP server, --json CLI, typed API, read-only or read-write key scopes, every mutation in the audit log
    • Status pages + monitoring in one tool — no need to wire up a separate monitoring service
    • 28 global regions checking in parallel across 3 cloud providers
    • Flat pricing, unlimited members — no per-seat or per-subscriber charges
    • Open source & self-hostable — AGPL-3.0, private-locations run in a single 8.5MB Docker image
    • Incident response — declare and run incidents from the dashboard or Slack, with severity, commander, and a full timeline
    • Incident communication — subscriber notifications via email, RSS, and webhooks

    Status pages

    Beautiful, customizable status pages with custom domains, password protection, maintenance windows, and subscriber notifications via email and RSS. Build trust and keep your users informed during incidents.

    Uptime Monitoring

    Monitor your servers, websites and APIs from 28 regions across multiple cloud providers globally. Get notified via Slack, Discord, PagerDuty, email, and more when your services are down or slow.

    Incident response

    Declare, coordinate, and resolve incidents from the dashboard or right inside Slack.

    • Dashboard — declare an incident, set its severity (critical, major, minor), assign a commander, and move it from open → mitigated → resolved. Every change lands on the incident timeline.
    • Slack — mention the openstatus agent to declare, update, resolve, or add notes to an incident without leaving the conversation. Bind an incident to a Slack channel so the team coordinates in one place.
    • Status page updates — link a status report to an incident so your users see what your team is working on.
    • Agents — the same incident tools are available over MCP, so Claude, ChatGPT, or Cursor can manage incidents too.

    Recognitions

    Tooling

    Everything the dashboard does is reachable from your terminal, your infrastructure code, and your AI assistant — all sharing a single API key.

    • API — typed JSON-over-HTTP (ConnectRPC) with a Node SDK
    • CLI — interactive for humans, --json for agents, YAML monitoring as code
    • Terraform — monitors, notifications, and status pages as HCL
    • MCP server — connect Claude, ChatGPT, Cursor, or any MCP client to your workspace

    Getting Started

    With Docker (Recommended)

    The fastest way to get started for both development and self-hosting:

    # 1. Copy environment file
    cp .env.docker.example .env.docker
    
    # 2. Start all services
    docker compose up -d
    
    # 3. Access the application
    open http://localhost:3002  # Dashboard
    open http://localhost:3003  # Status Pages
    

    Full guide: DOCKER.md

    Self-Hosting with Coolify

    We provide pre-built Docker images for easy deployment:

    ghcr.io/openstatushq/openstatus-server:latest
    ghcr.io/openstatushq/openstatus-dashboard:latest
    ghcr.io/openstatushq/openstatus-workflows:latest
    ghcr.io/openstatushq/openstatus-private-location:latest
    ghcr.io/openstatushq/openstatus-status-page:latest
    ghcr.io/openstatushq/openstatus-checker:latest
    

    Complete Coolify Deployment Guide

    Self-Hosting with Railway

    Deploy the full stack (dashboard, status pages, API, workflows, probes, libSQL, and Tinybird Local) to one Railway project with one click:

    Deploy on Railway

    The template source and the setup instructions are in ephraimduncan/openstatus-railway.

    Manual Setup

    Requirements
    Dashboard

    See apps/dashboard/README.md for full steps (env, db, login, troubleshooting).

    Status page
    1. Install dependencies

    pnpm install

    1. Run the server

    pnpm -w dev:status-page.

    Web (marketing site)
    1. Install dependencies

    pnpm install

    1. Run the server

    pnpm -w dev:web.

    Tech Stack

    Contributing

    If you want to help us build the best status page and monitoring platform, check our contributing guidelines.

    openstatus repository activity

    Contact

    Interested in our enterprise plan or need special features? Email us at [email protected] or book a call.

    License

    Distributed under the AGPL-3.0 License.