Get API Key

Web automation that's still signed in on run 100

Your Playwright, Puppeteer or Python script signs in once. Gologin Cloud Browser keeps the login in a profile with the same device and the same residential IP, so every later run starts signed in and the site sees a returning user, not a new device to verify.

Free to start, no card. Residential IPs included.

4.7 / 5 on G2from 79 reviews

Your script signs in once, then every run starts signed in

Cookies, device fingerprint and residential IP come back together on every run, so the portal sees the same returning user on run 40 as on run 1, not a new device asking to verify.

Mondayrun 1Signed in

The script signs in once, a person types the verification code in the live session, and the profile is saved.

cookiesdeviceaddresssaved
Fridayrun 2Stays signed in

Same device, same address, same account. No login screen, so the script goes straight to the work.

session restored
Next monthrun 40Still the same user

Nothing has drifted. One account on one consistent device the whole time, so the portal has nothing new to check.

session restored

Want the mechanics? Read how to connect a profile, then create your first one.

Where to run web automation: your own server or a cloud browser

A script that logs in needs two things between runs: a login that lasts and a browser that keeps running. Here is who handles each.

Login, IP, session length, upkeep and price of web automation on Gologin Cloud Browser, your own server, Browserbase and Browserless
What you getGologinYour own serverBrowserbaseBrowserless
Still signed in on the next runYesYou build itYesUp to 7 days
Same residential IP on the next runYesNoNot publishedNot published
Longest session, first paid planNo limitNo limit6 hours15 minutes
Chrome to install and keep updatedNoneYoursNoneNone
A person can step in from a linkYesNoYesYes
Residential traffic$1/GBSeparate provider$12/GB$12/GB
First paid plan$4.50 a monthServer cost$20 a month$25 a month, yearly

Collecting data rather than acting on it? See Dynamic scraping.

Web automation examples: logged-in work with no API

Marketplaces, ad platforms and portals check every sign-in. Gologin brings back the same device, IP and login on every run.

How to automate a website login with Playwright, Puppeteer or Python

Connect your script in one line. The first run signs in; every run after checks that the profile is still signed in and goes straight to work. The code below ran twice on a public practice site: signed in on the first run, already signed in on the second.

  1. Step 01

    Get your token

    Sign up with Google and copy your key from the dashboard. Free, no card.

  2. Step 02

    Create a profile

    One click in the dashboard, or one API call. The profile keeps the device, the IP and the login.

  3. Step 03

    Run it twice

    Run the script with your token and profile id. The first run signs in and prints "Signed in"; the second opens signed in and prints "Already signed in". More in the getting started guide.

Install
npm install playwright-core
Run
GOLOGIN_TOKEN=your_token GOLOGIN_PROFILE_ID=your_profile_id node login.mjs
Connects to
wss://cloudbrowser.gologin.com/connect?token=…&profile=…
import { chromium } from "playwright-core";

const token = process.env.GOLOGIN_TOKEN;
const profileId = process.env.GOLOGIN_PROFILE_ID;
const endpoint = `wss://cloudbrowser.gologin.com/connect?token=${token}&profile=${profileId}`;

const browser = await chromium.connectOverCDP(endpoint);
const page = await browser.contexts()[0].newPage();

await page.goto("http://quotes.toscrape.com/");
const signedIn = await page.locator("a[href='/logout']").isVisible();

if (!signedIn) {
  await page.goto("http://quotes.toscrape.com/login");
  await page.fill("#username", "demo");
  await page.fill("#password", "demo");
  await page.click("input[type=submit]");
  await page.waitForSelector("a[href='/logout']");
}

const first = await page.locator(".quote .text").first().textContent();
console.log(signedIn ? "Already signed in" : "Signed in", "|", first);

await page.close();
await browser.close();

Plans & Pricing

Every plan runs the same browser, with residential IPs included. Plans differ in browser hours and parallel sessions.

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.

Custom

From 4 parallel sessions, with a dedicated account manager, a premium SLA and tailored onboarding.

Get a personal demo

Part of the complete tech stack

One account, one proxy network, one ecosystem. Pick the product the job needs.

Web automation questions

What is web automation?

Web automation, also called browser automation, is software doing the clicks and typing a person would do on a website: signing in, filling forms, reading pages, moving data between tools. Developers write it with libraries such as Playwright, Puppeteer or Selenium, and it runs in a browser on a schedule.

What is the best web automation tool?

To automate browser tasks in code, Playwright is the common choice today, with Puppeteer for Chrome-only work. The library decides how you write the steps; the browser it drives decides whether the login survives. Gologin Cloud Browser runs Playwright and Puppeteer scripts with one line changed.

How do I keep a script logged in between runs?

Keep the login in a profile, not in a file. Playwright's storage state saves cookies, but a site that sees them arrive from a new IP or device often asks you to verify again. A Gologin profile brings the cookies back with the same device and residential IP, so the next run opens signed in.

What happens when a site asks for a 2FA code?

The run waits on the code page. Open the session's Live View link, type the code, and the script carries on in the same signed-in profile. See Cloud Browser UI.

Can I run web automation on a schedule?

Yes, from the scheduler you already use: cron, GitHub Actions or a job queue starts the script, and the script connects to the same profile every time. There is no limit on how long a session runs; a session left idle for 20 minutes closes on its own, so nothing is left running.

Is this headless browser automation?

Yes. The browser runs in Gologin's cloud with no window on your machine, which is what headless means for your script. To watch a run, open its Live View link.

Do I need to run Chrome on my own server?

No. The browser runs in Gologin's cloud and your script only connects to it: no Chrome to install, update or restart, and no memory to size on your server.

Can I do web automation in Python?

Yes. Python Playwright connects with connect_over_cdp, and the Python tab above has the full script. Install it with pip install playwright; no local browser download is needed.

Give your script a browser that stays signed in.

Connect your Playwright, Puppeteer or Python script in one line, and give each account one profile: the same device, the same IP and the same login on every run.

Free to start, no card. Residential IPs included.

4.7 / 5 on G2from 79 reviews