Every Gologin Cloud Browser session has a Live View link. Open it on any device to see the page your Playwright or Puppeteer script is on, step in for a 2FA code or a tricky form, then close the tab. The session stays signed in for the next run.
Free to start, no card. Residential IPs included.
4.7 / 5 on G2Every cloud browser here lets you watch a running session. The difference is what the session keeps after a person steps in, and what each hour and gigabyte costs.
| What you get |  Gologin | Browserbase | Steel | Anchor |
|---|---|---|---|---|
| Watch a running session from a link | Yes | Yes | Yes | Yes |
| Still signed in on the next session | Yes | Yes | Yes | Yes |
| Same IP on the next session | Yes | Not published | Paid add-on | Yes |
| Residential traffic | $1/GB | $10-12/GB | $6-10/GB | $8/GB |
| Extra browser hour, first paid plan | $0.09 | $0.12 | $0.10 | $0.05 |
Building an AI agent? See Browser for AI agents.
Run a profile in the cloud from the Gologin app, then open it on another computer or a phone. The video shows how, and how much of your own machine it saves.
One API call starts a profile in the cloud and returns the link to its live session. Send the link to whoever has to finish the step.
Sign up with Google and copy your key from the dashboard. Free, no card.
One click in the dashboard, or one API call. The profile keeps the device, the IP and the login.
Run the script with your token and profile id. It starts the profile in the cloud and prints the Live View link. Keep the link private while the session runs. More in the Live View docs.
ClaudeGOLOGIN_TOKEN=your_token GOLOGIN_PROFILE_ID=your_profile_id node live-view.mjsPOST https://api.gologin.com/browser/{profileId}/webconst token = process.env.GOLOGIN_TOKEN;
const profileId = process.env.GOLOGIN_PROFILE_ID;
const res = await fetch(`https://api.gologin.com/browser/${profileId}/web`, {
method: "POST",
headers: { Authorization: `Bearer ${token}` },
});
if (!res.ok) throw new Error(`Gologin API answered ${res.status}`);
const session = await res.json();
console.log("Live View:", session.remoteOrbitaUrl);GOLOGIN_TOKEN=your_token GOLOGIN_PROFILE_ID=your_profile_id python live_view.pyPOST https://api.gologin.com/browser/{profileId}/webimport json
import os
import urllib.request
token = os.environ["GOLOGIN_TOKEN"]
profile_id = os.environ["GOLOGIN_PROFILE_ID"]
request = urllib.request.Request(
f"https://api.gologin.com/browser/{profile_id}/web",
method="POST",
headers={"Authorization": f"Bearer {token}"},
)
with urllib.request.urlopen(request) as response:
session = json.load(response)
print("Live View:", session["remoteOrbitaUrl"])Every plan runs the same browser, with residential IPs included. Plans differ in browser hours and parallel sessions.
$0
No card needed
$4.50/ month
For individual developers
$8/ month
For growing teams
$14/ month
For critical operations
Need more at once? Add parallel sessions to any plan for $2 a month each, as many as you need. Proxy traffic beyond your allowance is $1/GB.
From 4 parallel sessions, with a dedicated account manager, a premium SLA and tailored onboarding.
One account, one proxy network, one ecosystem. Pick the product the job needs.
Start the session and open its Live View link in any browser tab, on a laptop or a phone. You see the page the session is on as it changes. The link works only while the session runs.
Yes. Open the Live View link, finish the step that needs a person, such as a 2FA code, and close the tab. The session keeps its cookies and its address, so your script carries on signed in.
A headless browser runs with no window; a headful one shows its window. Playwright's headed mode opens that window on your own machine. With Gologin Cloud Browser the window stays in the cloud, and the Live View link lets you watch it from any device. Moving tests to the cloud? See Playwright and Puppeteer.
Yes. The login lives in the profile, so the next session on the same profile opens signed in. You do not log in again or copy cookies between runs. Collecting data behind a login? See Dynamic scraping.
Share it only with people who should be inside the session. Anyone with the link can open the session while it runs, so treat it like a password and send it over a private channel.
A remote browser runs on another machine and shows you its screen. A cloud browser is a remote browser your code drives through an API. Gologin Cloud Browser does both: your script connects to it, and the Live View link shows the same session to a person.
Open any Gologin Cloud Browser session from a link, finish the step by hand, and let your script carry on signed in.
Free to start, no card. Residential IPs included.
4.7 / 5 on G2