Donut Browser
Donut
Get Started

For sales teams that run AI agents

A private browser for AI sales agents

Sales agents work in prospect lists, CRM records, inboxes and LinkedIn accounts. Donut gives each rep, client or sender account its own profile, with its own fingerprint, proxy and cookies. The browser has no AI model and collects no data. You connect the agent you already use.

Download Donut Browser Explore Pro
  • One profile per rep or account
  • No AI model, no telemetry
  • You approve saves and sends
Compare
An agent gets one task, to research 40 leads and draft intros for review, and works in 6 Donut profiles, one per sales rep. Every profile has its own operating system, fingerprint, time zone, exit IP and cookies, so a site check sees 6 different people. In the comparison, all tabs share one fingerprint and one IP, and the same check links all 6 accounts.Anna · DACH: macOS 15, Europe/Berlin, exit IP 185.72.14.9, own cookies. Louis · France: Windows 11, Europe/Paris, exit IP 91.168.20.44, own cookies. Yuki · Japan: Windows 10, Asia/Tokyo, exit IP 133.106.8.12, own cookies. Lucía · España: macOS 14, Europe/Madrid, exit IP 88.12.140.61, own cookies. Luca · Italia: Windows 11, Europe/Rome, exit IP 93.41.77.150, own cookies. Ola · Polska: Windows 11, Europe/Warsaw, exit IP 83.24.61.201, own cookies.

Six sales tasks for your agent

Each task runs in the profile that holds the right accounts. Copy a prompt into Claude, Cursor, Codex or another MCP client. The agent reads pages and prepares changes. You approve what it saves and sends.

How agents connect to Donut
  1. 01

    Call brief before a discovery call

    Pro

    The agent opens the account in your CRM, the prospect’s website, security page and open roles. It returns a one-page brief with source links, screenshots and five questions.

    In Donut The agent works in your own profile, which is already signed in to the CRM. It never needs your password.

    Ask your agent

    Open the Acme account in my CRM, then Acme’s website, security page and open roles. Write a one-page call brief with source links, screenshots of pages that may change, the main risks and five questions. Do not edit any record.

  2. 02

    CRM cleanup with a review table

    Pro

    The agent checks each account against its website and proposes new values for fields such as company size and industry. You get a table: current value, proposed value, source URL.

    In Donut Before it saves, the agent asks with ask_human. You approve or skip each change on the app’s Agent page.

    Ask your agent

    Open these 12 accounts in my CRM. For each one, check the company website and propose new values for company size and industry, with a source URL. Show me a review table, and ask me with ask_human before you save any field.

  3. 03

    Prospect list from a directory

    Pro

    The agent goes through a trade association or event directory and opens each member page. It writes a CSV with company, website, contact, title, LinkedIn URL where the page lists one, and the reason the company fits. It flags rows with missing fields.

    In Donut Run it in a separate research profile with its own proxy. The crawl then never touches a rep’s signed-in accounts.

    Ask your agent

    In my Research profile, open this directory and each member page. Export a CSV with company, website, contact name, title, LinkedIn URL if the page lists one, and why the company fits our ideal customer profile. Flag rows with missing fields.

  4. 04

    Follow-up drafts after calls

    Pro

    The agent reads yesterday’s calendar events, your call notes and the CRM activity. It saves one draft per account in your mailbox, with the buyer’s own words, one proof link and a next step.

    In Donut It saves drafts only. You read each draft and send it from the same profile.

    Ask your agent

    For each of yesterday’s calls, read the calendar event, my call notes and the CRM activity. Save a draft reply in my Gmail with the buyer’s quote, one proof link and a next step. Do not send anything.

  5. 05

    A profile for every client and sender account

    Solo

    Agencies and SDR teams work many email and CRM accounts, and each rep has a LinkedIn account. The agent can make one profile per account, give each a proxy in the client’s country and keep the profiles in groups.

    In Donut Each profile has its own fingerprint, proxy and cookies, so sessions never mix. LinkedIn allows one account per person, so each LinkedIn profile belongs to one rep. On Solo the agent manages profiles. Browser control starts with Pro.

    Ask your agent

    Create one profile per client in my Clients group, named after the client. Give each one a proxy from my list in the client’s country, and do not use a proxy twice.

  6. 06

    Weekly pipeline check on a schedule

    Solo · Pro

    Record the check once as a recipe: open the stale-deals view, export it and take a screenshot of each deal. A schedule runs it every Monday at 8:30 and emails you if a run fails.

    In Donut Recipe replays use no model tokens. Schedules start with Solo on Donut’s remote machines. Pro adds runs on your own computer and recipes on demand.

    Ask your agent

    Run my Stale deals recipe on the Pipeline profile now. Then read the export and draft a next step for each deal with no activity in 14 days.

You approve every save and send

Tell the agent where to stop. Donut gives it the tools to ask you, and gives you the controls to step in from the app’s Agent page.

Questions with suggested answers
ask_human shows the question and its choices on the Agent page and in a notification. The agent waits for your answer.
A person for sign-ins and checks
request_human_help hands you the profile for a sign-in, a verification or a payment. You hand it back with a note.
Take over a profile
Take over any profile the agent works in. Donut refuses the agent’s calls on it until you hand it back.
Pause all agents
One click pauses every agent. Paused agents can only read your notes and ask you questions.
Progress on long jobs
report_progress shows how far a job is, for example 31 of 80 accounts.
Example of the Agent page in the Donut app: Claude Code asks whether to save 9 field changes to the Northwind account in the CRM, with three suggested answers, a reply field, and the Take over and Pause agents controls.

One identity per rep and account

In one normal browser, every account shares one device fingerprint and one IP address, so sites can link them. In Donut, each profile looks like a separate device to the sites it visits.

Profile Accounts Device Proxy exit Time zone
Maya · AE LinkedIn, Gmail, HubSpot macOS · 1512×982 Chicago, US America/Chicago
Leo · SDR Sales Navigator, Outlook Windows 11 · 1920×1080 Austin, US America/Chicago
Northwind · client Outlook, Apollo Windows 10 · 1366×768 London, GB Europe/London
Kestrel · client Gmail, Pipedrive macOS · 1440×900 Berlin, DE Europe/Berlin
Example values. Each profile also keeps its own cookies, storage and history.
  • 01

    Fingerprint set in the engine

    Wayfern, Donut’s Chromium-based engine, sets each profile’s fingerprint in its C++ code, below the page’s JavaScript.

  • 02

    Proxy or VPN per profile

    HTTP, HTTPS, SOCKS4, SOCKS5 or WireGuard. DNS goes through the same route, and WebRTC leak protection hides your real IP address.

  • 03

    Time zone and language from the IP

    Donut matches them to the proxy’s exit IP and does not launch a profile when they disagree.

  • 04

    Other systems on Pro

    Pro gives a profile a Windows, macOS or Linux fingerprint on any computer, and lets you edit fingerprint values.

Separate profiles stop accounts from sharing one device and one IP address. They do not hide automation: in a 2026 study, FP-Agent detected all seven AI browsing agents it tested. Keep agent work at a human pace and follow each site’s terms. Read the study

Prospect data stays with you

Prospect lists, CRM records and inboxes belong to your company. This is where that data goes when an agent works in Donut.

Hosted AI browser: from Aside’s privacy policy and help pages, retrieved 14 Oct 2026. Aside comparison

What leaves your computer, in two diagrams. Donut Browser: your agent (Claude Desktop, Cursor, Codex) drives Donut through the local API and CDP on 127.0.0.1 and uses the model you choose. Profiles, cookies, history and fingerprints stay on your disk. Websites get the pages your agent visits, through each profile’s proxy. Donut sends nothing to model providers and has no telemetry. Optional sync is end-to-end encrypted, and remote MCP commands pass through Donut’s relay. Hosted AI browser, based on Aside’s privacy policy: with hosted models, model providers get prompts, page snapshots, screenshots and files; an analytics vendor gets your email, plan and device model, on by default; encrypted history and cookies go to the vendor’s cloud when sync is on.

  • No AI model in the browser

    Donut sends nothing to model providers. Your agent sees what it reads, under the terms of the agent you chose.

  • No telemetry

    The app has no analytics, usage tracking or crash reporting.

  • Profiles on your disk

    Cookies, history and sessions stay on your computer. Cloud sync is off by default. If you turn it on, you can encrypt it end to end with your password or run the sync server yourself.

  • Locked profiles

    A password-locked profile is encrypted at rest with AES-256-GCM and runs from a copy in memory.

  • Credentials you can revoke

    Each agent connects with its own dmk_ credential. A revoked credential stops working in about 10 seconds. Donut refuses tools that read local files or export secrets, and hides proxy passwords from the agent.

  • Recipes without passwords

    A recipe records your clicks and typing. It never records passwords.

Remote MCP messages travel through Donut’s API at api.donutbrowser.com to reach your desktop, and they are not end-to-end encrypted. To keep a job on one computer, drive the profile through the local REST API or Playwright over CDP. Both stay on 127.0.0.1.

Share accounts without sharing passwords

On Team, a rep or a rep’s agent opens a shared profile that is already signed in. Nobody needs the password.

Explore Team
Profile locks
Whoever opens a shared profile holds it. A teammate, or a teammate’s agent, cannot launch it until it closes.
Roles
Owner, Admin and Member roles decide who manages seats and profiles.
Clean hand-overs
When an account moves to another rep, the new rep opens the same profile with the same cookies and fingerprint.
$199 a month for 2 seats
Each extra seat is $99 a month. The team shares 100 cloud profiles, and every seat has the Pro tools.

Read each site’s terms before you share an account. LinkedIn does not allow account sharing.

What your agent can do on each plan

Browser control starts with Pro. Solo is for agents that only manage profiles.

  • Free

    $0 / month

    Unlimited local profiles, each with its own fingerprint and proxy. No MCP, so agents cannot connect.

  • Solo

    $29 / month

    Remote MCP. Your agent manages profiles, proxies and groups and asks you questions. Schedules run recipes on remote machines. No browser control.

  • Pro

    $99 / month

    Browser tools: launch, navigate, click, type, read pages and take screenshots. Recipes, the automation API and 200 remote hours a month.

  • Team

    $199 / month

    Pro for 2 seats, then $99 per seat. 100 shared cloud profiles, roles and profile locks.

Compare plans

Questions, answered.

Can an AI agent send LinkedIn connection requests and messages for me?
LinkedIn says it does not allow third-party software that scrapes or automates activity on its website, and it can restrict accounts that use such software (LinkedIn Help). Its User Agreement allows one account per person and does not allow bots. Donut does not change those terms. Let your agent research prospects off LinkedIn and draft the messages. Then send connection requests and messages yourself, from the rep’s profile.
Does Donut include an AI model?
No. Donut has no AI model and sends nothing to model providers. You connect the agent you already use, such as Claude Code, Claude Desktop, Cursor, Codex, VS Code or Zed, and the app writes the MCP config for 22 clients in one click. Remote MCP starts with Solo. The browser tools start with Pro. See AI agents in Donut.
Can one AI agent work several LinkedIn or sender accounts?
For email and CRM accounts, yes: each account gets its own profile, with its own fingerprint, proxy and cookies, and the agent opens a profile by name. For LinkedIn, the User Agreement allows one account per person and does not allow bots, so each LinkedIn profile in Donut should hold one rep’s own account, and the rep does the LinkedIn actions. Separate profiles lower the chance that a platform links your accounts. They do not prevent bans.
Does Donut see my prospect lists or CRM data?
The app has no telemetry. Profiles stay on your disk unless you turn on sync, which you can encrypt end to end. Remote MCP messages between your agent and your desktop pass through Donut’s API and are not end-to-end encrypted. For jobs that must stay on one computer, use the local REST API or Playwright over CDP, which stay on 127.0.0.1.
Can the agent update CRM records safely?
On Pro, yes. Ask it to show the changes in a review table with source URLs and to call ask_human before it saves. You answer on the app’s Agent page. When the CRM asks for a sign-in, the agent calls request_human_help and you sign in yourself. Recipes never record passwords.
Can sales tasks run on a schedule?
Yes. A schedule runs a saved recipe on set days and can email you when a run fails. A recipe replays recorded steps and uses no model tokens. Schedules start with Solo on Donut’s remote machines. Pro adds runs on your own computer and recipes on demand.
Will Donut stop my sales accounts from being banned?
No tool can promise that. Separate fingerprints and proxies stop your accounts from sharing one device and one IP address. Sites can still detect automation by its behavior: a 2026 study, FP-Agent, detected all seven AI browsing agents it tested. Keep the pace human and approve every send.
How is Donut different from Aside for sales teams?
Aside is an AI browser that runs hosted models, or local ones through Ollama or LM Studio. Its privacy policy says hosted AI model providers “receive the model-visible context needed to run the task”, and its help center says analytics sharing defaults to on (privacy policy, help center, retrieved 2026-10-14). Donut has no model and no telemetry, gives each profile its own fingerprint and proxy, and works with the agent you choose. See Donut compared with Aside.
What does Donut cost for a sales team?
Local profiles are free and unlimited. Pro is $99 a month and adds the browser tools an agent needs. Team is $199 a month for 2 seats, then $99 per seat, with 100 shared cloud profiles, roles and profile locks. See pricing.

Every rep and account in its own profile.

Local profiles are free. Pro gives your own agent browser control, and Team shares profiles across the sales team.

Download Donut Browser Donut compared with Aside