A place for every
browser workspace.

Get started

1. Create an account and name your organization.
2. Create a project to group related work.
3. Add an existing proxy if your work needs one.
4. Create a profile with its own name, language, and start URLs.
5. Use the desktop manager to launch the profile on your device.

The active organization is always shown in the sidebar. Switching organizations reloads the workspace’s profiles, projects, proxies, and permissions.

Profiles and saving

A local profile stays on its owning computer. Cloud profiles store shared metadata and supported browser snapshots in the connected backend. A saved name or setting is not a browser snapshot: the interface displays the actual save state separately.

Cloud snapshots currently include supported bookmarks, history, localStorage, IndexedDB, service-worker data, session files, and preferences. Native passwords, device-bound cookies, and payment autofill remain on the device. Cloud restores require the same operating system and browser major version.

Supported browser settings apply on the next launch. Time zone preferences are saved, but the current desktop runtime does not apply them. Before importing, exporting, or changing active profile data, stop its browser and let the device finish writing. Local profile archives can contain sensitive browsing data; store them securely.

Add and check proxies

Add a proxy manually or import proxy URLs with optional credentials. The ordinary proxy list never returns passwords. Assign a saved proxy in a profile’s configuration, then restart the profile for the assignment to apply.

Connection checks show the result from the checking environment. A server check does not establish the route from your desktop or guarantee a third-party website will accept it.

Guided setup

Enter a short description, then choose the profile count, project, location label, and an existing proxy. Review the generated plan before applying it. Guided mode uses deterministic setup rules; it does not claim to be a connected language model.

Teams and roles

Owners and authorized administrators can invite members and manage access. Manager, operator, viewer, and billing roles provide narrower capabilities. Current backend permissions apply to every action, even if an interface is left open.

Invitations expire and can be revoked. Development environments may show an explicit invitation link for manual sharing; delivery by email requires a configured provider.

Saved accounts

On desktop, open a profile’s Accounts tab to manage credentials supported by the local agent. Secrets use the device’s protected key storage. Password reveal is an explicit action and is unavailable in the web workspace.

Portable browser passwords and automatic cross-platform autofill require a qualified runtime bridge. Device-bound passkeys and hardware-backed credentials must not be assumed portable.

Current availability