Skip to main content
Legba vs Anchor

An Anchor alternative built on disposal.

Anchor keeps agents authenticated: it stores login state so a browser stays signed in across runs. Legba goes the other way. Each session is a real headful Chromium on a fresh residential IP, destroyed the moment it closes.

If you do not want a credential to outlive a single job, the difference is the whole product.

Add Legba to ChromeTalk to us

Side by side.

Session disposal and credential isolation as the product, against stored auth state and reused sessions.

Compare
Legba
Anchor
Core wedge
Session disposal and credential isolation as the product
Authenticated browser automation for agents
Session model
Disposable, burned on close
Persistent authenticated sessions, reused
IP type
Fresh residential IP per session
Managed exits, not residential per session
Rendering
Real headful Chromium
Headless-first automation
Credential lifetime
Destroyed with the session, nothing outlives a job
Stored auth state, reused across runs
What you buy
Isolation: no trail after close
An auth layer for agent browsers
Best for
Credentialed, risky, or agent work that must leave no trace
Keeping agents logged in across long-running workflows
Pricing
Free to $5,000/mo, plus custom
Usage-based

Last verified 2026-06-12 · reviewed by the Legba engineering team

When Anchor is the better pick

Anchor is the better pick when staying logged in is the goal: long-running agent workflows that need to keep a session authenticated across many runs without re-auth. If credential continuity matters more than leaving no trail, its stored-auth model is a real advantage.

Questions people ask.

How is Legba different from Anchor?
Anchor keeps agents authenticated across sessions: it stores and replays login state so a browser stays signed in. Legba does the opposite. Each session is a real headful browser on a fresh residential IP, and it is destroyed on close. The credential dies with the session.
Does Legba persist login state between runs?
No, not by default. State lives inside the session container and is destroyed when the session ends. If you need continuity, you can request an encrypted state blob under your own key. Otherwise nothing persists, which is the point.
Why does a fresh residential IP per session matter?
Many sites treat datacenter and shared exits as bots and challenge them. Legba gives each session a fresh residential exit, so the traffic reads as a real person on a real network. The IP is tied to one disposable session, not reused across jobs.
What happens to a leaked token after a run?
It has nowhere to go. Cookies, tokens, and cookies-in-memory are destroyed when the session closes. A prompt injection or a leaked credential cannot outlive the single job it was scoped to.

Access anything.
Expose nothing.

Legba is a disposable real browser: it spawns a clean session, does the work, and destroys itself on close.

Get started
Read the docs

chromium / real fingerprint · residential ip · burn on close

Real browser. Real IP. Real page. Spawn a session. Do the work. Destroy it. Off your device. Off your stack. Gone on close.