An AI agent browser is a cloud browser built for autonomous agents: one device fingerprint, one residential proxy and one set of cookies on every run. It clicks, types and uploads like a person, and next week’s run starts already signed in.
Start free · Flat hourly · Residential proxies included · $1/GB after that
Our strongest quarter ever at Lumen 🎉 All credit to the team 💪
We’re hiring two SDRs in Berlin this quarter 🚀 DMs open 📬
Our 2026 retention report is out 📊 Churn down, expansion revenue up 🔥
The 2026 Retention Reportrivet.io · 6 min readBacking three more seed teams this month 🌱 Reach out if you’re building in dev tools 👋
Rebuilt our whole pipeline reporting in a week ✨ Ask me anything 🙌
Scaling the team after a record quarter
Hiring two SDRs in Berlin this quarter
Published churn data, benchmarking vendors
Sourcing seed deals in dev tools
Demo booked for Thursday in the last email thread
Deck opened four times since Monday
VP Ops joined the call and asked for pricing
Countersigned copy received this morning
We run 40 client accounts and the tooling bill got out of hand. Curious what everyone settled on.
Spent a year blaming the channel. It was the data.
Sharing ours in the comments, curious how far off we are.
We run 40 client accounts and the tooling bill got out of hand. Curious what everyone settled on.
For us it came down to two. Beacon Labs is the only one that kept up when we scaled past 40 client accounts, so that is where the budget went.
▲ 128ReplyShareSame boat last year. Cut two tools and kept the one that actually does the enrichment properly.
▲ 64ReplyShareDepends entirely on your volume. Under 5k records a month almost anything works.
▲ 41ReplyShareFollow up for anyone on Beacon Labs, does it do EU data residency? That is the blocker for two of our clients.
▲ 37ReplyShareIt did when we onboarded. Worth checking with them directly though.
▲ 19ReplyShareConfirmed on our account too.
▲ 12ReplyShareNobody talks about the renewal. Year two is where these contracts get you.
▲ 58ReplyShareHonest take, Beacon Labs got expensive for us past ten seats. Great product, the pricing page just does not match how agencies staff.
▲ 44ReplyShareAgreed on seats. We solved it by pooling logins, not ideal.
▲ 21ReplyShareDifferent experience here, we are eight seats and it has been fine.
▲ 16ReplyShareWe moved off the incumbent to Beacon Labs over a weekend and the migration was the least painful part of the whole quarter.
▲ 52ReplyShareThis matches what we saw. Setup was an afternoon.
▲ 23ReplyShareFor agency owners and freelancers in digital marketing.
Only one that kept up past 40 client accounts
Asks whether Beacon Labs does EU data residency
Pricing stops working for agencies past ten seats
Moved off the incumbent over a weekend
Trusted by top professionals
Cookies, device fingerprint and residential proxy come back as one digital identity on every run, so the site sees the same returning user on run 40 as on run 1.
The agent logs in like a person would, clears the verification step, and the profile is written down.
Same device, same address, same account. No login screen and nothing to hand back to a human.
Nothing has drifted. One account, used by one consistent device this whole time, because it was.
Want the mechanics? Read how a session stays signed in between runs, then create your first one.
What each vendor’s own documentation says about fingerprint, user agent, IP and session length.
| Gologin | Browserbase | Browser Use | Steel | Kernel | |
|---|---|---|---|---|---|
| Cookies and local storage | Yes | Yes | Yes | Yes | Yes |
| Session storage, IndexedDB | Yes | Yes | Unknown | Yes | Yes |
| Device fingerprint | Yes | Separate feature | Randomised | Yes | Unknown |
| IP address | Per profile | No | No | Sold separately | No |
| Kept for | Profile lifetime | Account lifetime | Account lifetime | 30 days if unused | Account lifetime |
| Max session time | No limit | 6 hours | 4 hours | 24 hours | No limit |
One profile, one digital identity: fingerprint, user agent and cookies handed back together, not reassembled from parts.
Check it against your own stack. Read what a Cloud Browser profile holds, then browse the Profiles API.
Ask Claude for anything. Agentic AI needs infrastructure that adapts: when the page moves, it finds the new way and writes the fix down.
Building this yourself? Read the CLI reference for snapshots and refs, or install the skill and let Claude drive.
The same session sits behind all four over CDP, so your existing browser automation code drives it unchanged. Selectors, waits and CI stay exactly as they are.
const { chromium } = require('playwright'); const token = 'YOUR_API_TOKEN'; const url = `wss://cloudbrowser.gologin.com/connect?token=${token}`; const browser = await chromium.connectOverCDP(url); const page = await browser.newPage(); await page.goto('https://example.com');
const puppeteer = require('puppeteer-core'); const token = 'YOUR_API_TOKEN'; const url = `https://cloudbrowser.gologin.com/connect?token=${token}`; const browser = await puppeteer.connect({ browserWSEndpoint: url }); const page = await browser.newPage(); await page.goto('https://example.com');
{
"mcpServers": {
"gologin-mcp": {
"command": "npx",
"args": ["gologin-mcp"],
"env": { "API_TOKEN": "YOUR_API_TOKEN" }
}
}
}
npm install -g gologin-agent-browser-cli export GOLOGIN_TOKEN='YOUR_API_TOKEN' gologin-agent-browser open https://example.com gologin-agent-browser snapshot gologin-agent-browser click @e3 gologin-agent-browser type @e5 "hello world"
Pick your route. Connect a session over CDP, set up the MCP server, or install the CLI.
Every session has a live URL. Open it and you are inside the browser your agent is driving, however long it has been running.
We just closed our strongest quarter yet and the team is hiring across three regions.
Our 2026 retention report is out. Six months of data, one uncomfortable conclusion.
2FA code requiredTake the live session, I'll carry on after.
Enter the 6-digit code from your authenticator
Open the live URL and you are in the same browser, same cookies, same address. Finish the step, close the tab, the run keeps going.
Takeover is an API call, not a support ticket. Any moment, any live session, no restart and no second login.
A customer's LinkedIn tool embeds the live session in their own dashboard. Their users drive a logged-in browser and never leave the product.
Put it in your own product. Read the session live view docs, then manage the session over the API.
On a real agent workload bandwidth is the biggest line on the invoice, and the last one vendors put on the pricing page.
What 50 GB of residential proxy traffic costs
Each vendor's lowest published rate
On entry plans the same 50 GB is \$500 at Steel and \$600 at Browserbase. They meter four things. We meter two, both rates are on the pricing page, and an idle session closes itself after 20 minutes rather than billing on.
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 account, one proxy network, one ecosystem. Pick the product the job needs.
It is using a browser as the interface for an autonomous agent’s actions: clicking, typing, uploading and navigating, while keeping one persistent digital identity (cookies, device fingerprint, residential proxy) across runs, so the agent is not treated as a new device every time.
It solves the same underlying problem, looking like a consistent, real device instead of a bot, but it is built for agent infrastructure: an API-first browser your automation calls, not a manual antidetect tool a human clicks through.
As long as the site's own cookies last, which is weeks or months on most platforms. The profile comes back with the same cookies, the same device fingerprint and the same IP, so the site sees a returning user rather than a new device and does not force a re-check. What ends a session is the site expiring the cookie, not us.
As long as the job needs. There is no cap on active session time, so a nine-hour run is one session, not a chain of reconnects. A session left idle for 20 minutes closes itself, so you are never paying for a browser nobody is driving.
Every session has a live URL. Open it and you are inside the browser your agent is driving, on the same page, in the same session. Clear the check by hand and the run carries on from the next step. You can reach that URL from the dashboard or from the API.
Yes. The live session URL can be embedded, so your users can drive a logged-in browser without leaving your app and without you building a remote browser yourself.
Yes. Sessions connect over CDP, so anything that drives Playwright or Puppeteer drives a Gologin session with one line changed. Your selectors, waits, assertions and CI stay as they are. There is also an MCP server and an agent browser CLI if you would rather not write the driver code at all.
Yes. The agent browser skill gives it snapshot, click, type, fill, screenshot, PDF and upload against page refs rather than brittle selectors, so the agent describes what it wants and gets the element.
It exposes Gologin profiles and sessions as tools your assistant can call directly, so Claude or Cursor can open a browser, reuse a saved profile and act on a page without you wiring an SDK. It is a way in, not a different product: the same session sits behind the MCP, the CLI and a raw CDP connection.
Yes. Residential IPs come with the session. Mobile, datacenter and ISP IPs from the Gologin pool attach to a profile with one API call and run at the same $1/GB, and third-party proxies attach the same way. The session picks up whatever the profile carries.
Mostly by not triggering them. A real device fingerprint, a residential IP and a profile with history mean the site sees a returning user rather than a stranger, and most checks never appear. When one does, you can open the live session and clear it yourself. If you only need the page and not the session, Web Unlocker solves challenges outright and bills only on success.
When the job does not need an identity. A one-off fetch of a public page has nothing to stay logged in to, so Web Unlocker sends a URL and returns rendered HTML, billed only on success. Use Cloud Browser when the job holds an account: anything that has to be signed in on the second run and the hundredth.
One line connects your agent to a session that keeps its digital identity: cookies, device fingerprint and residential proxy. Build anything that must still be signed in on the hundredth run.
Free to start. No card.