fury-antidetect-browser

A free, open-source anti-detect browser with real team collaboration. Own Chromium fork, works standalone with no server, self-hostable when you need a team. No seats, no per-profile pricing, no telemetry.

furybrowser.dev · Русская версия

Status: in development, and now on both macOS and Windows. The core builds and spoofs; the agent launches profiles; the server and desktop shell work. Builds are on the Releases page, marked pre-release. macOS builds are signed and notarised since 21.09.2026; Windows is not — see below.

Windows works, as of 16.08.2026. The Chromium core built (57 528 targets), the agent runs on it, and tools/verify-windows.ps1 passes 30 claims on a real machine: the config reaches the browser as an inherited HANDLE, argv carries a slot number and nothing else, no process in the tree has a persona string in its command line, and the browser reports the persona's platform rather than the host's. The desktop shell builds to an NSIS installer. This paragraph used to say not yet, and it said so for as long as that was true.

Getting there found eight defects that only running could find — a BSD df flag, a bootstrap that returned success having done nothing, CRLF making git apply claim a patch was stale, PowerShell reading UTF-8 as Windows-1252, a persona leaking through --user-data-dir into every child process, and a beforeBuildCommand that cmd.exe could not execute. They are in the history, one commit each, with what they cost.

Team mode works end to end, as of 18.08.2026. Invite, enrol on a second machine, be let in with one button, send a profile to the server, open it there. Every stage of that path had a defect and one of them — sending a profile — had never worked at all: the fingerprint seed crossed as a number where the server wants sixteen hex characters, so every upload since the endpoint existed died in the request parser. They are in the history with what each looked like from the operator's side.

macOS is signed and notarised, as of 21.09.2026. The Apple Developer enrolment paid for on 15.08.2026 came through that day, and the same evening the 0.1.4 macOS files were rebuilt with the Developer ID and re-uploaded: the application, the core and the disk image each carry a stapled ticket, and Gatekeeper's verdict on a machine that has never seen them is accepted, source=Notarized Developer ID. Open the DMG, drag, open — no right-click, no xattr. The first real run of sign-core.sh and sign-shell.sh found five defects in the scripts themselves, which is in the history; docs/17 is the paperwork.

Windows is not signed. That is a separate certificate, not started, so the installer shows SmartScreen: More info → Run anyway. A macOS download of 0.1.3 or earlier is ad-hoc signed and needs xattr -dr com.apple.quarantine /Applications/Fury.app once; docs/15 walks through both.

Linux is not a target. See the table at the bottom.

Everything that is not done is listed at the bottom, honestly.

Why another one

Anti-detect browsers cost $30–150 a month per team and are closed source, so nobody can check what they actually spoof. We measured the popular ones: in one, the canvas readback was byte-identical to a clean machine — not spoofed at all, while the interface listed it as protected (docs/08).

This is the inverse. Every vector is documented against the Chromium file it lives in, the patches are in the repo, and you can measure it yourself with the bench that ships alongside.

"Self-hosted" is a word others use now too — with a closed core behind a licence key and one token for the whole installation. Here three things come together, each of which exists somewhere on its own and nowhere together: a core you can build and verify, a team with roles, locks and an audit trail, and a server you run yourself that cannot read your bundles (docs/08).

Three ways to run it

Solo is the default. No account, no registration, no database. Profiles and proxies live on your machine. Everything that makes this an anti-detect browser works here in full — the team layer adds nothing to the fingerprint.

Self-hosted is what you turn on when there is a team: projects, per-project access grants, a distributed lock. One binary and Postgres on any VPS — docs/13.

Hosted exists, and it opened only once the condition it was gated behind was met: bundles are encrypted on the operator's machine, so the server holds data it cannot itself read. The address is prefilled on the sign-up screen (srv.furybrowser.dev, desktop/src/defaults.ts) and is editable — a team with its own server clears it and types theirs. It runs with open sign-up, every registration is its own organisation, and it is still somebody else's machine: docs/13 is one command if you would rather that not be true.

What works today

A profile using a Windows 11 / RTX 4060 persona, launched on an Apple Silicon MacBook, reports:

navigator.platform      Win32
userAgent               Windows NT 10.0; Win64; x64 … Chrome/157.0.0.0
WebGL renderer          ANGLE (NVIDIA, NVIDIA GeForce RTX 4060 (0x00002882) Direct3D11 …)
screen                  1920×1080, availHeight 1032   ← the taskbar
Client Hints platform   Windows        brands: … Google Chrome/157
timezone                Europe/Berlin
navigator.webdriver     false

Consistently — in the main frame, in a Worker, and in three kinds of iframe. A disagreement between execution contexts is three lines of JavaScript to find and gives away a spoof more reliably than not spoofing at all.

One exception: speech synthesis voices. On a Mac this profile reports the macOS voices, because the system has no Windows voices and they cannot be invented. For real work, use a persona of the same OS as the computer; see "Open" below.

The noise is deterministic: the same profile produces the same canvas hash on every read, forever. A fingerprint that changes between calls describes a machine whose hardware moves while you watch it, which is worse than an honest one.

How it fits together

desktop (Tauri)  ──socket──▶  agent (Rust)  ──spawn──▶  core (Chromium fork)
     │                           │                        through a relay
     └──HTTPS──▶ server (optional: teams)

• core — Chromium 157 fork, 41 patches; spoofing is in C++, never injected JavaScript
• agent — the only component holding decrypted secrets: proxy relays, launching, the local automation API
• server — organizations, projects, permissions, locking. Deliberately dumb: it never generates a fingerprint and never decrypts a bundle
• desktop — Tauri rather than Electron: a 12 MB download, not 120 MB

Details in docs/01.

Install

If you only want to use it, you do not need any of what follows: docs/15 is two downloads and one command, and it is the page to send anybody who asks how to try this.

How to use the application once it is installed (profiles, proxies, importing from other anti-detect browsers, a team, invitations and project access, updating): docs/19.

Build

The core took 2 h 42 min on an Apple M5 with 10 cores and 16 GB, in the macos-arm64-lowmem configuration — measured on 30.07.2026, not estimated. The checkout and one build directory come to ~39 GB, also measured; fetch.sh still demands 150 GB free and warns about ~100 GB, and that number is a cautious estimate rather than a measurement (docs/03). Everything else takes minutes. Incremental rebuilds after the first are 5-30 minutes depending on what changed; ccache and sccache do not help, because the build uses -fmodules and they miss on everything.

git clone https://github.com/furyteamtop/fury-antidetect-browser && cd fury-antidetect-browser
cargo build --release

cd desktop && npm install && npm run app:build

Building the core: docs/03.

Run it

Start the local daemon — this is the whole solo product:

cargo run -p fury-agent -- serve

Point it at a core binary if it is not beside the agent:

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

Launch a persona directly, without any store, to see the spoofing work:

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

Automation

Six endpoints and one bearer token, off until FURY_API_PORT says otherwise. examples/ has four working scripts — curl, Playwright, Puppeteer, and the one people actually want: run a job across every profile, one at a time, never leaving a browser open on a failure.

MCP server, built in. Open AI assistants in the sidebar and press Connect: Claude Desktop, Cursor, Claude Code or any MCP client can then create profiles and proxies, open profiles, go to sites, read pages, click, type, take screenshots and warm profiles up, by asking in plain words: "open every profile tagged warm, check t