A place for every
browser workspace.

Get started

1. Start with the desktop app. See the download page for current platform and release availability.
2. Sign in or create an account and name your organization.
3. Organize shared profiles into groups in the desktop app or web dashboard, when your workspace role allows it.
4. Add an existing proxy if your work needs one.
5. Create a profile with its own name, language, and start URLs.
6. 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, groups, proxies, and permissions.

The web dashboard is for management. It does not launch browsers or run browser sessions on a server. Keep the desktop app installed on each computer where you want to use profiles.

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.

Both local and cloud profiles run in the desktop app. Cloud saving lets a compatible desktop restore supported profile data; it does not provide a hosted browser.

Cloud snapshots currently include supported bookmarks, history, localStorage, IndexedDB, service-worker data, session files, and preferences. New saves also include supported ordinary cookies; older saves may not. Supported Windows cloud profiles also sync browser-saved passwords after the browser closes. Device-bound session keys, payment autofill, extensions, the separate manual account vault, and downloaded files are excluded. Some websites may ask you to sign in again. Cloud restores require the same operating system and browser major version. Each snapshot is limited to 32 MiB compressed and 64 MiB before compression, separately from your workspace storage allowance.

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.

Finish saving before handing over

Only one person can use a cloud profile at a time. Stop its browser and wait for the save to finish before a teammate opens it. If a connection is interrupted, check the profile’s recovery state; unsynced changes do not become a completed cloud save automatically.

When the desktop system tray is available, closing the app window leaves profiles running in the background. To finish your work, choose Quit brwse.io in Settings or the tray menu. Quit closes open profiles and waits for cloud saving; if saving cannot finish, the app stays open so you can resolve it. With no tray available, closing the window follows the same quit process.

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.

In the desktop app, open Proxies, select My proxies, and choose Check. The app tests an HTTPS connection through that proxy from your computer. The latest result and check time are saved to the workspace and appear on the web too. Checks require permission to manage proxies; the web dashboard directs you to the desktop app. A successful check does not guarantee future availability, a particular location, or acceptance by another website.

Reuse profile settings

Open an existing profile and choose Clone settings to reuse its configuration. Edit the copy’s name, group, tags, or assigned proxy before opening it. Cloning settings does not copy browser contents.

Usage and sync

Overview’s Browser time and Proxy data views use the same synced workspace measurements on desktop and web. Proxies’ Data usage tab breaks traffic down by proxy. Compare the same workspace, account, and date range: cloud totals follow profile access, while owners and admins can see workspace local-session totals. Other members see their own local-session measurements.

Traffic is measured by the app and can differ from your provider’s bill. It includes proxy negotiation and excludes outer transport overhead. Interrupted sessions include only measurements received through the last report. New sessions appear after the desktop app syncs; older unmeasured traffic cannot be reconstructed.

Local profile names and browser contents stay on their device; synced local usage contains session measurements, not a profile backup. Older local browser-time history remains on its original device. Counts labeled On this device describe that computer, not every member’s running browsers.

Teams and roles

Owners and admins open Workspace from the sidebar in either the desktop app or web dashboard. Members shows the team directory and role controls, Invitations shows pending invites, and General contains the workspace name and identity. Personal appearance and app behavior remain in Settings.

Manager, operator, viewer, and billing roles do not see this management area. Admins can manage those narrower roles, but cannot change owners or other admins. Group access determines which profiles a member can use alongside their role. Permissions are checked for every action, including after a workspace switch or role change.

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, a local profile’s Accounts tab provides a separate manual account vault. It requires the device’s protected key storage and is not included in cloud snapshots. Password reveal is an explicit action and is unavailable in the web workspace.

On supported Windows and macOS runtimes, browser-saved logins sync with the cloud profile after the browser closes and saving completes. Authorized members who can use the profile can use its saved logins. The Accounts tab shows supported saved website credentials; revealing a password requires the appropriate access and desktop confirmation.

Cloud saves use application-managed encryption; brwse.io can decrypt them. This is not end-to-end encryption. Payment autofill, passkeys, device-bound sessions, and Google account-store credentials do not sync. Do not assume Windows password portability applies to other operating systems.

Get help

Open Support in the app’s Settings or in your web dashboard to manage your workspace support requests. If you cannot sign in, email support@brwse.io.

Include what happened, the app version, and the steps that led to the problem. Keep passwords, proxy credentials, and browser profile archives out of your message.

Current availability