What you can do with Cloud Browser
- Run multiple browser sessions in parallel in the cloud
- Automate with your existing stack (Puppeteer / Playwright)
- Use Gologin profiles to keep persistent state (logins, cookies, storage)
- Route traffic through proxies by configuring them on the profile
Common technical scenarios
Cloud Browser is typically used for workflows where you:- log into a web account once and then keep the session persistent via a profile
- run repeated actions on the same websites across many profiles
- need stable, long-running sessions without depending on a local machine
Core concepts
- Profile — a reusable browser identity (cookies/storage + profile settings such as fingerprint and proxy).
- Cloud session — a running instance of a profile in GoLogin’s cloud.
- Connect URL — the endpoint you pass to your automation tool to control the cloud session.
How it works (high level)
- (Recommended) Create and configure a profile via the Gologin REST API (proxy, fingerprint, etc.).
- Connect to Cloud Browser using your dev token and optional
profileId. - Automate the session with Puppeteer or Playwright.
- Close the connection when you’re done.
Connection URL
Use this URL as the remote browser endpoint: https://cloudbrowser.gologin.com/connect?token=${token}&profile=${params.profileId}token— your Gologin dev token (generate it in the dashboard:Personal Area → API Token).profile— profile ID (optional). If omitted, a new profile will be created for the session.
Managing profiles (proxy, fingerprint, etc.)
Cloud Browser is the connection layer.To create/update profiles, attach proxies, and configure profile settings, use the Gologin REST API:
- Profiles API: https://gologin.com/docs/api-reference/profile
- Proxy API: https://gologin.com/docs/api-reference/proxy
Next steps
- Getting Started: https://gologin.com/docs/api-reference/cloud-browser/getting-started
- API Quickstart: https://gologin.com/docs/api-reference/introduction/quickstart