Lupin vs Steel: managed browser controls and the agent workspace boundary

Steel gives existing browser code a clear entry point

Steel’s official quickstart creates a cloud browser session, connects Playwright over CDP and releases the session when work finishes. It also documents session options for its proxy network, CAPTCHA handling, user agent and timeouts. These are relevant when your application already drives browsers programmatically. Lupin offers browser sessions and supported page actions through a shared agent workspace, with temporary CDP access when a compatible client needs direct control. The overlap is browser execution; the surrounding resource and configuration models differ.

Network requirements create a concrete distinction

If an approved task requires the browser session to use configurable proxy routing, inspect that requirement before choosing a platform. Steel’s quickstart explicitly shows proxy configuration. Lupin’s current Cloudflare Browser Run integration does not support custom Lupin proxy routing, even though Lupin separately offers a proxy API. Buying proxy capacity does not connect those products automatically. Steel may be the better choice for this specific browser requirement; Lupin’s additional email or app resources cannot compensate for a missing network path.

A browser connection URL is a credential

Steel’s example connection uses API authentication with a session identifier. Lupin returns explicit browser access links only through its connect operation. Either design requires careful secret handling: keep links out of analytics, shared logs, screenshots and model-visible error dumps. A session viewer can reveal customer content even if it cannot purchase anything. Define which operator may take control, how the handoff is recorded and what happens after the browser is closed. Temporary access is helpful only when your application handles its expiry without accidentally creating additional sessions.

Lifecycle handling belongs in the finally path

Your automation should release or end the browser after success, validation failure and a client exception. Steel’s quickstart demonstrates release in cleanup. Lupin exposes an explicit end operation and a durable session registry, with a requested inactivity timeout rather than a universal task-duration guarantee. Preserve the session identity and confirm its closed state if cleanup fails. Retrying a browser task can repeat an external form submission; use the business system’s observed state and approval record to decide whether continuing is safe.

Estimate the options your task actually enables

Compare active session time, concurrency, network traffic, specialized browser options and operator recovery. Check current Steel terms for the selected features rather than assuming all session configurations have identical cost. Lupin browser runtime belongs to workspace allowances, while proxy traffic is separately accounted and is not a browser routing feature. Steel is attractive when specialized browser controls remove custom integration work. Lupin is attractive when a bounded browser step sits inside a larger email-and-app workflow and the exposed browser feature set is sufficient.

Choose using a browser compatibility checklist

Start with a controlled public test page and list the required browser operations, network behavior, timeout and cleanup outcome. Check your existing Playwright code against Steel’s connection model and Lupin’s temporary CDP access without assuming identical launch controls. Then evaluate a read-only authorized target and a deliberately interrupted run. Prefer Steel when its documented session options are essential. Prefer Lupin when its supported actions and lifecycle meet the requirement and shared workspace ownership adds value. Do not use CAPTCHA or proxy feature availability as evidence that every target site will work.

When switching from Steel, list every session option your code sets, including proxy, CAPTCHA and user-agent controls. Port browser-client code only after verifying those options in the destination surface, and plan new session identities and authentication. A changed CDP URL does not migrate launch semantics.

Sources & verification

Official documentation and Lupin public documentation/source were reviewed on 2026-11-05. This is an architecture and operating-scope comparison, not a live benchmark, hands-on provider test or independent review of service quality.

• Steel Sessions API quickstart ↗Checked 2026-11-05
• Lupin browsers documentation ↗Checked 2026-11-05
• Lupin bounded agent registration ↗Checked 2026-11-05

Prepared with AI assistance by Lupin editorial. How we research and maintain these guides.