Gologin Cloud Browser

以下为收录时的原文，语言与页面不同，未做翻译。

GoLogin Cloud Browser is a cloud-based platform that provides scalable, headful browser instances with unique fingerprints and IPs for web scraping and automation. It offers programmatic control via Puppeteer/Selenium, integrated proxy services, and team management tools to reduce detection and simplify infrastructure.

官网介绍

Real Chromium in the cloud for AI agents and automation. One line connects Playwright or Puppeteer, and profiles stay logged in for weeks. Free API key.

官网要点

• Web Automation
• Scraping Browser API
• Secure Cloud Browser for Web Automation & API

官方常见问题

Is there a free cloud browser?

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.

Is a cloud browser secure and private?

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.

Can I run the cloud browser headless?

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.

How long does a persistent browser session stay logged in?

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, the site doesn't see a new device and doesn't force a re-check. What ends a session is the site expiring the cookie, not us.

Does it work with my existing Playwright or Puppeteer code?

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.

Do you handle CAPTCHAs and bot detection?

Mostly by not triggering them - real device fingerprints, residential or mobile IPs, and a profile with history mean sites see a returning user rather than a stranger. When a challenge does appear, the run retries on a fresh IP, and you can open the session headful and clear it yourself. If you only need the page and not the session, Web Unlocker solves CAPTCHAs outright and bills only on success.