Create
One request. A few seconds later a real Chromium is running in the cloud with your name on it. Pick a timeout up to 6 hours, an exit country, or bring your own proxy.
The whole product
fits on this page.
BrowserGen is real Chromium in the cloud, rented by the browser, not the minute. You start one with a POST, drive it with the tools you already use, and watch it live when you are curious. That is the product. The rest of this page is detail.
A browser's life in four verbs.Create, connect, observe, end.
There is no SDK to adopt and no framework to migrate to. Two REST endpoints handle the lifecycle; everything between create and stop is standard Chrome DevTools Protocol, which your automation already speaks fluently.
Connect
The response carries a plain CDP websocket. Playwright and Puppeteer treat it like a local browser; nothing in your code needs to know it is not.
Observe
Every session streams its screen to the dashboard. Watch your script work the page, or take the mouse when a step needs a human.
End
Stop it, let it time out, or just walk away: two minutes after the last client leaves, the browser cleans up after itself. No zombies, ever.
Every browser leaves a story.And you can read it while it happens.
This is a session record: a script drove the page, a human named Mia took the mouse for 52 seconds to clear a checkout step, and the script picked up where she left off. Nothing here is reconstructed after the fact; you watch it live.
Nothing is implicit
Attach, live view, human control, navigation: the timeline shows what happened while your script ran, as it happens. Your 3 a.m. run is not a mystery, it is a log you can open.
A defined end, always
Stop call, timeout, or disconnect grace: every session record names the reason it ended. There are no orphaned browsers to hunt down, because there is no way to orphan one.
30 days of history
Ended sessions stay queryable for a month, over the API and in the dashboard. Last night's run is one GET away, not an archaeology project.
The numbers, since you were going to ask.All of them enforced server-side.
100exit countries, down to the city
6 hlongest session, 60 s the shortest
$19per month for unlimited use of one browser
1-50concurrent browsers on the slider
30 dof session history, queryable
120 sdisconnect grace before self-cleanup
Everything is included. Yes, everything.Plans differ by one number: concurrency.
Live view and control
liveViewUrlHeadless infrastructure with a head when you want one. Every session streams its screen to the dashboard with input control, so debugging means watching the page instead of rereading a stack trace, and a stuck automation can be rescued by a person without restarting anything.
The stream is the session's real screen, page content only: exactly what your script acts on, to the pixel.
Geo targeting and proxies
country: "de"One request parameter launches the browser from any of 100 countries, down to specific cities in larger ones (us-dal is Dallas). Prefer your own network path? Pass a proxy URL per session instead and BrowserGen stays out of the way.
A dashboard your team shares
unlimited membersAPI keys, running sessions, history, and usage live in one workspace with unlimited members; seats are not a thing we sell. Anyone on the team can open a colleague's live view, stop a runaway session, or check what ran last night.
Predictable lifecycle
ended_reasonTimeouts, disconnect grace, and explicit stops mean every session has a defined end, and its record tells you which one happened. Browser state is destroyed with the session, never persisted: the next one starts factory-fresh.
You have now read the entire product.
Two endpoints, a websocket, and a dashboard: that was it. The free trial is the same thing with a browser attached.
Start free trial7 days free. Cancel anytime.