OneUptime

Name: OneUptime
Rating: 1.0 (1 reviews)

Open Source Datadog Alternative

1.0•1 review•

64 followers

Open Source Datadog Alternative

1.0•1 review•

64 followers

Visit website

AI Coding Agents

•

Code Review Tools

•

Cloud Computing Platforms

OneUptime is an open-source Status Page, Monitoring, and On-call software all combined into one. OneUptime replaces services like StatusPage.io, PagerDuty, and Pingdom with one simple platform that lets you monitor your apps and alert your team instantly when downtime happens.

This is the 3rd launch from OneUptime. View more

OneUptime

Launching today

Open source observability with an AI SRE that fixes code

OneUptime replaces Datadog, PagerDuty, Statuspage, Pingdom and Sentry with one open-source app: uptime monitoring, on-call, incident management, status pages, logs, traces, metrics, APM and error tracking. New in this launch: an AI SRE. When an incident opens it correlates your logs, traces and metrics, finds the root cause, and opens a pull request with the fix — verified against your repo's own build and test commands before you see it. Apache 2.0. Self-host free, or use our cloud.

Free Options

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team

Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free

Promoted

Maker

📌

Hey Product Hunt 👋 I'm Simon, one of the makers of OneUptime. Every team I've worked on ended up with the same shelf of tools: Pingdom for uptime, PagerDuty for on-call, Statuspage for customers, Datadog for telemetry, Sentry for errors. Five bills, five dashboards, five places to look at 3 AM — and none of them talk to each other. OneUptime is all of that in one open-source app (Apache 2.0, free to self-host): uptime monitoring, on-call & escalations, incident management, status pages, logs, traces, metrics, APM and error tracking. What's new since our last launch is the part I'm most excited about: OneUptime now closes the loop. When an incident opens, the AI agent correlates your logs, traces and metrics, finds the root cause, and opens a pull request with the fix — verified against your repo's own build and test commands before you ever see it. You review and merge. It's the difference between being told what broke and being handed the fix. A real 2:47 AM run looks like this: • Probes catch checkout latency past your threshold → incident opens automatically • The Payments on-call is called, texted and escalated until someone acks • Your status page updates itself and emails/SMSes every subscriber • The trace waterfall pins it to a slow SELECT … FOR UPDATE on a missing index • The agent opens the PR with the index migration Getting started: • Cloud, free forever plan → https://oneuptime.com • Self-host with Docker Compose or Helm → https://github.com/OneUptime/one... • A Raspberry Pi is genuinely enough for a homelab install We're all here today and would love your questions — especially the hard ones about where an AI agent should and shouldn't be allowed to touch your code. And if you've been stitching five tools together, tell me which combination; I want to know what we still need to replace. 🙏

Report

1d ago

Previous OneUptime Launches

OneUptimeOne Complete Observability platform.

Launched on August 7th, 2024

OneUptimeOpen source Datadog alternative

Launched on January 17th, 2023