Advanced Anti-Detect Custom Browser Development

I'm looking for an experienced **Chromium/browser developer** to help build a custom browser application focused primarily on **anti-detect capabilities, isolated browser profiles, browser fingerprinting, and realistic browser environments**.

I'm looking for someone with genuine experience working with **Chromium/browser internals**, rather than someone who simply operates existing anti-detect browser platforms.

### Project

The goal is to develop a custom browser application with capabilities similar to modern anti-detect browsers, with a strong focus on the underlying browser environment and fingerprint consistency.

The browser should be designed to **avoid detection by modern browser-security and fraud-detection systems, specifically Verisoul and IPQualityScore (IPQS)**.

A key requirement is that profiles should behave like genuine, consistent browser environments rather than simply changing a few obvious fingerprint values.

The application should support multiple independent browser profiles, with each profile maintaining its own configuration, storage, cookies, sessions and browser environment.

### Main Areas

* Chromium-based browser development
* Anti-detect browser development
* Isolated browser profiles
* Persistent profile management
* Custom browser configurations
* Browser version management
* User-Agent and OS configuration
* Screen and device characteristics
* Canvas / WebGL / GPU
* Audio and WebRTC
* Fonts and other browser-exposed characteristics
* Language, locale and timezone
* Fingerprint consistency
* Automation detection considerations
* Browser integrity signals
* Profile-level configuration and management
* Per-profile proxy support

### Fingerprint & Detection

A major focus of this project is understanding how modern systems identify modified, automated, or inconsistent browser environments.

The browser will be specifically evaluated against **Verisoul and IPQualityScore (IPQS)**.

We need someone capable of working at the browser/Chromium level to address detection signals across the overall browser environment, rather than relying on simple JavaScript spoofing or random fingerprint generation.

Experience dealing with:

* Browser fingerprinting
* Chromium-level detection signals
* Automation/headless detection
* WebDriver-related signals
* WebRTC/network behavior
* Canvas/WebGL/GPU characteristics
* Browser storage and persistence
* Device/browser consistency
* Browser integrity checks
* Fraud-detection systems

is highly desirable.

### Proxy Support

The browser will also require **per-profile proxy support**, including authenticated proxies and different proxy configurations.

Proxy infrastructure is not the primary focus of this position — the primary focus is **Chromium, anti-detect functionality, fingerprinting, and browser-level detection resistance**.

### Developer Requirements

Strong experience with one or more of:

* Chromium source code
* C++
* CEF
* Electron
* Chromium internals
* Browser fingerprinting
* Browser profile architecture
* Browser automation
* Windows desktop applications
* JavaScript / TypeScript
* Network/browser APIs

Experience with **Verisoul, IPQS, or comparable browser-security/fraud-detection systems** is a significant advantage.

### What I'm Looking For

I'm looking for someone who can contribute to both the **technical research and development** of the browser.

The project will initially start with a prototype and can progress into a larger production application.

Please include in your proposal:

* Previous Chromium/browser projects
* GitHub or portfolio
* Experience building anti-detect/privacy browsers
* Experience with browser fingerprinting
* Experience modifying Chromium/CEF/Electron
* Experience with browser profiles
* Experience with Verisoul, IPQS, or similar systems
* Your preferred technology stack
* Estimated timeline
* Estimated cost

**Please don't apply if your experience is limited to operating existing anti-detect browsers. I'm specifically looking for someone who understands browsers at the implementation/Chromium level and can develop the underlying technology.**