Hyperbrowser vs Scrapeless

Both rent you a stealth Chrome in their cloud with proxies and CAPTCHA solving. Hyperbrowser also sells Firecracker sandboxes for running code (CPU, GPU and macOS beta). Scrapeless stays a browser and scraping toolkit, with lower proxy traffic prices and CAPTCHA solving included.

The companies and products

Hyperbrowser

Hyperbrowser calls itself the AI agents' gateway to the internet: cloud browsers, sandboxes, web data APIs and browser agents behind one API and one credit balance.

Its main product is a cloud Chrome session you drive with Playwright or Puppeteer, with stealth mode, residential proxies, CAPTCHA solving, saved profiles and recordings. Next to it Hyperbrowser sells Sandboxes: Firecracker VMs on Ubuntu 24.04 that live up to 24 hours, with memory snapshots, shared volumes and outbound rules. GPU sandboxes and macOS sandboxes (beta) are available on request in the us region. It also sells Fetch, Scrape and Search APIs and hosted browser agents. This page compares where it overlaps with boat: agents that browse, and agents that run code.

Scrapeless

Scrapeless is a web scraping company. It sells Agent Browser, a managed cloud browser, along with AI scrapers, a web unlocker and proxies.

Scrapeless Agent Browser is a different kind of product from boat. You get a Chromium browser in their cloud and reach it over a CDP WebSocket with Puppeteer or Playwright, an MCP server or their agent-browser CLI. Each session gets a random fingerprint, CAPTCHA solving and a residential proxy. You pay per browser-hour plus proxy traffic. It is built for teams that scrape or automate many websites. Your own code runs on a machine you supply.

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. “20th cheapest of 356” means 19 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 workloadHyperbrowser: price rankScrapeless: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Neither is built for a software factory. Scrapeless has no shell on the browser machine. Hyperbrowser's sandboxes do not document Docker inside, and a stopped CPU sandbox cannot be restarted. boat ranks #5.
168th of 365, with limits
$1,206 a month
129th of 365, with limits
$868 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 outlives both: Hyperbrowser sandboxes stop after 24 hours (#85), and Scrapeless sessions are meant to last minutes (#263). boat ranks #6 and has no session cap once auto-stop is off on a paid plan.
85th of 361, with limits
$5,475 a month
263rd of 361, with limits
$2,628 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
241st of 336, with limits
$246 a month
243rd of 336, with limits
$249 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
Each of your users gets a browser on either, not a machine: Scrapeless ranks #222 and Hyperbrowser #241, and Hyperbrowser's Scale plan stops at 100 browsers at once. boat ranks #3, with starts capped per plan.
241st of 349, with limits
$1,029 a month
222nd of 349, with limits
$741 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
257th of 349, with limits
$4,972 a month
244th of 349, with limits
$3,580 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
257th of 359, with limits
$400 a month
256th of 359, with limits
$399 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
238th of 374, with limits
$120 a month
230th of 374, with limits
$97 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
254th of 371, with limits
$73 a month
248th of 371, with limits
$59 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 run computer use inside a browser. boat ranks #7 and streams a full Linux desktop at 60fps where the agent can use any app.
185th of 367, with limits
$360 a month
159th of 367, with limits
$274 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 fit browser-use agents: Scrapeless ranks #13 and Hyperbrowser #20. boat ranks #7 and also gives the agent a shell, files and Docker next to Chromium.
20th cheapest of 356
$360 a month
13th cheapest of 356
$274 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
At startup scale the two are close: Hyperbrowser ranks #36 and Scrapeless #37. Hyperbrowser adds per-page Fetch and Scrape APIs, and Scrapeless adds ready-made AI scrapers. boat ranks #6 and gives each bot a whole machine with a disk.
36th cheapest of 343
$366 a month
37th cheapest of 343
$370 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
Mass scraping of sites with strong bot checks is where both are strong. Scrapeless ranks #5, helped by lower residential proxy prices, and Hyperbrowser #10. boat ranks #73: you set up residential IPs and CAPTCHA solving yourself.
10th of 327, with limits
$9,750 a month
5th of 327, with limits
$7,020 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
Hyperbrowser's sandboxes give red-team agents a place to run tools, and it ranks #58 against Scrapeless's #101. boat ranks #3 and gives each one a full VM with root and Docker.
58th of 351, with limits
$356 a month
101st of 351, with limits
$199 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
73rd of 102, with limits
$1,167 a month
Not ranked: misses a requirementNot 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 requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureHyperbrowserScrapelessboat
Kind of productCloud browser sessions, plus Firecracker sandboxes (CPU, GPU, macOS beta) and fetch, scrape and search APIsA managed Chromium browser for scraping, plus AI scrapers, a web unlocker and proxiesA full Linux VM per sandbox, with a desktop and Chromium inside
Running your own codeFirecracker sandboxes with exec, process and terminal APIs; SSH not documentedNo shell on the machine running the browser; your code runs on your own machine and drives the browser over CDPSSH and root on every sandbox, any language
Machine sizeSandboxes up to 32 vCPU and 256 GiB RAM, disk up to 64 GiB; GPU sandboxes on request; browser size not publishedNot published; you buy browser-hours4 vCPU / 8 GB by default, up to 16 vCPU / 32 GB by plan; 51 to 251 GB disk by size
Session lengthBrowsers up to 12 hours; sandboxes up to 24 hours from VM start3 minutes by default, 15 minutes recommended at most, longer allowedAuto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no session cap
State after a sessionSaved browser profiles; a stopped CPU sandbox cannot be restarted, and files survive on a team volume or in a snapshot taken while it runs; macOS sandboxes (beta) keep a persistent diskBrowser profiles keep cookies, storage, cache and logins, saved when the session closesDisk saved every minute and at each stop and kept at least 14 days; memory is not saved; no compute charge while stopped
Snapshots and forkMemory snapshot of a running CPU sandbox, then start many new ones from itNo fork; several sessions can load one profile, and the last to close is savedFork a running sandbox from its last 1-minute disk snapshot; no memory snapshots
Docker and nested virtualizationDocker builds images on your machine; Docker or /dev/kvm inside a sandbox is not documentedNo shell on the browser machine; you run containers on your own machineDocker, systemd and /dev/kvm on every sandbox
Stealth and CAPTCHAsStealth mode and CAPTCHA solving on paid plans; ultra stealth on EnterpriseRandom fingerprint per session; CAPTCHA solving included at no extra chargeChromium on datacenter IPs; you set up a stealth library and a CAPTCHA service yourself
ProxiesManaged proxies at $10 per GB on paid plans; your own proxy on EnterpriseResidential IPs in 195+ countries, from $1.80 per GB; your own proxy on paid plansNone managed; you can run your own proxy client inside the VM
Web data toolsFetch, Scrape and Search APIs billed per page or query, plus hosted browser agentsAI Scraper tasks for ChatGPT, Perplexity, Gemini and more, plus crawl and search tools over MCPNone; you write or run your own
Desktop and computer useCloud Chrome with live view and recordings; hosted computer-use models in the browserLive URL to watch and control the browser, session replay and Chrome extensionsA full Linux desktop and Chrome streamed at 60fps, with computer-use tools; embeddable
Reaching the machineHTTPS URL per exposed sandbox port through a shared regional proxy; raw TCP not documentedThe browser is reached through Scrapeless endpoints; you host your services elsewhereUp to 50 HTTPS URLs, token-gated; SSH; public IPv6 for raw ports; no dedicated IPv4, and the IP changes at each resume
Coding agentsSandbox base images with the Claude Code, Codex or OpenClaw CLI, run through the exec APIA CLI skill and an MCP server so an agent on your own machine drives the cloud browserSeven harnesses installed, including Claude Code, Codex and OpenCode, with a prompt, steer and events API
Regionsus-central, us-east, us-west and europe-west; asia-south on Enterprise and Select plansMore than 12 data centers, with exit IPs pinned to a country, state or cityGermany, Finland and France; no US or Asia region; you cannot pick one
Every feature Battleships tracks (43)
FeatureHyperbrowserScrapelessboat
Full VM (own kernel)YesNot publishedYes
Docker insideNo documented wayNo documented wayYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesNot publishedYes
SystemdNo documented wayNot publishedYes
Desktop GUINo documented wayNo documented wayYes
BrowserYesYesYes
Computer-use APIYesYesYes
SSHNo documented wayNo documented wayYes
Persistent diskWith your own setupNo documented wayYes
Pause/resumeNo documented wayNo documented wayYes
Automatic snapshotsNo documented wayNo documented wayYes
Fork/cloneYesNo documented wayYes
Live fork (no pause)YesNo documented wayYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesNot publishedYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestNo documented wayNo documented wayNo documented way
HTTPS preview URLsYesNo documented wayYes
Raw TCP inboundNo documented wayNot publishedYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistYesNo documented wayNo documented way
Secret proxyNo documented wayNo documented wayYes
Secret proxy for any APINo documented wayNo documented wayYes
Preinstalled agentsYesNo documented wayYes
Agent harness APINo documented wayNo documented wayYes
MCP serverYesYesNo documented way
GPUYesNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64Not publishedNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayNo documented wayNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNot publishedNot publishedYes
Usage per sandbox (API)YesNo documented wayYes
Audit logsNot publishedNot publishedNo documented way
SSONo documented wayYesNo documented way
SOC 2No documented wayNot publishedNo documented way
HIPAANot publishedNot publishedNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

HyperbrowserNot measured
ScrapelessNot measured
boat28.06 runs/s

Neither Hyperbrowser nor Scrapeless is in the public benchmarks we use, and neither publishes the CPU behind its browsers, so we cannot say which is faster. Hyperbrowser says a browser is ready in under 500 ms, and Scrapeless says its sessions start in under 2 seconds. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15 providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also uses Ryzen 7 9700X hosts and does not promise a CPU model.

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. Hyperbrowser and Scrapeless 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.

ScenarioHyperbrowser, a monthScrapeless, a monthboat, 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
$16 · Free · with limits$399 · Business · with limits$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$73 · Free · with limits$399 · Business · 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
$792 · Scale · with limits$570 · Business · 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
$450 · Scale · with limits$399 · Business · 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
$994 · Scale · with limits$716 · Business · with limits$8,800 · $2000/mo · with limits

Hyperbrowser: Everything spends one credit balance at $0.001 a credit. Browsers cost $0.10 a browser-hour plus $10 per GB of proxy data. CPU sandboxes cost $0.045 per vCPU-hour plus $0.015 per GiB-hour while the VM runs, so 4 vCPU / 8 GiB costs $0.30 an hour. Startup ($30) and Scale ($100) turn their fee into credits that reset each month, and Free gives $5 of credits once.

Scrapeless: Plans of $49, $199 or $399 a month are prepaid into your balance, and unused funds do not roll over. Browser time is $0.09 an hour, discounted on larger prepaid plans, with residential proxy traffic billed per GB on top. A free tier gives 1 session at once and 1 browser-hour a month with no card.

Scrapeless: Plans cost $20, $100, $500 or $2,000 a month. The whole plan price comes back as VM time for that month, billed per second while a sandbox runs ($0.036 an hour at 4 vCPU / 8 GB). Included time does not carry over. Each plan caps starts (the $20 plan: 12 a minute, 60 an hour, 200 a day); extra starts cost $0.03 to $0.07 each. A stopped sandbox has no compute charge, but saved snapshots above the included count 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 Hyperbrowser or Scrapeless as written, because each asks for a general machine, and the prices shown are for browser sessions with no disk that stays and no published size. Scrapeless sessions are built to last minutes, and Hyperbrowser browsers stop at 12 hours, so the workday and always-on agents do not fit either. Concurrency bites next: Hyperbrowser's Scale plan allows 100 browsers at once and Scrapeless's Business plan 400, so 1,000 short jobs at once need a custom Enterprise quote on both. On boat that burst does not fit either: the $2,000 plan includes 90 starts a minute and 2,400 a day, extra starts cost $0.03 to $0.07 each, and starts above 270 a minute fail with 429.

ScenarioHyperbrowserScrapelessboat
One coding agent, workdays
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • machine size per session not published
  • missing persistent disk
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
None for this scenario
One agent that never stops
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • sessions end after 12 h: needs restarts to run 24/7
  • missing persistent disk
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
None for this scenario
50 agents in parallel
  • missing Docker inside
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • missing persistent disk, Docker inside
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
None for this scenario
Sandboxes for your users
  • Scale: max 100 concurrent
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • machine size per session not published
None for this scenario
1,000 short jobs at once
  • Scale: max 100 concurrent
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • Business: max 400 concurrent
  • machine size not published
  • browser-session product, not a general sandbox
  • different kind of product: browser session
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use Hyperbrowser when

your agent needs a stealth browser and also a short-lived place to run code, with memory snapshots, outbound rules, GPU or macOS sandboxes, browser sessions of several hours, or US regions.

  • Sandboxes next to the browser. For agents that browse and also run code: Firecracker sandboxes up to 32 vCPU, with memory snapshots to start many from a warm state; GPU sandboxes on request.
  • Longer browser sessions. For browser tasks that take hours: a Hyperbrowser browser can stay open up to 12 hours, where Scrapeless sessions default to 3 minutes.
  • Outbound rules and US regions. For teams that need control: default-deny outbound rules on sandboxes, and three US regions plus Europe.

Use Scrapeless when

you run many short browser sessions on sites with strong bot checks and want low residential proxy prices, CAPTCHA solving included and ready-made scrapers.

  • Lower proxy traffic prices. For scraping where proxy data is most of the bill: residential traffic from $1.80 per GB, against $10 per GB on Hyperbrowser.
  • Stealth included. For small teams on bot-protected sites: random fingerprints and CAPTCHA solving are included at no extra charge.
  • More sessions at once on prepaid plans. For wide scraping runs: concurrency grows with the prepaid plan, up to 400 browsers on Business, where Hyperbrowser's Scale plan stops at 100.

Where boat fits

If the browser is only one step in what your agent does, both Hyperbrowser and Scrapeless leave the rest of the work somewhere else. boat gives each agent a full Linux VM with Chromium and a 60fps desktop inside, and a disk saved every minute. boat has limits too: plans start at $20 a month, starts per day are capped, and sandboxes run only in Germany, Finland and France. For heavy scraping behind bot checks, keep a stealth browser and call it from boat.

A full VM with Docker, systemd and /dev/kvm

Scrapeless gives no shell on the browser machine, and Hyperbrowser's sandbox docs do not cover Docker inside the VM. An agent that runs docker compose or a database container then needs a second machine you run yourself. Every boat sandbox has Docker, systemd and /dev/kvm.

Jobs that run for days and keep their files

Hyperbrowser CPU sandboxes stop after 24 hours and cannot be restarted; files survive on a team volume or in a snapshot taken while they run. Scrapeless sessions last minutes and keep a browser profile. boat saves the disk every minute and at each stop, and keeps it at least 14 days. Memory is not saved.

Coding agents driven from outside

On Hyperbrowser you write the harness around exec and pass model keys in as environment variables. On Scrapeless the agent runs on your own machine. boat ships seven coding-agent harnesses with a steer API, and an optional, paid credentials proxy for supported AI providers.

Use boat when your agent does more than browse: it needs a shell, Docker, a desktop or a server next to Chromium, and has to keep its files and keep working for hours or days. Compare it one to one: boat vs Hyperbrowser and boat vs Scrapeless.

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 Hyperbrowser cheaper than Scrapeless?

It depends on scale. In our scenarios Scrapeless lands lower for 50 agents in parallel ($570 against $792) and for sandboxes for your users ($399 against $450). Hyperbrowser is lower for one agent on workdays ($16 against $399), since its smaller plans cover it. For 1,000 short jobs at once, both need a custom Enterprise quote. Proxy data is billed on top, at $10 per GB on Hyperbrowser and from $1.80 per GB on Scrapeless. boat comes to $317, $200 and $20 for those first three.

Which is better at getting past bot checks?

Both are built for it. Scrapeless gives every session a random fingerprint and includes CAPTCHA solving, with residential IPs in 195+ countries. Hyperbrowser has stealth modes, residential proxies and CAPTCHA solving on paid plans, plus ultra stealth on Enterprise. boat runs Chrome on datacenter IPs; you add your own services.

Which is faster?

We cannot say. Neither is in the public benchmarks we use, and neither publishes the hardware behind its browsers. Hyperbrowser says a browser is ready in under 500 ms, and Scrapeless says its sessions start in under 2 seconds.

Can Hyperbrowser or Scrapeless run Docker?

Scrapeless gives you a browser with no shell on its machine, so you run containers elsewhere. Hyperbrowser uses Docker on your own machine to build sandbox images, but its docs do not describe running Docker inside a sandbox. Every boat sandbox runs Docker, systemd and /dev/kvm.

How long can a session run on each?

Hyperbrowser browsers run up to 12 hours and its sandboxes up to 24 hours from VM start. Scrapeless sessions default to 3 minutes, with 15 minutes as the recommended maximum, though longer values can be set. A boat sandbox stops after 1 hour by default; on a paid plan you can turn auto-stop off for no session cap.

Can I use either one together with boat?

Yes. Both are reached over CDP, so an agent on a boat sandbox can open a Hyperbrowser or Scrapeless session with Puppeteer or Playwright when it needs a stealth browser. Its code, files and other tools stay on the boat machine.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons