Point Puppeteer at managed cloud Chromium
Puppeteer API
Run Puppeteer against BrowserSolver cloud browsers instead of local Chrome. Keep familiar scripts for ecommerce and hardened flows while we own the fleet, routing, and stealth baseline.
- Remote Chromium for existing Puppeteer suites
- Stealth-aware sessions for protected storefronts
- Fallback to REST scrape modes when scripts are overkill
- Same account as unlock and screenshot products
Puppeteer
client
Cloud
Chrome
Stealth
baseline
eCom
ready
Keep Puppeteer, drop the ops
- Step 1
Connect
Point your Puppeteer client at BrowserSolver cloud Chrome.
- Step 2
Automate
Reuse selectors and flows you already trust.
- Step 3
Simplify later
Move extract-only jobs to Website Rendering REST when ready.
Puppeteer without the grid
Keep selector logic in your repo. Move browser hosting to BrowserSolver so deploys stop shipping Chrome layers. Built for production jobs that need predictable access before brittle parsing.
- Useful when teams already invested in Puppeteer suites
- Pair with AntiBot before pointing at new retailers
- Prefer Website Rendering REST for greenfield scrapers
- Same API key and credit balance across BrowserSolver scrape modes
Scripts that survive production
Remote sessions reduce flake from CI machines and laptop Chrome versions. Built for production jobs that need predictable access before brittle parsing.
- Remote Chromium so CI never installs local Chrome
- Same account as unlock and screenshot products
- Documented limits and timeouts in the API library
- Same API key and credit balance across BrowserSolver scrape modes
Keep Puppeteer, drop the ops
Cloud Chromium for scripts you already trust.
Remote Chrome
No local binary.
Connect
Familiar Puppeteer client.
Stealth
Baseline anti-detection.
Ecommerce
Storefront scrape patterns.
Sessions
Cookies across steps.
No fleet
We scale the browsers.
Compatible
Keep existing Puppeteer code
No fleet
We scale browsers for you
Stealth
Baseline anti-detection on sessions
Migrate path
REST Rendering when scripts shrink
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Is every Puppeteer API supported?
Support tracks the cloud browser capabilities we expose. For many extract-only jobs, Website Rendering is simpler and cheaper.
Can I reuse existing Puppeteer scripts?
Yes for flows that fit the cloud browser capabilities we expose. Point the client at BrowserSolver and keep your selectors and wait logic.
Can I combine Puppeteer with WebUnlocker?
Use AntiBot and WebUnlocker for allowlisted domains when driver flows still hit vendor challenges.
Do CI machines need Chrome?
No. CI keeps your script; browsers run in BrowserSolver cloud.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes