Hyperion is an open-source desktop application for managing separate Chromium browser profiles.
I started building it to make browser environments easier to organize: testing sessions, client projects, proxy configurations, extensions, cookies and fingerprint settings can quickly become difficult to manage in a single browser.
What Hyperion does
Hyperion brings several browser workflow tools into one desktop app:
- separate browser profiles;
- HTTP, HTTPS and SOCKS5 proxy configuration;
- extension management;
- cookie import/export and warm-up helpers;
- configurable browser fingerprint properties;
- profile folders, tags, templates and bulk actions;
- English and Russian interfaces.
The application supports Linux and Windows.
Browser fingerprint configuration
Hyperion includes Chromium source patches for browser fingerprint settings. Depending on the profile configuration, Hyperion can present selected values for properties such as:
- User-Agent;
- platform;
- CPU concurrency;
- reported memory;
- screen resolution;
- Canvas and AudioContext noise;
- WebGL vendor and renderer information.
These settings are implemented through a modified Chromium engine. The Electron profile manager and the browser engine are separate components, so engine compatibility matters for fingerprint-dependent features.
Technical overview
The project is built from two main parts:
- an Electron desktop manager for profiles, proxies, extensions and settings;
- a Chromium engine with Hyperion source patches.
The repository also includes Python helpers for cookie operations and browser warm-up workflows.
Hyperion is open source, so the UI, packaging logic and engine patches can be inspected directly in the repository.
What Hyperion is not
A profile manager is not a complete device emulator. Selecting Windows, macOS or a mobile platform changes the browser configuration; it does not run that operating system.
Profile separation is also not an OS-level security boundary. Users should still protect local data, proxy credentials, exports and browser profile directories.
Current state
The project already supports the core workflow: create a profile, configure a proxy, choose fingerprint properties, install extensions and launch the browser.
The next development focus is improving release reliability, engine delivery and validation across supported platforms.
Try it
GitHub repository:
https://github.com/Linchevatel/hyperion-browser
Releases:
https://github.com/Linchevatel/hyperion-browser/releases
If you try Hyperion, I would be glad to hear what works well, what feels inconvenient and which workflows are still missing.
Top comments (0)