Website monitoring with Playwright Autopilot. Point it at a URL and it generates a real browser test suite for you. Add URL, API, and heartbeat monitoring, incidents, and status pages — run all of it from a dashboard or entirely from the CLI.
| Repo | What it is |
|---|---|
| oo-workers | The monitoring engine, self-hosted. Real Playwright browser checks and JSONPath assertions. If you've run Uptime Kuma and wished it could drive a browser, this is that. Apache-2.0 |
| ObserveOne CLI | Monitors, API checks, heartbeats, incidents, and status pages from the terminal. The config is JSON, so it lives in git like everything else. Apache-2.0 |
| browser-use | Our fork of the browser-use library for AI-driven browser automation. We track upstream and patch here. MIT |
- Playwright Autopilot. Point it at a URL and it generates the browser test suite for you, running on real Chromium. When a test breaks because your UI moved, it tries to fix the selector instead of just going red.
- URL, API, and heartbeat monitoring in one place — uptime, endpoint checks, and cron liveness.
- Incidents and public status pages. Open, assign, resolve.
- It's all JSON.
obs exportpulls your whole setup;obs applyputs it back. Commit it, diff it, review it like code. - CI integration. A GitHub App connects your repos and runs suites on demand, or you generate a webhook token and trigger them from any pipeline yourself.
SaaS — free plan, no card → app.observeone.com
Self-hosted — your own engine on Docker, Postgres, and Redis → oo-workers
CLI
npm install -g @observeone/cli
obs login
obs export # pull your monitoring stack as JSON
obs apply observeone.json # commit it, GitOps itoo-workers and the CLI are Apache 2.0. The hosted platform isn't open source. Each repo states its own license.