Open Source

Self-hosted uptime monitoring.
Run it on your own boxes.

The open-source engine behind ObserveOne. Every monitor type, run from your own boxes. Multi-region. Apache 2.0.

What it does

Production monitoring you run yourself.

Same monitor types the SaaS uses, minus the SaaS. One image, one command.

Coverage

Every monitor type

HTTP and API checks with assertions. TCP and UDP reachability. Database liveness. TLS certificate health. Browser checks. Heartbeats. One worker runs them all.

ObserveOne — Every monitor type
Inverted ping

Heartbeats

For cron jobs and background workers. Your service pings a URL we give you on every successful run. We alert when a ping doesn't arrive in time. Recovery alerts fire when it comes back.

ObserveOne — Heartbeats
ObserveOne — Multi-region

Multi-region

Distributed

Agents pull work from the master. No inbound ports needed on the agent side. Spin one up wherever you need a check to run from.

View docs →
ObserveOne — Dashboard included

Dashboard included

UI included

Sign in, add monitors, watch runs, set up status pages, wire alert channels. Built into the same image, same port. No extra service to run.

ObserveOne — Alerts

Alerts

Alerting

Webhook, Discord, Slack, and email. Bind any channel to any monitor. Bring your own SMTP. No third-party alert vendor sits between you and the outage.

View docs →
$## Investigating
$DB connection saturation in eu-west-1.
$
$## Identified
$Rolling back the 14:02 deploy.
$
$## Resolved
$Latency back to baseline.

Status pages with incidents

Public-facing

Public status pages list your monitors plus an incident timeline you write yourself. Markdown-rendered, XSS-safe, no third party. Backups carry the timeline along with everything else.

$curl -O https://monitor/runs/482/trace.zip
$npx playwright show-trace trace.zip

Failed runs come with traces

Debuggable

Every failed browser run saves the Playwright trace and a screenshot to bundled S3-compatible storage (RustFS, no setup). Download from the run detail page and open locally to see exactly where it broke. Backups bring them along to the new host.

$bun scripts/export.ts --include-artifacts -o backup.oodump.tar.gz
$bun scripts/import.ts --from backup.oodump.tar.gz --force

Backup & restore

Portable

One command dumps the database and every Playwright artifact into a single tar.gz; one restores it on a fresh host. The schema-version guard refuses dumps that don't match the target's migration head, so you can't silently downgrade.

View docs →
${
$ "warnDays": 30,
$ "verifyChain": true,
$ "verifyHostname": true,
$ "expectCnRegex": "^api\\.prod\\."
$}

Deep TLS checks

TLS

Beyond expiry: assert the full chain trusts a public root, the hostname matches the certificate's SAN, and the CN/SAN matches a regex you control. A reverse-proxy swap that quietly serves the wrong cert fails the check instead of slipping into prod.

View docs →
Compare

oo-workers vs Uptime Kuma

Both are self-hosted and open source. Here's where they differ.

Browser checks

End-to-end UI flows, not just an HTTP ping.

oo-workers
Uptime Kuma

API response assertions

Kuma matches keywords; oo-workers asserts on response shape.

oo-workers
Uptime Kuma

Multi-region agents

Run checks from wherever you need them.

oo-workers
Uptime Kuma

Full TLS validation

Kuma reports expiry; oo-workers validates the chain too.

oo-workers
Uptime Kuma

TCP / UDP with payload checks

oo-workers
Uptime Kuma

Export / import via CLI

Move a full monitor set between hosts in one command.

oo-workers
Uptime Kuma

Heartbeats

oo-workers
Uptime Kuma

Status pages

oo-workers status pages include an incident timeline you write yourself.

oo-workers
Uptime Kuma

Backup & restore

DB + browser run artifacts in one .oodump.tar.gz, schema-version guard on restore.

oo-workers
Uptime Kuma

Browser run artifacts

Playwright trace.zip + screenshot saved on failure, downloadable per run, included in backups.

oo-workers
Uptime Kuma

License

Apache 2.0oo-workers
MITUptime Kuma
FAQ

Common questions

oo-workers is the engine the SaaS runs on. Same code. You give up the hosted dashboard, account management, and our regions. You keep your data on your hardware and pick the regions yourself. Apache 2.0.

Nothing. Apache 2.0. No enterprise tier, no usage cap, no telemetry. You pay for the boxes you run it on.

Docker. The README has a copy-paste compose snippet that gets you running. After that, the in-app docs cover the rest.

Kuma is excellent and has a head start on maturity and alert provider breadth. Pick oo-workers when you need browser checks, multi-region, API response assertions, or a CLI export/import workflow. If basic HTTP monitoring from one host covers you, Kuma is the right call.

Yes, mostly. The CLI exports your monitors, API checks, alert channels, QA suites, status pages, and heartbeats. Heartbeat ping URLs are preserved across the move, so services already POSTing to /heartbeat/<token> keep working unchanged. What doesn't carry: incidents (runtime state), alert-channel routing on heartbeats (rewire on the self-host), and a few SaaS-only channel types (Teams, Telegram, SMS).

Apache 2.0 with the patent grant. Full text in the LICENSE file at the repo root.

GitHub Issues: https://github.com/Observeone1/oo-workers/issues. Discussions are open too for questions.

Start for free

Your site is running right now.
Is it working?

Generate tests, monitor production flows, and catch failures before users report them.

No credit card required · Free plan available · Upgrade anytime