OSS Tanbou

manage monitoring, status pages, and incidents as code

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
9,155
Primary language
TypeScript
License
AGPL-3.0
Repository last updated
Sep 30, 2026
On this page

Overview

openstatus combines uptime and API monitoring, status pages, notifications, and incident workflows in an open-source operations platform whose resources can be declared with YAML or Terraform.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Declare monitors and status pages as code

Define monitors, notification channels, and status pages in YAML or Terraform and apply them from the CLI or CI, keeping operational configuration reviewable in code.

Sources: [2]

Connect incident response with public communication

Create, update, and resolve incidents from the dashboard or Slack, then link them to status reports and subscriber notifications over email, RSS, and webhooks.

Sources: [2]

Operate the same resources from CLI, Terraform, and MCP

The tooling includes a human-friendly CLI, Terraform provider, typed API, and MCP server so supported AI clients can work against the same operational model.

Sources: [2]

Best fit

Fits SRE teams that want monitoring-as-code plus public status communication

It is relevant when external monitoring and status pages should not be separate systems and configuration changes should flow through code review.

Sources: [2]

Before adoption

The full self-hosted stack contains several services

The Docker-based setup starts the dashboard, status pages, API, workflows, probes, and data services together. Production deployments should plan persistence and external dependencies separately from a local evaluation.

Sources: [2]

Review AGPL-3.0 network-use obligations

The repository is licensed under AGPL-3.0. Check the source-availability obligations that may apply when operating a modified version over a network.

Sources: [3]

Official sources

  1. [1]openstatusHQ/openstatus repository(2026-09-30)
  2. [2]openstatus README(2026-09-30)
  3. [3]openstatus AGPL-3.0 license(2026-09-30)
Supplemental curator note

openstatus treats monitors and status pages as declarative resources that can be managed through YAML, Terraform, CLI, CI, and MCP against the same API. Self-hosters should also review the AGPL-3.0 terms.

Try it in 3 steps

  1. 1

    Clone openstatus

    Fetch the official repository for the Docker-based evaluation path.

    git clone https://github.com/openstatusHQ/openstatus.git && cd openstatus
  2. 2

    Prepare the Docker environment file

    Copy the example environment file as documented. Replace sample secrets before exposing any deployment.

    cp .env.docker.example .env.docker
  3. 3

    Start the stack

    Open http://localhost:3002 for the dashboard and http://localhost:3003 for status pages after the containers start.

    docker compose up -d
Check the official README

Growth

Growth trends · Last 30 days

9,155 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • alerting
  • incident-management
  • mcp
  • mcp-server
  • monitoring
  • monitoring-as-code
  • observability
  • on-call
  • open-source
  • sre
  • status-page
  • statuspage
Stars
9,155
Forks
778
Watchers
31
Open issues
104
Owner type
Organization
Primary language
TypeScript
License
AGPL-3.0
Repository last updated
Sep 30, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?