Self-Hosted

​

What you stop operating

​

The connection change

import Kernel from '@onkernel/sdk';
import { chromium } from 'playwright';

const kernel = new Kernel();
const kernelBrowser = await kernel.browsers.create({ timeout_seconds: 600 });

const browser = await chromium.connectOverCDP(kernelBrowser.cdp_ws_url);
const page = browser.contexts()[0].pages()[0];
await page.goto('https://example.com');

await kernel.browsers.deleteByID(kernelBrowser.session_id);

from kernel import Kernel
from playwright.sync_api import sync_playwright

kernel = Kernel()
kernel_browser = kernel.browsers.create(timeout_seconds=600)

with sync_playwright() as p:
    browser = p.chromium.connect_over_cdp(kernel_browser.cdp_ws_url)
    page = browser.contexts[0].pages[0]
    page.goto("https://example.com")

kernel.browsers.delete_by_id(kernel_browser.session_id)

​

Then make these three changes

1. Stop connecting over CDP for the hot path. Playwright execution runs your code inside the browser’s VM: no round trip per action, no connection to keep alive, and no CDP fingerprint for anti-bot vendors to read. See how you drive the browser.
2. Replace your session-state handling with profiles, and your login scripts with managed auth.
3. Delete your warm-pool code. Browser pools hold pre-configured browsers with a fill rate, and idle pool browsers aren’t billed.

​

Two things to check before cutting over

• Region. Browsers default to us-east. If your loop runs elsewhere, either move it or run it on the App Platform — otherwise you trade container start-up latency for network latency.
• Isolation model. Each Kernel browser is a microVM with its own kernel, so per-browser isolation is stronger than a shared-kernel container. If you were multiplexing tabs across one Chrome to save memory, use more browsers instead.