Most automations break the moment they have to log in. Gologin Cloud Browser is real Chrome in the cloud that brings cookies, device fingerprint and residential IP back together between runs - a persistent browser session you reach from a Playwright or Puppeteer script, the browser UI, or an AI agent.
Start free · Flat hourly · Residential IPs included · $1/GB after that
70 reviews
111 reviews
Why sessions die
The data worth having is behind a login. Getting there once is easy - still being there next month is the hard part.
Websites don't only check for automation; they also look at consistency. They score coherence and history - whether the hardware story holds together, and whether this identity has been seen before. A browser that didn't exist three seconds ago has neither, so every run starts as a stranger. A disposable container is exactly what every cloud browser ships.
Cookies don't keep you logged in.
Identity does.
Sites bind a session to the cookie, the device fingerprint and the network it came from. Restore the storage alone and you look like a stolen cookie. A Gologin profile brings back all three.
Cookies, localStorage, IndexedDB and device-trust tokens - everything the site wrote.
The canvas, WebGL, audio and hardware profile that was there at login.
The residential or mobile IP the account signed in from.
A returning user. Not a stranger.
Want this on a real job? See Dynamic scraping, or Web automation.
Compare
Restoring cookies is the easy part - everyone does it. These are the pieces that decide whether the session is still yours a month later.
| Component | Gologin | Browserbase | Browser Use | Steel |
|---|---|---|---|---|
| What returns with a saved profile | Cookies, storage, fingerprint and IP | Cookies and storage | Cookies and login state | Cookies, storage and fingerprint |
| Stays logged in without re-auth | Weeks to months | Until cookies expire | Not published | Within one session (24 h) |
| Mobile (4G/5G) IPs | Built-in | Residential only | Residential only | Your own proxy only |
| Fingerprints on a default session | Real, from real devices | Randomly generated | Real - OS profiles | Plugin-managed |
| Live view with human takeover | Yes | Yes | Not published | Debug UI |
Start free · Flat hourly · Residential IPs included · $1/GB after that
Getting started
Sign up with Google and copy your key from the dashboard. Free, no card.
Swap your local launch call for a connection to our endpoint. Same selectors, same assertions, same CI.
Save the profile. Every run after that starts already authenticated, on the same device and the same IP.
wss://cloudbrowser.gologin.com/connect?token=${token}&profile=${profileId}
https://cloudbrowser.gologin.com/connect?token=${token}&profile=${profileId}
Same endpoint either way - Playwright connects over wss://, Puppeteer over https://. The profile is optional: leave it out and you get a temporary one.
// npm i playwright const { chromium } = require('playwright'); (async () => { const token = 'YOUR_API_TOKEN'; // Dashboard - Personal Area - API Token const profileId = ''; // optional - empty gives a temporary profile const url = `wss://cloudbrowser.gologin.com/connect?token=${token}` + (profileId ? `&profile=${profileId}` : ''); const browser = await chromium.connectOverCDP(url); const page = await browser.newPage(); await page.goto('https://example.com'); console.log(await page.title()); await browser.close(); // ends the cloud session - billing stops here })();
// npm i puppeteer-core const puppeteer = require('puppeteer-core'); (async () => { const token = 'YOUR_API_TOKEN'; // Dashboard - Personal Area - API Token const profileId = ''; // optional - empty gives a temporary profile const url = `https://cloudbrowser.gologin.com/connect?token=${token}` + (profileId ? `&profile=${profileId}` : ''); const browser = await puppeteer.connect({ browserWSEndpoint: url, defaultViewport: null, }); const page = await browser.newPage(); await page.goto('https://example.com'); console.log(await page.title()); await browser.close(); // ends the cloud session - billing stops here })();
Already have a script? See the Playwright and Puppeteer guides, or drive the same sessions yourself in the Cloud Browser UI.
Pricing
Across this category the meter sits on the things that go up when a run goes wrong: requests, bandwidth, session starts. A 403, a CAPTCHA, a login that asks for 2FA again, a page that quietly returns nothing - all of them end in a retry, and retries burn exactly those units.
"Credits are charged whenever Firecrawl's infrastructure processes a request, even if the target site returns an HTTP error status code such as 403 Forbidden or 404 Not Found."
Firecrawl billing documentation
Browserbase meters bandwidth at $10–12/GB on top of browser hours, with a one-minute minimum on every session - so every retry costs a fresh minute plus fresh bandwidth, across five metered lines.
A hard site costs the same
as an easy one.
We bill browser hours. Residential IPs are included in the rate, and traffic beyond your allowance is $1/GB. The next cheapest published rate in the category is $4. One line on the invoice.
What 50 GB of residential traffic costs
Each vendor's lowest published rate
On entry plans: Steel $500, Browserbase $600.
Compare
A low hourly rate means little if bandwidth, requests and retries are billed on top. Here's every line each vendor puts on your invoice.
| Billing line | Gologin | Browserbase | Browser Use | Steel |
|---|---|---|---|---|
| Proxy traffic beyond allowance | $1 / GB | $10–12 / GB | $5 / GB | $6–10 / GB |
| Per request or per credit | None | $1–7 per 1,000 | None | None |
| Metered lines on your invoice | 1 | 5 | 2 | 2 |
| Browser time | $0.04–0.09 / hr | $0.10–0.12 / hr | $0.02 / hr | $0.08–0.10 / hr |
| Do failed requests cost you extra? | No | Yes - bandwidth + a minute | Yes - bandwidth | Yes - bandwidth |
Start free · Flat hourly · Residential IPs included · $1/GB after that
Build with Claude
Our MCP server and Claude Code skills give Claude direct control of profiles, proxies and fingerprints. You describe the job; it sets up the accounts and writes the automation against the Cloud Browser API.
Want to see what else Gologin can do? Read the AI agent docs, or see Cloud Browser for AI agents.
Definition
A cloud browser is a full web browser that runs on a remote server instead of your computer. You control it online through a UI or programmatically through an API, while the pages themselves load on the server's hardware and network. Gologin Cloud Browser is a secure cloud browser with isolated profiles: each session is a real Chromium instance with a real device fingerprint, its own cookies and storage, and a residential or mobile IP - and all three persist between runs.
That makes it different from a headless container or a virtual browser sandbox. Those give you a clean browser every time; a Gologin profile gives you the same browser every time, so sites treat it as a returning user. It is browser as a service in the literal sense: Chrome in the cloud, reachable as a browser session API, with a persistent browser session behind every profile.
One page per job: what it needs from a browser, and how to run it on Gologin Cloud Browser.
Connect over CDP with one line. Same selectors, same tests, same CI – the browser just runs in the cloud.
Dynamic pages and logins handled by a browser with history and a residential IP, not a fresh container.
Run headless by default, switch a profile to headful when you need to watch or take over a session.
Let Claude build self-learning scripts and do real work. Every profile has a secured fingerprint, cookies and IP.
Watch automation live, take control for 2FA or a tricky form, then hand the session back to your script.
Real Chrome your Puppeteer or Playwright script connects to, with a real device fingerprint and a residential IP, for reliable access to public web pages.
FAQ
Yes. Sign up with Google and you get an API key immediately - 15 minutes of browser time across 3 parallel sessions, no card. Everything on this page works on the free key, including saved profiles, the Cloud Browser UI and the API.
Pages load on our servers, not on your machine, so nothing from the target site touches your device or your home IP. Each profile is fully isolated with its own fingerprint, cookies and IP, and Gologin is SOC 2 Type II certified with SSO and SAML on team plans.
Yes. Sessions are headless by default and connect over CDP for Playwright and Puppeteer. Any profile can be switched to headful in the Cloud Browser UI so you can watch a run or take over by hand in the same session.
As long as the site's own cookies last - weeks or months on most platforms. Because the profile returns with the same fingerprint and the same IP, your session stays consistent between runs. What ends a session is the site expiring the cookie, not us.
Yes - as a Playwright cloud browser or a Puppeteer cloud browser you change the connection line and nothing else. Selectors, assertions, waits and CI config all stay as they are. Playwright connects over wss://, Puppeteer over https://, and both use the same endpoint.
Every session runs in a real browser profile with its own fingerprint, proxy and saved history, so public pages load as they do for a returning visitor. If a check appears, open the session in a visible window and complete it yourself. If you only need public pages, Web Unlocker delivers them and bills only on success.
It retries on a fresh IP with the profile intact, so you keep the session state you'd already built. If it keeps failing, switch that profile to headful, watch where it stops, and take over in the same session rather than restarting from the login page.
Each profile is fully isolated: its own cookies, its own fingerprint, its own IP. Nothing is shared between profiles, so one profile hitting a problem doesn't affect the others.
The free key gives you 3 parallel sessions. On paid plans it comes with the tier: Professional runs 1, Business 2, Enterprise 3. Custom plans start at 4 and scale from there - talk to us about the number you need.
Residential, mobile, datacenter and ISP IPs across 195+ countries, with geo-targeting and automatic rotation. Mobile IPs are built in rather than an add-on, which is useful for testing how sites behave on carrier networks.
Browser time past your included hours, at $0.04-0.09/hr depending on plan, and proxy traffic past your allowance at $1/GB. A browser hour is 60 minutes of active browser runtime. There are no per-request fees, no charge for retries, and no separate extraction billing.
If the pages you need are public and the job is stateless - send a URL, get the content, move on - Web Unlocker is cheaper and simpler, and it only bills when a request succeeds. Cloud Browser is for work that needs a session: logging in, staying logged in, and acting as the same identity across many runs.
Explore
One account, one proxy network, one ecosystem. Pick the product the job needs.
Free trial + Simple hourly pricing with included hours – no hidden costs. Proxy bandwidth overages at only $1/GB.
Try Cloud Browser API for free: click Get API Key below, sign up with Google & grab your offer in Gologin dashboard 
Free
$0
15 minutes included (3 parallel sessions)
Try the full platform for free (sign up with Google required)
Popular plan
Professional
$4.50/m
50 hours included (1 parallel session)
Great for individual developers and small projects
Business
$8.00/m
100 hours included (2 parallel sessions)
Designed for teams with growing workloads
Enterprise
$14.00/m
200 hours included (3 parallel sessions)
Advanced support and features for critical operations
Estimate your monthly cost based on usage
Extra parallel sessions: $2/session per monthOne line connects your script to Gologin Cloud Browser. Log in once, and build anything that has to stay signed in: scrapers, agents, internal tools, workflows that run for months.
Free to start. No card.