OSS Tanbou

run monitoring, status pages, and on-call workflows from one self-hostable service

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
36
Primary language
Rust
License
AGPL-3.0
Repository last updated
Sep 30, 2026
On this page

Overview

uptimepage combines synthetic checks, a public status page, incidents, on-call rotations, and escalation into one Rust-based monitoring service available as both hosted and self-hosted software.

Features and best fit

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

Key features

Monitor services with eight check types

Run HTTP, TCP, ICMP ping, heartbeat, DNS, TLS-certificate expiry, domain-expiry, and browser-login-flow checks from multiple regions.

Sources: [2]

Connect monitoring results to status communication and incidents

Turn failures into incidents and connect them to public status pages, maintenance windows, subscriber updates, and recovery notifications.

Sources: [2]

Operate on-call, Terraform, APIs, and MCP from the same platform

The product includes rotations and escalation policies plus a REST API, official Terraform provider, and MCP server for automation and assisted operations.

Sources: [2]

Best fit

Fits smaller SRE teams reducing tool sprawl from monitoring through paging

It is relevant when monitoring, status communication, alerting, and on-call should live in one self-hostable operational system instead of several separate services.

Sources: [2]

Before adoption

Treat the repository Docker Compose as an evaluation stack

docker-compose.yml explicitly states that TLS is absent, metrics have no authentication, database ports are published, and development credentials are used. Production deployments should follow the separate deployment guidance.

Sources: [3]

Browser-flow and check-frequency limits depend on environment and plan

Browser-flow checks require supported probe environments, while minimum intervals and flow counts vary by plan. Self-hosted deployments should verify the relevant feature settings.

Sources: [2]

Review AGPL-3.0 terms for the intended deployment

uptimepage is released under AGPL-3.0. Check the license conditions before modifying it or operating it as a public service.

Sources: [4]

Official sources

  1. [1]uptimepage/uptimepage repository(2026-09-30)
  2. [2]uptimepage README(2026-09-30)
  3. [3]uptimepage Docker Compose(2026-09-30)
  4. [4]uptimepage AGPL-3.0 license(2026-09-30)
Supplemental curator note

uptimepage combines monitoring with public status pages, incidents, and on-call escalation, while exposing Terraform, REST API, and MCP automation. Its Docker Compose file is explicitly for evaluation and exposes database and metrics ports, so it should not be published unchanged.

Try it in 3 steps

  1. 1

    Clone uptimepage

    Fetch the official repository containing the evaluation Docker Compose stack.

    git clone https://github.com/uptimepage/uptimepage.git && cd uptimepage
  2. 2

    Start the monitoring stack

    Start uptimepage, PostgreSQL, and ClickHouse. This Compose file is explicitly for evaluation, without TLS and with database ports exposed, so do not publish it directly.

    docker compose up -d
  3. 3

    Create the first owner

    Save the one-time sign-in URL, API token, and organization slug that are printed, then open http://localhost:8080 and add the first monitor.

    docker compose exec uptimepage uptimepage bootstrap-owner --email you@example.com
Check the official README

Growth

Growth trends · Last 30 days

36 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • alerting
  • clickhouse
  • devops
  • incident-management
  • incident-response
  • mcp
  • monitoring
  • observability
  • on-call
  • oncall
  • rust
  • self-hosted
Stars
36
Forks
8
Watchers
0
Open issues
51
Owner type
Organization
Primary language
Rust
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?