Open-source, OpenTelemetry-native observability platform that brings logs, metrics, traces, alerts and dashboards into one self-hostable tool.
OneUptime/oneuptime
Open-source observability platform combining uptime monitoring, status pages, incident management, on-call alerts, logs, traces, and metrics in one self-hostable app.
Open-source alternative to:Datadog
PagerDuty
StatusPage.io
- Stars
- 7,754
- Forks
- 476
- Open issues
- 316
- Last commit
- 4 hours ago
What is it?
OneUptime is a self-hostable platform that covers the workflow from detecting an outage to resolving it. It provides uptime monitors for websites, APIs, ports, SSL, DNS and synthetic checks run from multiple regions, along with public and private status pages, incident workflows, and on-call schedules with escalation policies over SMS, phone, push, email and Slack.
Beyond alerting, it also collects logs via OpenTelemetry, stores distributed traces and metrics, offers custom dashboards, and tracks errors with stack traces and release context. Workflows connect the platform to tools such as Slack, Jira, GitHub and Microsoft Teams, and an AI agent can surface anomalies and propose fixes as pull requests.
The project can be run on a single server with Docker Compose or deployed to Kubernetes with a Helm chart. Its Community Edition is Apache 2.0 licensed, while the ee/ directory contains Enterprise features such as SCIM provisioning and audit logs.
Key features
- 01Uptime monitors for websites, APIs, ports, SSL, DNS and synthetic checks from multiple regions
- 02Public and private status pages with subscriber notifications
- 03Incident management with on-call schedules and escalation policies
- 04Log collection via OpenTelemetry, plus distributed tracing and metrics dashboards
- 05Error tracking with stack traces and release tracking
- 06Infrastructure agents for hosts, Kubernetes, Docker, Proxmox, VMware and databases
Use cases
- Replacing separate SaaS tools for uptime checks, status pages and on-call paging with one self-hosted platform
- Running monitoring and incident response for a small team on a single Docker Compose server
- Operating observability for Kubernetes clusters with a Helm-based install
- Correlating logs, traces and metrics to find the root cause of slow database queries
Quick start
- 1
Clone the release branch
git clone --depth 1 --single-branch --branch release https://github.com/OneUptime/oneuptime.git - 2
Enter the project folder
cd oneuptime - 3
Create config.env from the example (then generate random secrets as the README describes)
cp config.example.env config.env - 4
Start everything with Docker Compose
npm start
Things to know
- The ee/ directory is under a separate Enterprise license, and its features ship only in the Enterprise image.
- Self-hosting runs a full multi-service stack on Docker, so it needs a capable server and some setup effort.
Topics
FAQ
- What is oneuptime?
- Open-source observability platform combining uptime monitoring, status pages, incident management, on-call alerts, logs, traces, and metrics in one self-hostable app. OneUptime is a self-hostable platform that covers the workflow from detecting an outage to resolving it. It provides uptime monitors for websites, APIs, ports, SSL, DNS and synthetic checks run from multiple regions, along with public and private status pages, incident workflows, and on-call schedules with escalation policies over SMS, phone, push, email and Slack.
- Is oneuptime free to use? What license does it have?
- oneuptime is open source under the Other license. Check the license terms before using it in commercial products.
- Is oneuptime still maintained?
- Actively maintained. The last commit to oneuptime was on Oct 21, 2026.
- What can I use oneuptime for?
- Replacing separate SaaS tools for uptime checks, status pages and on-call paging with one self-hosted platform Running monitoring and incident response for a small team on a single Docker Compose server Operating observability for Kubernetes clusters with a Helm-based install Correlating logs, traces and metrics to find the root cause of slow database queries
- How do I install oneuptime?
- Clone the release branch: git clone --depth 1 --single-branch --branch release https://github.com/OneUptime/oneuptime.git Enter the project folder: cd oneuptime Create config.env from the example (then generate random secrets as the README describes): cp config.example.env config.env Start everything with Docker Compose: npm start
- Where can I get oneuptime?
- The source code and installation instructions are on GitHub: https://github.com/OneUptime/oneuptime
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
Self-hostable observability platform for logs, metrics, traces, RUM and LLM monitoring, built in Rust and positioned as an alternative to Datadog and Splunk.
Cachet is an open source, self-hosted status page system for communicating service uptime and incidents to users.
Self-hosted alerting for metrics, logs, and SQL data sources, with notification routing and a built-in AI agent and MCP server.
Datadog's open-source agent that collects metrics, logs, traces and profiles from hosts and sends them to the Datadog platform.
A self-hosted AI SRE agent that learns normal log patterns, auto-raises incidents for new anomalies, and routes alerts to Slack, Teams, Telegram and on-call tools.