The use case: how Flint deploys Kernel
Flint runs an autonomous website platform whose agent uses Kernel's hosted browsers to visit a customer's site and clone their brand, and to run real-time web research such as visiting competitor sites, taking screenshots and running QA loops. It replaced its self-hosted Chromium and Playwright setup with Kernel.
More reported results
Figures published in Kernel’s case study. They are not independently measured by usedby.
5x fewer bot detection errors
after switching to kernel's browsers, cold starts dropped from 5 seconds to about 30 ms.
In the customer’s words
when it comes to infra, i'll take reliability over great developer experience. kernel has both.Other companies using Kernel
Customers across industries, with public evidence.
FelicityConfirmed
RyeConfirmed
StablyConfirmed
The Prompting CompanyConfirmed
Cash AppObserved
Claim HealthObservedGo straight to the source
Based on Kernel’s published case study. We check the public evidence; the results are reported by the vendor.
kernel.sh- Source published
- Mar 30, 2026
- Last checked
- Oct 25, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 167xChecked
Printed word for word on the page, near the name of Flint.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Flint.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Flint uses KernelChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
after switching to kernel's browsers, cold starts dropped from 5 seconds to about 30 ms. this enabled an entirely new use case: flint customers could now run real-time, open-ended web research—visiting competitor sites, taking screenshots for inspiration, and running qa loops.