Donut Browser

Donut Browser describes each profile as a separate environment with its own fingerprint, cookie store, and proxy or WireGuard VPN. In practical terms, a profile keeps its browser data distinct from other profiles on the same device.

The provider says profiles, cookies, and logins stay on the user’s device rather than going to its servers. Its feature descriptions also include WebRTC leak protection and routing DNS through the profile’s proxy. These are vendor descriptions, not independent assessments of how a platform will interpret a profile.

A password-locked profile is described as encrypted at rest, while ephemeral profiles are stored in RAM. Before choosing a storage mode, check which profile data needs to persist and who needs access to it.

Ask what account and plan are needed for each paid feature or cloud service; the terms say the free plan does not require an account, while paid features and cloud services do. Then ask support to identify which plan covers the intended workflow, since Solo includes commercial use and email support.

For a team, ask how the shared-profile lock works when a person opens a profile and what happens when that person closes it. Also clarify the trade-off between end-to-end encryption and remote browser or Cookie Bot use: the Team page says both require profiles without end-to-end encryption.

If a bug needs reporting, the About page recommends filing reports publicly on GitHub. The same page directs support, security, press, and licensing questions to one email address. Before registering, ask support to map the intended setup and integrations to the relevant plan.

The pricing page lists Solo at $29 per month and Pro at $99 per month, both billed monthly. The docs specify 20 cloud profiles for Solo; the pricing page lists 20 cloud profile backups and 40 Cookie Bot hours for that plan. Pro includes 50 cloud profile backups and 200 remote execution and Cookie Bot hours, according to the pricing page.

Team costs $199 per month and includes two seats, according to the pricing page. Additional Team seats cost $99 per seat on that page; the Team page lists the additional-seat price as $99 per month. Teams with five or more seats can ask for a discount, according to the Team page. Enterprise has custom pricing and an annual contract, according to the pricing page.

The vendor describes local profiles as free, separately from its cloud profile allowances. Paid plans are billed in advance monthly or annually, with prices in US Dollars unless stated otherwise. The terms say payments are final and non-refundable except where applicable law requires a refund. Commercial use requires a paid plan after a two-week trial, according to the docs. An active Pro subscription or higher grants a commercial license for proprietary use while the subscription lasts.

In Team, a shared profile locks when someone opens it and remains locked until that person closes it. The provider describes Team as a service for sharing accounts and synced browser profiles. It includes API, MCP for users’ own AI agents, remote browsers, and fingerprint control with each seat.

For local automation, the Pro page says Playwright and Puppeteer can attach to any profile over CDP, and automation on the user’s machine uses no remote hours. The same page lists MCP support for Claude Code, Cursor, and Codex.

Remote browser sessions and Cookie Bot runs draw from pooled remote hours in Team, while Cookie Bot uses the same remote hours as cloud browser sessions. The docs say Free excludes remote MCP, Cookie Bot, and scheduled recipes. Pro includes 100 automation requests per minute, according to the pricing page.

The terms limit the software to personal computers and say it may not be operated on servers or hosting and cloud environments. That condition matters alongside Enterprise’s listed self-hosted infrastructure, so ask the provider how the two descriptions apply to the intended setup.

Cloud services are limited to subscribers of applicable paid plans and may have usage limits, according to the terms. Cancellation takes effect at the end of the current billing period, when cloud-synced profiles and associated data are permanently deleted.

The terms require prior written consent to incorporate Donut Browser into a product or service for third parties. They also cap total liability for claims at the amount paid in the 12 months before the claim. The homepage states that the app is open source under the AGPL-3.0 license. The About page says the Wayfern browser engine is a binary and is not open source. Check the applicable license and usage terms before building a third-party service around the application.

Donut Browser lists local storage, optional encrypted sync, profile import, and cookie-handling tools among its controls.

• The provider says profile data is stored on the user’s device, with optional end-to-end encrypted sync.
• The app is listed as open source under the AGPL-3.0 license.
• The docs describe importing Chromium profiles, including cookies and passwords, and support cookie import, paste, export, and storage-state copying.
• The provider lists macOS, Windows, and Linux availability.
• DNS blocklists are included for ad and tracker blocking, according to the provider.

Before relying on sync, check whether the optional cloud backup matches the intended data-handling approach; the provider says it is off by default and can be self-hosted.

Local profile use and paid cloud or automation needs point to different parts of Donut Browser’s offer. The provider describes the app as running isolated browser profiles, while its Pro page says Pro is for people who automate profiles.

The Free plan does not require an account, but an account is required for paid features and cloud services. The terms say users must be at least 16 years old.

Before registering, match the intended work to local storage, cloud profiles, shared access, and automation, then check the relevant account and age conditions.

Compare services by where profiles are stored, how cloud access and seats are charged, which automation interfaces are supported, and how terms address data handling. Ask providers to explain how those conditions apply to your workflow before choosing between options.

Does the Free plan require an account?

No; the pricing page describes Free as always free and says it does not require an account. The terms distinguish that plan from paid features and cloud services, which do require an account. Check whether the work depends on cloud access before treating the free-plan condition as sufficient.

What happens to cloud-synced profiles after cancellation?

The terms say cancellation takes effect at the end of the current billing period, when cloud-synced profiles and associated data are permanently deleted. Plan data retention around that point, and check which information needs to be preserved outside the cloud service before cancelling.

Does local automation use remote hours?

The Pro page says automation on a user’s own machine uses no remote hours. It also says Playwright and Puppeteer can attach to any profile over CDP. Clarify whether a workflow stays local or uses remote browser sessions, since the provider separates those uses.

What does the Team profile lock do?

The Team page says a shared profile locks when someone opens it and stays locked until that person closes it. This gives teams a defined handoff condition for shared profiles; check how that condition fits the team’s expected access pattern.

Which terms govern commercial use?

The docs say commercial use requires a paid plan after a two-week trial. The terms say an active Pro subscription or higher grants a commercial license for proprietary use while the subscription lasts. Review both conditions against the intended use before registering.

Fits if… local profiles meet the workflow, or the applicable paid plan covers its cloud, team, or automation needs.

Probably not if… the intended setup depends on operating the app on servers or hosting environments, which the terms prohibit.

The app is open source under the AGPL-3.0 license.