aronhy/pibrowse

What it is

PiBrowse is a Chromium fork packaged as an anti-detect browser: each profile presents a chosen hardware and OS persona, while cookies, proxies and logins stay inside that profile. It targets QA, ad verification, market research, scraping within site terms, and running several legitimate business accounts. The solo mode runs entirely locally with no account or database; team mode adds projects, per-project access and a distributed lock.

The architecture has four parts: a Tauri desktop shell, a Rust agent that holds decrypted secrets and launches browsers, a patched Chromium core, and an optional server handling organizations, permissions and locking but never generating fingerprints or decrypting bundles architecture. Spoofing is implemented in C++ patches rather than injected JavaScript fingerprint surface.

Quick start

For ordinary use, follow the install guide, which describes two downloads and one command. The project itself says this is the page for anyone who wants to try it, and a separate usage guide covers profiles, proxies, imports, teams and updates.

To run from source, the documented flow is:

cargo build --release
cd desktop && npm install && npm run app:build

Then start the local daemon and optionally point it at a core binary:

cargo run -p fury-agent -- serve
FURY_CORE=/path/to/Chromium cargo run -p fury-agent -- serve

To launch one persona without any store:

cargo run -p fury-agent -- launch shared/personas/windows-11-rtx4060-1920x1080.json --proxy socks5://user:pass@exit.example:1080 --timezone Europe/Berlin

These commands come from the README's upstream Fury documentation, and the clone URL shown there points at the upstream Fury repository rather than this one; treat the build steps as upstream-derived until the PiBrowse repository maps them to its own tree.

Verify the spoofing

The repository ships a probe so results can be checked instead of trusted:

cd tools/detect-suite && python3 -m http.server 8791

Open http://127.0.0.1:8791/probe.html in normal Chrome and in the browser, then compare the dumps. fury-detect diff shows changes and fury-detect gate applies release criteria and exits non-zero on failure detection suite. A rendered summary of the last measurement is also published status page.

Constraints and limits

• Platforms: macOS and Windows are supported; Linux is explicitly not a target, and no Linux release or core config is planned.
• Windows builds are unsigned, so SmartScreen shows a warning; the README instructs users to use More info → Run anyway. macOS builds are signed and notarized.
• Building the Chromium core is heavy: about 2 h 42 min on an Apple M5 with 10 cores and 16 GB in the low-memory configuration, with the checkout and build directory around 39 GB. Incremental builds take 5–30 minutes.
• Speech synthesis voices leak across OS personas: a Windows persona on a Mac reports the host's macOS voices. The documented workaround is to use a persona matching the host OS.
• WebRTC candidates are disabled rather than routed through the proxy, and hiding CDP timing is treated as unclosable; cdp: false is the default control.
• Widevine is not redistributed; it is staged from a locally installed Chrome, so a machine without Chrome gets no DRM.
• Licensing is split: agent/, server/, desktop/, shared-rs/ and tools/ are AGPL-3.0-or-later, core/patches/ is BSD-3-Clause, and shared/ schemas are Apache-2.0 license.
• Acceptable use excludes fraud, credential stuffing, phishing and evading law enforcement.

HotRepo's take

On the 11 November 2026 new-project list for TypeScript, PiBrowse recorded 109 stars and 31 forks in a growth window starting 10 November, meaning the entire listed count accumulated in roughly fifteen hours. That is a single snapshot, so it establishes an early spike but not a trend. It did not appear on the all-language daily ranking. The more useful signal is the repository's maturity claims: 41 core patches, a documented 13-check detection gate, a published competitor measurement, and explicit open/closed item lists, including admitted leaks such as speech synthesis and the CDP timing limit. Those are checkable artifacts rather than marketing copy. The mixed upstream Fury material and the unsigned Windows installer are the main reasons to look closely before adopting it.