Introduction

ObserveOne watches things that break in production and tells you when they do. Uptime, certificates, API responses, background jobs, and full browser journeys through your app.

The browser part is what makes it unusual. You give ObserveOne a URL, and it explores the site, writes Playwright tests for what it finds, runs them on a schedule, and repairs the ones that break when your markup shifts. That last piece is called Autopilot.

What it watches#

Monitors check that something is reachable and healthy. Five kinds: URL, TLS certificate, TCP port, UDP port, and database (PostgreSQL, MySQL, Redis).

API checks are saved HTTP requests with assertions. Compose the request, decide what a passing response looks like, then run it on demand or on a schedule.

Heartbeats work backwards. Your cron job pings ObserveOne when it finishes, and if the ping does not arrive in time, that silence becomes the alert.

Autopilot suites are generated Playwright tests. Point one at a URL, it plans a set of scenarios, generates the specs, and reruns them on your schedule. When a selector breaks, healing rewrites the test rather than paging you.

When any of these fail, an alert channel delivers the news to email, Slack, Discord, Microsoft Teams, Telegram, SMS, or a webhook. Failures can open an incident, and incidents can appear on a public status page you host at ObserveOne.

How you drive it#

Three surfaces, same API underneath.

• The dashboard at app.observeone.com for everything interactive: building a check, reading a failed run, editing a generated test.
• The CLI (obs) for the terminal, for CI, and for keeping your monitors in a JSON file that lives in your repo. See Install the CLI.
• The MCP server so a coding agent can create and read monitors on your behalf. See MCP server.

There is also a REST API if you would rather talk to it directly.

Where to start#

If you want something running in the next five minutes, use the Cloud quickstart.

If the vocabulary is the confusing part (what separates a check from a monitor, what an environment does), read Core concepts first.

If you would rather run ObserveOne on your own infrastructure, the Self-host quickstart covers Docker Compose and the environment it needs.