OSS TanbouOn this page
Overview
OneUptime combines uptime monitoring, metrics, logs, traces, error tracking, alerting, on-call, incident response, and status pages in one monitoring and observability platform. It can be self-hosted with Docker Compose or deployed to Kubernetes with Helm.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Bring monitoring and telemetry into one operational surface
Alongside uptime checks, OneUptime covers metrics, logs, traces, and error tracking so detection and investigation can share one observability platform.
Sources: [2]
Connect alerts to on-call, incident response, and status pages
The platform extends beyond signal collection into paging, incident handling, and public status communication, reducing handoffs between separate operational tools.
Sources: [2]
Self-host with Docker Compose or Kubernetes Helm
The README documents a single-server Docker Compose path and a Helm path for Kubernetes, supporting evaluation and larger deployments.
Sources: [2]
Best fit
Fits teams consolidating several monitoring and incident-response tools
It is relevant when monitoring, observability, on-call, incidents, and status pages are currently split across several services and the team wants one self-hosted operational platform.
Sources: [2]
Before adoption
Plan capacity, backup, and upgrades for the integrated stack
Because telemetry, incidents, and status services share the platform, review storage growth, persistence, backup, availability, and upgrade procedures together.
Sources: [2]
Replace example secrets and add production TLS before exposure
The Compose quick start tells operators to copy config.example.env and replace it with strong random secrets. Public deployments also need production URLs, credentials, TLS, and persistence.
Sources: [2]
Official sources
- [1]OneUptime/oneuptime repository(2026-10-01)
- [2]OneUptime README(2026-10-01)
- [3]OneUptime 14.0.10 release(2026-10-01)
- [4]OneUptime root license(2026-10-01)
- [5]OneUptime Enterprise License(2026-10-01)
Supplemental curator note
OneUptime is a candidate when uptime monitoring, telemetry, alerting, on-call, incident response, and status pages should live in one operational platform. Community code is Apache-2.0 outside ee/, while ee/ has a separate Enterprise License.
Try it in 3 steps
- 1
Clone the release branch
Follow the documented Docker Compose path and clone the repository's release branch with a shallow checkout.
git clone --depth 1 --single-branch --branch release https://github.com/OneUptime/oneuptime.git && cd oneuptime - 2
Create the configuration file
Copy the example configuration, then replace passwords, secrets, URLs, and other deployment values before public exposure.
cp config.example.env config.env - 3
Start OneUptime
Start the Docker Compose stack, then open http://localhost and create the first account.
npm start
Growth
Growth trends · Last 30 days
7,693 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 2,850
- Open PRs
- 96
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- devops
- monitoring
- incident-response
- incident-management
- status-page
- observability
- on-call
- Stars
- 7,693
- Forks
- 468
- Watchers
- 28
- Open issues
- 203
- Contributors
- 121
- Owner type
- Organization
- Primary language
- TypeScript
- License
- Not determined
- Repository last updated
- Oct 2, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- Langfuse35,298 Stars
4 shared tag(s) · 2 shared category(s) · Same language
connect LLM application tracing, evaluation, and prompt improvement
TypeScript - openstatus9,161 Stars
4 shared tag(s) · 2 shared category(s) · Same language
manage monitoring, status pages, and incidents as code
TypeScript - Prometheus66,347 Stars
4 shared tag(s) · 2 shared category(s)
monitor and alert on time-series metrics with PromQL and pull-based collection
Go - Dokku32,159 Stars
4 shared tag(s) · 2 shared category(s)
turn a single Linux VM into a PaaS from git push through build, release, and routing
Go - Rancher25,946 Stars
4 shared tag(s) · 2 shared category(s)
Unify access and operations across multiple Kubernetes clusters
Go - Gatus12,221 Stars
4 shared tag(s) · 2 shared category(s)
run HTTP, TCP, DNS, and other active checks with conditions, alerts, and a status page
Go
Report incorrect information
Tell us if any listing information is incorrect or outdated.