CR · FFChromium and Firefox, built in-house

Anti-detect on our own Chromium and Firefox

You pick the engine when creating a profile. The fingerprint is spoofed inside the browser, and the platform pins one version for the whole team.

New profile
New profile window: engine, OS, category and proxy selection
How it works

From engine choice to launch

The engine is bound to the profile at creation and never changes.

  1. 01

    Pick an engine

    Chromium or Firefox, chosen when you create the profile. The profile OS matches your computer.

  2. 02

    The app installs the build

    It downloads the version pinned by the platform — the same one for every team member.

  3. 03

    The fingerprint goes into the engine

    The saved fingerprint is passed to the browser unchanged on every launch.

  4. 04

    Updates reach everyone at once

    The platform rolls out new versions. An older version won’t open a profile saved by a newer one.

Builds

Spoofing inside the browser, not on top

Both engines are forks with our patches. Builds for macOS on Apple Silicon and Intel, and for Windows x64.

CR

Chromium — our own fork

Official Chromium with our patches. The fingerprint config is read in C++, with no JS injection.

  • User‑Agent and client hints, platform, cores, memory, screen
  • WebGL — only real vendor and renderer pairs
  • Time zone and locale across all workers
  • Automation without CDP traces
FF

Firefox — a Camoufox fork

Upstream Camoufox plus our patches, carried over to every new release.

  • macOS system fonts, just like on a real Mac
  • Time zone and geolocation matched to the proxy IP
  • Juggler for Playwright
Versions

One version per team

The platform pins the engine version. A profile won’t open in a version older than the one that last saved it.

OS

Profile OS = computer OS

On a computer with a different OS, the profile launches only after you confirm.

Android

A third engine — the emulator

Mobile profiles on real Android, right on your computer. They are labelled as emulation in the app.

Can I change the engine of an existing profile?

No. The engine is chosen at creation and bound to the profile together with its fingerprint.

How do Chromium and Firefox differ?

Chromium is our fork of official Chromium with spoofing in C++. Firefox is a Camoufox fork with our patches. For Playwright, Chromium exposes a CDP endpoint and Firefox exposes Juggler.

Why does the profile OS match my computer’s OS?

Detectors such as Fingerprint.com catch a persona running on a foreign OS. So profiles are created for your computer’s OS, and launching on another OS requires confirmation.

Who updates the engines?

The platform. New versions roll out to everyone at once, and the app downloads them automatically.

Start with 3 free profiles

© 2026 inoBrowserinobrowser.run