Every profile.
A world of its own.

Profiles and browser engines use separate storage. Creating or duplicating a profile does not copy another profile’s signed-in sessions. Identity consistency checks reflect the native browser and operating system.

Dry-run validates a template without creating profiles. API clients can use a stable idempotency key and inspect the saved batch receipt after an interrupted response, avoiding duplicate creation.

An import preview accepts up to 500 lines, expires after 10 minutes, and skips duplicate email addresses. It creates local profiles; account creation and website sign-in remain separate. Location targeting must match the observed connection at launch.

The desktop list shows 50 profiles per page. Selection is retained across pages, while select-all applies to the current page. Start, stop, and recoverable deletion are available for selected profiles.

The new profile receives its own ID and storage. Existing cookies and signed-in browser sessions are not cloned. Edit a stopped profile to adjust its connection and environment before the next launch.

RevBrowser presets include native Chromium, Windows, macOS, Linux, Android phone, and Android tablet. They adjust advertised identity and client hints; they do not install another OS or enable touch. Fingerprint regeneration is a separate Camoufox capability.

Stop the profile, change Enable proxy, save, and launch again. System routing can use an already connected OS VPN or WireGuard tunnel. RevANT does not connect or manage that VPN. Enabled-proxy failures do not silently use the system route.

The observed country determines the regional locale, while account location requirements are checked independently. Website account settings or cookies can still affect displayed language. Host Windows synchronization is a separate owner-controlled opt-in, off by default.

Auto-close can be changed while the profile runs. Turning it off keeps the browser window open with a warning while managed requests remain blocked. Monitoring is periodic; the default interval is 60 seconds, rather than an operating-system firewall guarantee.

A ready-to-start prerequisite check is different from a verified running session. Diagnostics describe the latest stored observations; reading them does not run a fresh network test. Optional engine setup reports progress and explains why Launch is unavailable.

Audits use temporary synthetic browser data rather than saved account sessions. Review individual verdicts, reasons, and private baselines. Network collector checks require your configured collector; missing or unsupported measurements remain not tested.

Protected results expire after five minutes and refresh after a successful connection check when auto-check is enabled. An optional direct positive control runs only after an explicit one-time choice and exposes that connection’s public IP to the test provider.

Exceptions use exact HTTP(S) origins and do not grant camera, microphone, or location access. The starter rule set is intentionally limited. Chrome and Camoufox can retain this setting but do not apply RevBrowser’s tracker policy.

Supported checks inspect timezone, locale, languages, User-Agent, platform, and client hints. Results belong to their measured startup context. A passing configuration check does not establish a unique fingerprint or certify every external website.

Choose a client in API & MCP, issue a scoped credential, merge the generated configuration, and verify health and profile access. The adapter uses stdio. RevANT and the agent run on the same computer; the local HTTP API is not an MCP server URL.

RevBrowser executes page jobs inside the managed engine without a debug port; Chrome and Camoufox use their configured worker. Inspect job status, wait for completion, or cancel. An unknown outcome requires inspection before repeating a page action.

At most three profiles start simultaneously. Stop cancels queued launches too. After a service restart, retained undispatched intents stay paused for explicit Resume or Cancel; uncertain page actions are not replayed automatically.

Auto type starts off for each window. Enable it, focus a field, and paste; Escape or switching fields, tabs, or windows cancels it. RevBrowser is its own Chromium-based engine; Chrome Web Store and Google account synchronization are not included.

Use the portable settings backup to transfer configuration. Restore previews show the profiles to add, and restored profiles remain stopped. Passwords are protected using the destination workspace’s configured credential mode.

Stop all profiles and the launch queue first. Full snapshots use authenticated AES-256-GCM encryption. Restore requires the same OS; cookies may also depend on the original user, machine, browser version, or key store, so signed-in sessions are not guaranteed to transfer.

Recoverable deletion retains profile metadata and browser data in Trash. Full-backup restore validates the file, stages separate directories, and creates new stopped profiles while retaining existing profiles. Preview expires after 10 minutes.

The interval accepts 1–720 hours; retention accepts 2–30 automatic copies. Rotation follows a successful new backup and leaves manual or imported copies intact. The passphrase stays in memory unless you explicitly save it in an available OS vault.

Existing file-based workspaces migrate only through Protect saved credentials. Password protection does not encrypt usernames, all profile metadata, or every browser file. An encrypted workspace backup provides separate protection for exported browser data.

Insufficient agent permissions never fall back to owner access. Backups exclude agent grants and owner API-session credentials, so restore does not revive revoked access. API scopes govern requests; they do not sandbox an agent with unrestricted access to your OS account.