Ovobrowser

Connect isolated profiles to the automation you already use

Run a local-only service, manage profile lifecycles with JSON requests, and receive CDP endpoints for established browser automation frameworks.

Core features free foreverWindows · macOS
Ovobrowser
Preview
POST /browser/open{ "profileId": "demo-01" }_
127.0.0.1Running
POST/browser/createPOST/browser/openPOST/browser/closeHTTP CDP · WS CDP

Local-only service

The service listens on 127.0.0.1 and is designed for tools running on the same computer.

Simple JSON contract

Endpoints use POST with JSON bodies and return a consistent success or failure envelope.

CDP connections

Opening a profile returns HTTP and WebSocket CDP endpoints for automation clients.

Local API · Core capabilities

The right capability at every step

From setup to execution, every capability maps to real work and keeps the context clear and inspectable.

04capabilities

How it works

Keep context visible from initial setup through daily operations.

  1. Start the local service

    Open the API & MCP page and start the service on its displayed loopback address.

  2. Select or create a profile

    Use /browser/list or /browser/create and retain the returned profile identifier.

  3. Open and connect

    Call /browser/open, then connect the returned CDP endpoint to your automation client.

Clear boundaries for different teams

Automation engineers

Connect established browser-control frameworks to Ovobrowser profile lifecycles.

QA and testing teams

Launch repeatable, configured environments from local test runners.

Internal tool builders

Add profile management to schedulers, dashboards, and controlled local workflows.

Frequently asked questions

Is the Local API exposed to the internet?+

No. The current service listens on 127.0.0.1 and is intended for local applications on the same computer.

Does the local service require an API token?+

The current loopback-only service does not require a token or additional authentication header. Do not expose it through an external tunnel or public proxy.

Which automation frameworks can connect?+

The returned CDP endpoints can be used with compatible clients such as Playwright, Puppeteer, and Selenium.

Which request format is used?+

The current endpoints use POST requests with JSON bodies. Responses use a consistent success/data or success/message envelope.

Start with one isolated profile. Make multi-account work simpler.

Download Ovobrowser free and organize accounts, proxies, fingerprints, and team collaboration in one clear workspace.

OvobrowserWindows · macOS
Core features stay free for people and teams