Orbit Browser
The browser your profiles open in
Every profile you open becomes its own Orbit Browser process, against its own directory, with the device identity and network route that belong to it. Nothing is shared between them — no cookie, no stored session, and not even the machine they claim to be running on.
Every build is verified on install.
Each profile records the build it was created against.
Division of labour
PowerOps controls the identity. Orbit Browser runs the browser.
Two components, one job each. Keeping them separate is what makes a profile portable and an environment reproducible.
PowerOps
Controls the identity
- Which profile exists, and what it looks like
- Which proxy it connects through
- Which browser build it launches
- What is captured, encrypted and synced
- Who on the team can reach it
Orbit Browser
Runs the environment
- A separate operating-system process per profile
- Its own on-disk browser directory
- The identity PowerOps handed it, for the whole session
- All traffic through the proxy it was given
What Orbit Browser gives a profile
The reasons, in the order they matter to the account inside it.
Chromium-based
Sites behave the way you expect, and Chrome Web Store extensions can be imported and assigned.
A process per profile
Each open profile is its own browser process against its own directory. One closing does not disturb another.
Consistent identity
The device a profile presents is the same on every launch, because it is derived from the profile rather than the machine.
Profile-specific runtime
Identity, network route, stored state and extensions all come from the profile being opened.
Verified installation
A build is checked before PowerOps will install it, so the runtime is never something that merely arrived.
Builds you can go back to
Older builds stay until you remove them, and a profile can be launched with the one it was created against.
Orbit Browser, answered
Is Orbit Browser something I install separately?
No. It comes with PowerOps, which installs it, verifies it and keeps it. There is no second application and no browser version to pick off a list.
Do my extensions work?
Yes. Orbit Browser is Chromium-based, so Chrome Web Store extensions can be imported as packages, shown with the permissions they ask for, and assigned to the profiles that should carry them. A profile only loads the extensions you gave it.
Does the browser update itself underneath my profiles?
No, and this is the one update behaviour worth stating: a browser that updated itself would change the environment an account was set up in without anyone asking. Builds arrive when PowerOps brings them, and a profile records the build it was created against.
One install, a browser for every profile
Orbit Browser comes with PowerOps. Install one application and every profile has a browser of its own.