OneUptime

Visit Website

Introduction

OneUptime is an open-source observability platform that tries to replace a stack of separate tools. It checks that websites, APIs and servers work, collects the logs, metrics and traces your apps send, pages whoever is on call when something breaks and tells customers on a status page, all in one product, so the tool that notices a problem is the one that pages your team. You can use OneUptime Cloud or run it on your own servers.

Monitoring covers websites, APIs, ports, DNS and certificates from probes around the world or inside your own network, plus servers, Kubernetes, Docker, VMware, databases and network devices. Incidents are worked on one timeline, with paging by phone, SMS, email, push, Slack or Microsoft Teams and escalation until someone responds. Public or private status pages keep customers informed and announce scheduled maintenance.

For telemetry, you send logs, metrics and traces with OpenTelemetry, then search them and build dashboards; exceptions, profiles, real user monitoring and security events live in the same place. Workflows and runbooks automate routine work and connect Jira, ServiceNow and other tools.

OneUptime AI investigates new incidents and alerts and posts a root-cause analysis with citations. If you turn fixing on, it can open a pull request with a fix for your team to review. Everything can be automated through an API, a CLI and Terraform, so monitors, status pages and on-call can be managed as code. An MCP server at https://oneuptime.com/mcp lets Claude, Cursor, VS Code with GitHub Copilot or any MCP client investigate incidents, query logs and traces, acknowledge alerts or create monitors.

Self-hosting is straightforward but not tiny: you need a Linux server with at least 8 GB of memory plus Docker, Docker Compose, Git and Node.js. You clone the release branch, set HOST in config.env, and npm start generates random secrets and starts the stack; the first account becomes the admin. The project also offers air-gapped deployments, a trust centre and resellers for enterprises.

For testing teams, OneUptime’s synthetic monitors and API checks extend your test suite into production, and incident data shows which failures your tests never covered. Monitoring is the last line of a testing strategy: it catches what tests, reviews and staging missed. Wire its alerts into the same place your CI failures go, and when an incident reveals a gap, add a test or a synthetic check so the same failure is caught before release next time.

The source code is at OneUptime/oneuptime on GitHub under the Apache-2.0 (outside its ee/ directory) licence, with about 7,800 stars; the most recent commit was on 11 November 2026.

Consolidation is the main reason to choose it: fewer tools means fewer integrations to maintain and one place to look during an incident.

Features

1. Uptime and synthetic monitoring: Websites, APIs, ports, DNS and certificates.
2. Infrastructure monitoring: Servers, Kubernetes, Docker, VMware and databases.
3. Incidents and on-call: Paging, escalation and one timeline.
4. Status pages: Public or private, with maintenance notices.
5. Logs, metrics and traces: OpenTelemetry ingestion and dashboards.
6. Workflows and runbooks: Jira, ServiceNow and more.
7. OneUptime AI: Root-cause analyses and fix PRs.
8. API, CLI and Terraform: Monitoring as code.
9. MCP server: AI clients can query and act.
10. Self-hosted or air-gapped: Run it yourself.

Pros

1. All-in-one: Replaces several separate tools.
2. Free cloud plan: No credit card needed.
3. Free to use: Open source under the Apache-2.0 (outside its ee/ directory) licence, so the core tool costs nothing to use.
4. Actively maintained: The repository had commits as recent as 11 November 2026.
5. Community: About 7,800 GitHub stars.

Cons

1. Breadth over depth: Specialist tools may go deeper in each area.
2. Self-hosting resources: At least 8 GB of memory.
3. Enterprise directory: Some code is under a separate licence.

Usage and Links (Example)

git clone --depth 1 --single-branch --branch release https://github.com/OneUptime/oneuptime.git
cd oneuptime
# edit config.env: set HOST to your domain or IP (without http://)
npm start                          # prints "OneUptime is up!"

Or sign up for OneUptime Cloud, create a project and add your first monitor.

Resources:

• OneUptime website
• GitHub repository

Pricing

OneUptime has a free cloud plan with no credit card required, paid cloud plans on its pricing page and free self-hosting of the open-source edition; enterprise and air-gapped options are by quote.

Recommended for?

1. Small and mid-size teams that want one open-source reliability platform.
2. Regulated organisations needing self-hosted or air-gapped monitoring.

Conclusion

OneUptime is an ambitious open-source alternative to a whole stack of monitoring, paging and status tools.

Try the free cloud plan before committing to self-hosting.

On CheckOps, OneUptime is filed under the Production monitoring & observability and Release & CI gates stages. Related tools listed here include Uptime Kuma, Better Stack, Datadog, SigNoz, Checkly and Grafana. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.