Self-host

Guides and reference in this section.

Quickstart

Run oo-workers, the open-source self-hosted ObserveOne engine, with one docker compose up. Eight probe types, a scheduler, and an admin UI on your own infrastructure.

Monitor types

The eight probe types oo-workers ships: HTTP uptime, API checks with JSONPath assertions, Playwright browser tests, TCP and UDP probes, database liveness, TLS certificate checks, and heartbeats.

Alerts

oo-workers alerts on status transitions to webhook, Discord, Slack, or email channels. Outage fires on SUCCESS to FAILED, recovery on FAILED to SUCCESS; sustained failure stays quiet.

Status pages and incidents

Public, server-rendered status pages at /status/<slug> with 90-day uptime bars, plus operator-authored incident timelines for narrating outages.

Multi-region

Run probes from multiple locations by attaching stateless regional agents to your master. Agents need only outbound HTTPS; the master schedules and aggregates results.

API keys and deployment

Authenticate the oo-workers API with email/password or bearer API keys, mint and revoke keys, and expose the dashboard safely behind TLS.

Backup and restore

Take a portable, schema-versioned snapshot of an oo-workers instance (config plus execution history, optionally S3 artifacts) and restore it on another host.