OneUptime: unified open-source monitoring, incident response and observability platform

OneUptime consolidates monitoring, alerting and incident response in one platform

OneUptime is a comprehensive observability platform that brings together monitoring, alerting, incident response and observability under a single open-source application. OneUptime replaces a whole shelf of SaaS tools with one platform you can self-host for free.

OneUptime features map to traditional separate tools: Pingdom/UptimeRobot for uptime monitoring, StatusPage.io for status pages, PagerDuty/Opsgenie for on-call and alerts, Incident.io for incident management, Datadog/New Relic for APM, Loggly for logs, and Sentry for error tracking. All these capabilities are built into OneUptime's single interface.

Starting with OneUptime Cloud or self-hosting with Docker Compose

The simplest way to try OneUptime is the cloud version at oneuptime.com, which offers a free forever plan with no credit card required. The cloud approach avoids setup entirely and keeps you on the latest version.

For self-hosting, OneUptime supports Docker Compose on a single server. To get started, clone the release branch and create your config:

# Clone the release branch
git clone --depth 1 --single-branch --branch release https://github.com/OneUptime/oneuptime.git
cd oneuptime

# Create your config
cp config.example.env config.env

# Start everything
npm start

OneUptime is then accessible at http://localhost. The README notes that Docker Compose deployment works on Debian, Ubuntu and RHEL, and even on Raspberry Pi for small setups. You must edit config.env to set strong, random secrets before deploying to production.

Deploying OneUptime on Kubernetes with Helm

For production deployments, OneUptime provides a Helm chart. Install via Helm with:

helm repo add oneuptime https://helm-chart.oneuptime.com
helm install oneuptime oneuptime/oneuptime

Full installation instructions and Helm values are documented on Artifact Hub at https://artifacthub.io/packages/helm/oneuptime/oneuptime. An upgrade guide is available for existing installations at `/packages/App/FeatureSet/Docs/Content/en/installation/upgrading.md`. Kubernetes deployment is recommended for larger deployments, high availability and integration with existing cloud infrastructure. The project is compatible with standard Kubernetes patterns and can be deployed on any Kubernetes cluster.

Both Docker Compose and Kubernetes deployments require the same infrastructure: Postgres for operational data, Valkey for caching, and ClickHouse for storing telemetry metrics, traces and logs. The docker-compose.yml file extends a base configuration (docker-compose.base.yml) to define services for the main app, probes, the background runner, and an Nginx ingress. For sizing and capacity planning, see the documentation at `/packages/App/FeatureSet/Docs/Content/en/installation/sizing.md`.

Automated incident detection and end-to-end response

OneUptime detects outages automatically and manages the full incident workflow. When an incident occurs, OneUptime detects it, pages the right person, updates the status page, finds the root cause and opens a pull request with the fix.

For example, probes in multiple regions detect checkout latency exceeding a threshold and open an incident automatically. The on-call engineer is called, texted and push-notified with automatic escalation. The status page updates automatically and subscribers are notified by email and SMS. Traces, logs and metrics are correlated to identify the root cause, such as a slow SQL query. The AI agent then opens a pull request with the fix, verified against repository build and test commands.

Comprehensive monitoring: uptime, status pages, logs, traces and metrics

OneUptime includes comprehensive monitoring capabilities across multiple dimensions. Uptime monitoring supports website, API, IP address, port, SSL, DNS and synthetic monitors from multiple global regions. This multi-region approach detects outages from the perspective of different locations globally.

Status pages are branded and customizable, supporting both public and private visibility. Status pages show incident history and automatically notify subscribers by email and SMS without manual intervention. Log management ingest, stores and searches logs via OpenTelemetry, the open standard for telemetry collection.

APM and traces provide distributed tracing with span-level visibility into application performance. Performance dashboards help identify slow code paths and bottlenecks. Metrics and dashboards allow you to build custom views over your telemetry data. Error tracking shows exceptions with full stack traces and context, capturing the same information that commercial error tracking services like Sentry provide.

On-call schedules and alert routing

OneUptime's on-call module manages schedules and escalation policies. Alerting supports SMS, phone call, push notifications, email and Slack. You define on-call schedules and escalation policies so that when an incident fires, the right person is notified through their preferred channel. Alerts automatically escalate to backup engineers if the primary engineer does not acknowledge within a configured time.

Recent development and licensing

OneUptime is actively developed. The last push was on 2026-09-29, and recent releases include version 14.0.9 from the same date, 14.0.8 from 2026-09-28, and 14.0.7 from 2026-09-27. The project releases regularly with bug fixes and features. The repository includes an upgrade guide for existing installations at `/packages/App/FeatureSet/Docs/Content/en/installation/upgrading.md`. The project is written in TypeScript with package version 14.0.9 as documented in the root package.json.

The project is open source under the Apache 2.0 license for the Community Edition. An Enterprise Edition is also available. All Community Edition features are free to self-host. Community and Enterprise editions are selected via the `APP_TAG` environment variable in config.env: `APP_TAG=release` runs the Community Edition, while `APP_TAG=enterprise-release` runs the Enterprise Edition. Both editions include the same infrastructure: Postgres database, Valkey (Redis alternative), and ClickHouse for telemetry storage.

Docker images are available on both Docker Hub and GitHub Container Registry. The project is documented at oneuptime.com/docs, with examples for Docker, Kubernetes, and OpenTelemetry collectors in the Examples/ directory, including examples for Fluentd, SNMP simulation, .NET OpenTelemetry instrumentation, and OpenTofu infrastructure.

Editorial conclusion

Use OneUptime if you need multiple monitoring and observability tools and prefer open-source or self-hosted solutions. Skip it if you use a tight integration with a specific vendor's ecosystem or need complex multi-tenancy. Start with the free cloud version at oneuptime.com, then evaluate Docker Compose for self-hosting on a single server.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes