We’ve been building infrastructure to spin up browsers for AI agents. Originally, we built[0] it as a pool of warm Docker containers running Chromium, exposing:<p>- Chrome DevTools Protocol (for Playwright/Puppeteer)<p>- noVNC (for live view)<p>We’ve been following the unikernel space for a while, so we decided to see if we could get our image on one. We went with Unikraft Cloud[1]. Here’s how it did:<p>- Boot-up time: 10–20ms (vs. ~5s for Docker containers)<p>- Near 0 CPU/memory consumption when idle<p>- Still ~8GB RAM when active (headful Chromium)<p>Potential use cases:<p>- Standby mode during long-running jobs: unikernels can sleep after X sec of inactivity, reducing clock time costs<p>- Session reuse: auth/session cookies persist for hours/days. Basically as long as the cookies are valid<p>- Cold start speed: good for low-latency, event-based handling<p>We open sourced it with Apache 2.0! Feel free to fork or submit an issue / PR. Open to feedback or suggestions. www.github.com/onkernel/kernel-images<p>==<p>[0] <a href="https://github.com/onkernel/kernel-images">https://github.com/onkernel/kernel-images</a><p>[1] <a href="https://unikraft.cloud/" rel="nofollow">https://unikraft.cloud/</a><p>[2] Thanks to the Unikraft Cloud team @fhuici @nderjung @razvandeax for helping us figure this out (we're not affiliated)<p>[3] (OPs) @rgarcia @juecd