SessionX Browser

Some work needs many browser sessions that genuinely cannot see each other - agencies running client accounts, QA teams testing per-tenant behaviour, ad and marketplace operations verifying what different regions actually get served. A normal browser is the wrong tool for this. Profiles leak state through shared storage and a shared fingerprint, and running one browser per session does not survive contact with a few hundred of them. Doing it by hand is worse: every session needs its own proxy, and mismatching a session with the wrong endpoint is both easy and silent. So the real problem was not isolation on its own. It was isolation at a scale where a person can still find the session they want, hand it to a colleague, and be sure it launched with the right network route attached.

Treat a session as a record, not a window. Each profile owns its storage, its fingerprint and its assigned proxy, and those travel together - launching a profile is the only way to use it, so a session can never come up with someone else's network route by accident. Above the individual profile sit the structures a team actually needs: workspaces to separate bodies of work, groups and tags to slice hundreds of profiles into something navigable, and per-profile status so an operator can see what is running before starting anything. The management surface is a table rather than a grid of cards, because at this volume the questions are comparative - which profiles use this proxy, which were last opened in July, which belong to this group. A table answers those; a card wall does not.

A native Windows desktop application, not a web app in a wrapper. Managing browser engines, per-profile storage on disk and real network configuration needs a level of system access a page cannot have. The profile list is built for volume from the start: server-side pagination, sorting, and a summary row that reports totals - profiles, running, idle, and how many have a proxy attached - so an operator can spot an unconfigured session without reading the table. Each row exposes the two actions that matter, launch and configure, at the row itself rather than behind a menu. Proxy assignment is surfaced in the list rather than buried in profile settings, because a wrong or missing proxy is the failure operators most need to catch early. Access is invite-only, issued by an administrator, with the desktop client distributed as a signed Windows build.