Anchor Browser vs Browserless
Anchor Browser gives each session a headful Chromium in its own VM, with managed logins, proxies and hosted agents, and lets sessions run as long as you set. Browserless is a browser API with headless Chrome, Firefox and WebKit, sessions of up to 60 minutes, and an open source core you can run yourself.
The companies and products
Anchor Browser
Anchor Browser is cloud browser infrastructure for AI agents: managed Chromium sessions you control over CDP or a REST API, plus hosted browser agents.
Anchor Browser is a different kind of product from boat. Each session is a headful Chromium in its own VM, and Anchor erases that VM when the session ends. You drive it with Playwright or Puppeteer, with mouse and keyboard calls, or with a task in plain words to a hosted agent. It adds managed logins with MFA, residential proxies, stealth, CAPTCHA solving and session recording. To run your agent's own code, its docs tell you to use a separate sandbox and connect to the browser over CDP.
Browserless
Browserless calls itself a cloud browser automation platform: managed browsers you connect to with one line of code.
You point existing Puppeteer, Playwright or Selenium code at a Browserless WebSocket URL. You can also use BrowserQL, its GraphQL language with stealth and CAPTCHA solving, REST endpoints for screenshots, PDFs and scraping, an MCP server, a CLI and agent skills. Self-serve sessions last 2 to 60 minutes by plan. Between sessions, the browser profile can be kept, and processKeepAlive (Puppeteer) keeps the live browser for a set window. Enterprise adds persistent sessions on dedicated workers. It is a browser product, not a general sandbox: your code gets a browser, not a shell on the machine. This page compares where the two overlap, which is agents that browse.
Which use cases each one fits
For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “27th cheapest of 356” means 26 of the other 355 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.
| Use case and its workload | Anchor Browser: price rank | Browserless: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Neither gives a shell or Docker, and Anchor's own docs send agent code to a separate sandbox, so builds and tests fit boat. | 203rd of 365, with limits $2,000 a month | 198th of 365, with limits $1,771 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An assistant that runs all month hits Browserless's 60-minute cap on Scale, and Anchor erases its VM after each session. A boat sandbox with auto-stop off keeps running, and its disk is saved every minute. | 119th of 361, with limits $1,845 a month | 311th of 361, with limits $6,170 a month | 6th cheapest of 361 $657 a month |
| Code interpreter bursts 100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month | 317th of 336, with limits $2,171 a month | 265th of 336, with limits $350 a month | 189th of 336, with limits $2,000 a month |
| Sandboxes for your users 300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month 300 sandboxes at once is past Anchor's Growth cap of 200 and Browserless's Scale annual cap of 100, and each one would be a browser, not a machine. | 278th of 349, with limits $2,000 a month | 258th of 349, with limits $1,490 a month | 3rd cheapest of 349 $209 a month |
| RL rollouts 1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month | 291st of 349, with limits $12,510 a month | 273rd of 349, with limits $8,600 a month | 39th of 349, with limits $2,000 a month |
| Agent evals 250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month | 353rd of 359, with limits $2,000 a month | 251st of 359, with limits $350 a month | 10th cheapest of 359 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month | 285th of 374, with limits $500 a month | 242nd of 374, with limits $140 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A dev box needs SSH and a disk that stays, which neither browser session has. | 239th of 371, with limits $50 a month | 341st of 371, with limits $350 a month | 19th cheapest of 371 $26 a month |
| Computer-use agents 50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month Both act inside a browser, and Browserless documents Anthropic and OpenAI computer-use integrations. boat streams a full Linux desktop at 60fps, so a computer-use agent can open any app. | 212th of 367, with limits $500 a month | 183rd of 367, with limits $350 a month | 7th cheapest of 367 $200 a month |
| Browser-use agents 50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month Both are built for this. Our default ranking puts boat at #6, Browserless at #13 and Anchor Browser at #19; boat ranks well because the same agent also gets a shell, files and code next to Chromium. | 27th cheapest of 356 $560 a month | 19th cheapest of 356 $350 a month | 7th cheapest of 356 $200 a month |
| Scraping & bots (startup scale) 50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month Both fit startup-scale bots; Browserless adds REST endpoints for screenshots, PDFs and scraping, and Anchor adds managed logins with MFA. | 53rd cheapest of 343 $500 a month | 50th cheapest of 343 $478 a month | 6th cheapest of 343 $90 a month |
| Mass scraping & bots (undetectable) 1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month Our default ranking puts Anchor Browser at #3, Browserless at #11 and boat at #46: both bring stealth, CAPTCHA solving and residential proxies, while boat uses datacenter IPs and you add those yourself. | 4th of 327, with limits $6,175 a month | 19th of 327, with limits $17,150 a month | 73rd of 327, with limits $1,800 a month |
| Parallel red teaming 200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month | 328th of 351, with limits $2,000 a month | 113th of 351, with limits $350 a month | 3rd cheapest of 351 $200 a month |
| GPU eval jobs 10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month | Not ranked: misses a requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
| macOS agents 5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month | Not ranked: misses a requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Anchor Browser | Browserless | boat |
|---|---|---|---|
| What a session is | A headful Chromium in its own VM, erased when the session ends | Headless Chrome, Firefox or WebKit in a managed pool with resource isolation between sessions; the isolation technology is not published | A full Linux VM with its own kernel and root, with Chromium and a desktop inside, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat |
| Shell, code and Docker | No shell; from Growth you can run TypeScript snippets against the page | No shell or SSH; you drive the browser over CDP, BrowserQL or REST | SSH, any language, Docker, systemd and nested virtualization (/dev/kvm) |
| Browser engines | Chromium, headful | Chrome, Firefox and WebKit, headless | Chromium on a 60fps Linux desktop |
| Session length | 180 minutes by default with no upper limit if you raise it; ends after 5 idle minutes by default | 2 minutes on Free, 15 on Prototyping, 30 on Starter, 60 on Scale; Enterprise persistent sessions on dedicated workers can stay running | Auto-stop after 1 hour by default; set up to 30 days, or turn it off on a paid plan for no session cap |
| What is kept between sessions | Profiles keep cookies, local storage and cache, and up to 10 volumes keep files | Persisted sessions keep cookies, localStorage and cache for 1 to 90 days by plan; by default a new browser process starts on reconnect, and processKeepAlive (Puppeteer only) keeps the live browser for a set window | The disk, saved every minute and at each stop, kept at least 14 days after a stop; memory and running programs are not saved; fork a running sandbox from its last 1-minute snapshot |
| Stealth and CAPTCHAs | CAPTCHA solving from Starter, full stealth Chromium on Growth, unique fingerprints on Enterprise | BrowserQL stealth with fingerprint mitigations and CAPTCHA solving | Chromium on datacenter IPs; no fingerprint rotation or CAPTCHA solving |
| Proxies | Residential proxies with country and city targeting, sticky IPs, or your own proxy | Built-in residential and datacenter proxies; your own proxy on paid plans; city targeting on Scale | None managed; you can run your own proxy client inside the VM |
| Logging in to sites | Managed identities with MFA keep logins across sessions, from Starter | A live URL hands the session to a person for a login or 2FA step; 1Password fills logins into the page | Your agent logs in itself, with the credentials you put in the sandbox |
| Ready-made web tools | Send a task in plain words to a hosted agent, or run versioned automation tasks | REST endpoints for screenshots, PDFs and scraping, and an MCP server | None built in; any tool you install runs on the VM |
| Agents | Hosted browser agents (browser-use, OpenAI, Gemini and Anthropic computer use) with human-in-the-loop and webhooks | Agent Run API in beta, up to 15 minutes and 60 steps per turn | Claude Code, Codex, OpenCode and more preinstalled, driven from outside with a prompt, steer and events API |
| Keeping secrets from the agent | Secret values scoped by domain, with TOTP 2FA and 1Password, never shown to the model and typed into the page | 1Password integration fills logins without the value reaching your code | Optional paid AI credentials proxy ($1 a day plus $1 per 1,000 requests): real keys of supported AI providers stay outside the sandbox; other secrets enter it |
| Reaching the machine | Only the CDP socket and the live view URL | Regional WebSocket and HTTPS endpoints and short-lived live URLs; no ports to host on | HTTPS URLs for up to 50 ports, token-protected by default; SSH; raw ports over IPv6 only on sandboxes with no IPv4 of their own |
| Running it yourself | Your own cloud or on-premise on Enterprise | Open source core under SSPL-1.0 you can run with Docker; commercial use needs a paid license | Hosted only |
| Regions | US by default; EU, Asia and Australia on Growth; any region on Enterprise | San Francisco, London and Amsterdam; New York on private fleets | Germany, Finland and France; no region choice, no US or Asia region; snapshot copies can be stored outside the EU |
Every feature Battleships tracks (43)
| Feature | Anchor Browser | Browserless | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Not published | Yes |
| Docker inside | No documented way | No documented way | Yes |
| Nested virtualization | No documented way | No documented way | Yes |
| Root | No documented way | Not published | Yes |
| Systemd | No documented way | Not published | Yes |
| Desktop GUI | No documented way | No documented way | Yes |
| Browser | Yes | Yes | Yes |
| Computer-use API | Yes | Yes | Yes |
| SSH | No documented way | No documented way | Yes |
| Persistent disk | Yes | No documented way | Yes |
| Pause/resume | No documented way | No documented way | Yes |
| Automatic snapshots | No documented way | No documented way | Yes |
| Fork/clone | No documented way | No documented way | Yes |
| Live fork (no pause) | No documented way | No documented way | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | No documented way | Not published | Yes |
| ≥24 h sessions | Yes | No documented way | Yes |
| Idle auto-stop | Yes | Yes | No documented way |
| Wake on request | No documented way | No documented way | No documented way |
| HTTPS preview URLs | No documented way | No documented way | Yes |
| Raw TCP inbound | No documented way | Not published | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | No documented way |
| Secret proxy | No documented way | No documented way | Yes |
| Secret proxy for any API | No documented way | No documented way | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | No documented way | No documented way | Yes |
| MCP server | Yes | Yes | No documented way |
| GPU | No documented way | Yes | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | No documented way | No documented way |
| Self-hosting | Yes | Yes | No documented way |
| BYOC | Yes | Yes | No documented way |
| Open source | No documented way | Yes | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Not published | Not published | Yes |
| Usage per sandbox (API) | Yes | No documented way | Yes |
| Audit logs | Not published | Not published | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | Yes | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Anchor Browser and Browserless are not in the public benchmarks we use, so we cannot say which is faster. Both sell browser time and do not publish the CPU or memory behind a session. For reference, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 in StarSling's run of 3 October 2026 (run 37073680030). Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure.
V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. Anchor Browser and Browserless are not in the public benchmarks we use, so we cannot say which is faster.
Pricing in five scenarios
Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.
| Scenario | Anchor Browser, a month | Browserless, a month | boat, a month |
|---|---|---|---|
| One coding agent, workdays 4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days | $50 · Starter · with limits | $350 · Scale annual · with limits | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $50 · Starter · with limits | $350 · Scale annual · with limits | $26 · $20/mo |
| 50 agents in parallel 50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside | $500 · Team · with limits | $1,026 · Scale annual · with limits | $317 · $20/mo × 3 seats |
| Sandboxes for your users 2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once | $2,000 · Growth · with limits | $410 · Scale annual · with limits | $200 · $100/mo × 2 seats |
| 1,000 short jobs at once 2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month | $2,510 · Growth · with limits | $1,400 · Scale annual · with limits | $8,800 · $2000/mo · with limits |
Anchor Browser: Anchor Browser bills $0.05 per browser-hour, counted to the nearest minute, plus $0.01 for each browser created, paid from credits worth $1 each. The Free plan gives $5 of credits a month with no overage. Plan fees (Starter $50, Team $500, Growth $2,000) become credits. Traffic is extra: $8 per GB through its proxy or $0.20 per GB direct. AI steps cost $0.01 to $0.10 each.
Browserless: Browserless bills in units: one unit is up to 30 seconds of a connected browser, and a reconnect starts a new block. Annual plans cost $25, $140 or $350 a month for 20,000, 180,000 or 500,000 units, then $0.0020, $0.0017 or $0.0015 a unit. Proxy traffic uses 6 or 2 units per MB and a CAPTCHA solve uses 10 units. Monthly billing costs more. There is a $0 Free plan with 2-minute sessions.
Browserless: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, per second while it runs. The $20 plan includes 12 starts a minute and 200 a day; extra starts cost $0.03 to $0.07. A stopped sandbox has no compute charge and keeps its disk for at least 14 days; extra saved snapshots and the AI credentials proxy still charge. A card is required, also for the 7-day trial.
Limits in those scenarios
None of the five scenarios fits either one as written, because each asks for a general machine and both sell a browser session with no shell and no published size. Browserless's 60-minute cap on Scale and its lack of a disk that stays rule out the workday agent, the always-on agent and the 50-agent fleet, and Anchor has no Docker for the fleet. Concurrency caps at 200 browsers on Anchor's Growth and 100 on Browserless's Scale annual, so 300 sandboxes for your users and 1,000 short jobs at once need a custom Enterprise quote on both. boat fits four scenarios. A boat sandbox stops after 1 hour by default unless you turn auto-stop off on a paid plan. At 1,000 short jobs at once, boat's $2,000 plan includes 90 starts a minute, charges for extra starts and refuses starts above 270 a minute, so boat does not fit that scenario either.
| Scenario | Anchor Browser | Browserless | boat |
|---|---|---|---|
| One coding agent, workdays |
|
| None for this scenario |
| One agent that never stops |
|
| None for this scenario |
| 50 agents in parallel |
|
| None for this scenario |
| Sandboxes for your users |
|
| None for this scenario |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Anchor Browser when
your agents need long browser sessions on sites with logins, MFA and bot checks, with residential proxies, sticky IPs and hosted browser agents handled for you.
- Long sessions in their own VM. For jobs that run for hours: sessions last 180 minutes by default, can be raised with no upper limit, and each gets its own VM.
- Logins handled for you. For agents working inside web apps with no API: managed identities with MFA stay logged in across sessions.
- More regions and sticky IPs. For sites that check location: residential proxies down to the city, sticky IPs, and regions in Asia and Australia on Growth.
Use Browserless when
you want a browser API on short sessions with Chrome, Firefox and WebKit, quick REST screenshots and PDFs, stealth for sites that block bots, or a Docker image you can run yourself.
- Run it on your own machines. For browsers that must stay inside your network: the open source core runs from one Docker image, with a license for commercial use.
- Three browser engines. For tests and scrapers that need more than Chromium: headless Chrome, Firefox and WebKit from the same service.
- One call for common jobs. For quick web tasks: REST endpoints return screenshots, PDFs and scraped content without writing a script.
Where boat fits
Anchor Browser and Browserless both sell a browser, not a machine, and they are better than boat at getting past bot checks. If what you are really running is agents that browse and then also write code, run Docker, keep files or serve an app, boat gives each one a full Linux VM with Chromium and a desktop inside. You can also keep a protected browser on Anchor or Browserless and run the rest of the agent on boat.
A whole machine around the browser
Neither gives your agent a shell, and Anchor's own docs say to run agent code in a separate sandbox. That means a second service to pay for and wire up, with every download crossing between the two.
Work that is still there tomorrow
Anchor erases its VM after each session and Browserless ends sessions at 60 minutes on Scale; both carry profiles, and Anchor also carries volumes. boat saves the disk every minute and at each stop, with no compute charge while stopped, and can fork a running sandbox. A boat resume is like a reboot.
Coding agents you drive from outside
Anchor's hosted agents and Browserless's beta agent act in the browser; Browserless's stops at 15 minutes and 60 steps a turn. boat ships Claude Code, Codex and five more that you prompt and steer through one API, and an optional paid proxy keeps real AI keys out of the sandbox.
Use boat when your agent does more than browse: it needs a shell, files, Docker, a desktop or a server next to the browser, and it has to keep its work between runs. Compare it one to one: boat vs Anchor Browser and boat vs Browserless.
boat's own limits
- Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
- Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
- A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
- Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
- boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
- Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
- Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
- Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source
Questions people ask
Is Anchor Browser cheaper than Browserless?
Mostly Browserless, for pure browser work. In our default rankings, browser-use agents cost $350 a month on Browserless and $560 on Anchor, and startup-scale scraping $478 against $500. boat comes to $200 and $90. One agent on workdays needs at least Anchor's $50 Starter plan; on Browserless it does not fit, because Scale ($350) ends sessions after 60 minutes and keeps no disk. For 300 browsers or 1,000 short jobs at once, both need a custom Enterprise quote.
Which is faster, Anchor Browser or Browserless?
Neither is in the public benchmarks we use, so we cannot say. Neither publishes the CPU or memory behind a browser session. For browsing work, speed depends mostly on the sites, the proxy and the model.
Can Anchor Browser or Browserless run Docker?
No. Anchor gives a browser with no shell, plus TypeScript snippets against the page from Growth, and Browserless gives a browser over CDP, BrowserQL or REST. You can run the Browserless Docker image on your own server, but that is your machine. Every boat sandbox has root, SSH, Docker, systemd and /dev/kvm.
How long can a session run on each?
Anchor sessions last 180 minutes by default and you can raise that with no upper limit, but the VM is erased at the end. Browserless allows 2 minutes on Free up to 60 on Scale; Enterprise persistent sessions on dedicated workers can stay running. A boat sandbox stops after 1 hour by default, you can turn auto-stop off on paid plans, and it keeps its disk for at least 14 days when it stops.
Which is better at getting past bot checks?
Both are built for it, with stealth, CAPTCHA solving and residential proxies. Anchor adds managed logins with MFA, sticky IPs and unique fingerprints on Enterprise, while Browserless offers BrowserQL with fingerprint mitigations and datacenter proxies too. boat runs Chromium on datacenter IPs and solves no CAPTCHAs.
Can I self-host Anchor Browser or Browserless?
Browserless has an open source core under SSPL-1.0 that you can run with Docker, and commercial use needs a paid license. Anchor offers your own cloud or on-premise only on Enterprise, through sales. boat is hosted only.
Try boat
Install the CLI, then run boat new.
7-day free trial
More comparisons
- boat vs Anchor Browser
- boat vs Browserless
- Browserbase vs Anchor Browser
- Browser Use vs Anchor Browser
- Steel vs Anchor Browser
- Hyperbrowser vs Anchor Browser
- Kernel vs Anchor Browser
- Anchor Browser vs Notte
- Anchor Browser vs Scrapeless
- Anchor Browser vs Zenrows
- Browserbase vs Browserless
- Browser Use vs Browserless