Legba

How is this different from Browserbase or Steel?

Each session is contained and disposable by default. The work runs off your stack and is destroyed on close, so a prompt injection or a leaked token has nowhere to go. We run a real browser on real residential IPs, not headless behind a rented proxy. They sell a browser. We sell isolation.

What is the cold start latency?

Under 200ms from a warm pool, under 2 seconds cold. These are measured per region. The status page is public. We do not quote averages we cannot ship.

How does the MCP integration work?

One config block in your MCP client. The server exposes session creation, navigation, and extraction as tools. Claude, GPT, or any MCP-aware agent gets a real browser without you writing a line of orchestration.

Where do sessions run?

You pick the geography per session. We hold residential capacity across major US, EU, and APAC metros. New regions land regularly. Enterprise gets dedicated regional pools.

Are you SOC 2 compliant?

SOC 2 Type II is in progress, tracked in Vanta. For early enterprise conversations we share our controls and questionnaire responses on request.

What happens to credentials I pass in?

They live inside the session container, scoped to the targets you declare, and are destroyed when the session ends. We do not log them. A persistent session stores an encrypted state blob under your key.

Does this work with LangChain, CrewAI, and the rest?

Yes. There are SDK adapters for the major frameworks plus a Playwright-compatible interface, so existing automation code redirects with minimal change.

What is Legba Adversary?

Adversary is the same engine pointed at your own attack surface. It maps your external assets, validates the real exposures, and returns a client-ready report in minutes. Exposed API keys, subdomain takeover, leaked secrets. Validated findings, not scanner noise.