Documentation
Morrow docs
Morrow is persistent, fingerprint-resistant browser infrastructure. Create a profile once, log in once, and come back tomorrow — the browser is still there, still authenticated, and still hard to fingerprint. Every profile is a real, persistent Camoufox browser with a stable, spoofed fingerprint that stays consistent across restarts.
Four surfaces, one browser
A profile can be driven from four directions at once, all sharing the same identity, cookies, and login state:
Dashboard
A human, through the live viewer and Take Control — mouse, scroll and keyboard go straight to the remote browser.
REST
One-shot scrape, screenshot and content endpoints, with or without an authenticated profile behind them.
Playwright
Any stock Playwright client attaches straight to the persistent browser over a websocket.
MCP
An AI agent, through 13 MCP tools operating on the same persistent, optionally logged-in profile.
Start here
New to Morrow? The Quickstart walks through running it, creating a profile, starting it, and opening the live viewer — the fastest path to a working instance.
Already running an instance and want the full request/response reference? /api-docs is a themed Swagger UI backed by an OpenAPI 3 document at /api/v1/openapi.json — point any OpenAPI client generator at it to produce a typed SDK.
What's in these docs
- Profiles — the persistence model, lifecycle, and configuration.
- Stealth & fingerprinting — how Morrow avoids CAPTCHAs and bot walls, honestly scoped.
- Live viewer — the remote browser, Take Control, and the single-controller lock.
- Playwright, Scraping API, and MCP — the three programmatic surfaces.
- Self-hosting — Docker, environment variables, and security posture.
Morrow is self-hosted