Skip to main content
Steel and Kernel both hand you a hosted Chromium over CDP, so the connection swap is one line. The differences worth planning for are what happens around the session.

Concept mapping

The connection change

What to change next

  • Stop connecting over CDP for the hot path. Playwright execution runs your code inside the browser’s VM and returns values, with no connection to manage and no CDP fingerprint on the wire. See how you drive the browser.
  • Replace credential handling with managed auth. Kernel performs the login, keeps the session warm with health checks, and writes the result into a profile your browsers attach.
  • Use a pool for repeated work. Pool acquisition skips both browser creation and the per-plan create rate.
If you were self-hosting Steel to control cost or data residency, read zero data retention and security practices before you plan the move.