donutbrowser: Manage Isolated Chromium Browser Profiles

Use at your own risk

OSRepos shares public repositories for knowledge and discovery only. Any installation, execution, configuration, or use of code from these repositories is the user's own responsibility. Always review the repository, source code, dependencies, licenses, and security implications before running or installing anything. OSRepos is not responsible for issues, damages, or losses resulting from third-party repositories.

Overview

Donut Browser is a desktop application for creating and managing isolated Chromium profiles. Each profile keeps its own fingerprint settings, cookies, extensions, and browser data, helping users keep distinct browsing contexts separate rather than juggling them in one browser profile.

It is intended for privacy-focused browsing and workflows that require profile separation, proxy configuration, or browser automation. Its README describes fingerprint spoofing through the Wayfern Chromium fork, but users should treat anti-detection claims as claims about the engine, not as a guarantee of anonymity or of bypassing every detection system.

Key Features

Creates isolated profiles with separate cookies, extensions, fingerprint settings, and data.
Supports HTTP, HTTPS, SOCKS4, and SOCKS5 proxies per profile, plus per-profile WireGuard configurations.
Includes DNS-based ad and tracker blocking that can be configured per profile.
Provides a local REST API and MCP server for automation and integrations.
Supports profile groups, bulk settings, and importing profiles from Chromium browsers such as Chrome, Edge, and Brave.
Offers optional cloud sync for profiles, proxies, and groups, including self-hosting and end-to-end encryption options.
Supports cookie and extension management, and can be configured as the default browser.

Use Cases

Researchers or testers who need separate browser profiles to examine how sites behave with different stored data or configurations.
People managing multiple accounts who want cookies, extensions, and browser data isolated by profile.
Automation developers who want to control profiles through the local API or MCP server.
Users who need a different proxy or VPN configuration for each browser profile.
Small teams or individuals who want to sync profile settings across devices, with the option to operate their own sync server.

Project Facts

Language: Rust
License: AGPL-3.0
Stars: 4k
Forks: 422
Topics: anti-detect, anti-detect-browser, anti-detection, browser, browser-automation, browser-fingerprint-bypass, browser-fingerprinting, browser-management, chromium, management, manager, orchestration, orchestrator, privacy, profile-management
Archived: No

Getting Started

On macOS, install with Homebrew:

brew install --cask donut

Installers are also provided for Windows and Linux. See the README for platform-specific instructions, sync setup, and troubleshooting.

Considerations

Anti-detection behavior is not a guarantee of anonymity or universal compatibility with fingerprinting and anti-bot systems.
Cloud sync is optional. Self-hosting it requires setting up a sync server, and end-to-end encryption is an optional setting.
The project is licensed under AGPL-3.0, which should be reviewed before incorporating or redistributing it.
Linux packaging has platform-specific caveats. For example, the README notes that AppImage may require FUSE libraries, while the Flatpak cannot set itself as the default browser.
The repository reports 4k stars and 422 forks and is not archived; these counts do not establish product security or long-term support guarantees.