Kameleo’s multikernel architecture lets every browsing profile run on the most suitable browser engine at any moment. By separating the application from its browser kernels and shipping each kernel independently, we can minimize fingerprint mismatches, react to upstream security patches within days, and keep profile start‑up snappy because the engine you need is already cached locally.
What is a kernel in an anti‑detect browser?
A browser kernel is the rendering engine (Chroma, Junglefox) responsible for executing JavaScript, drawing pages, and exposing low‑level APIs that sophisticated bot‑detection scripts interrogate. Kernel version, therefore, is part of your fingerprint. Traditional anti‑detect solutions bundle one fixed kernel version, forcing users to wait for bulky client updates or live with growing discrepancies.
Consistent kernel rollouts
To stay ahead of bot‑detectors without breaking your scripts, we publish kernels on two separate tracks:
Chroma kernels - every official Chrome release +5 days
Google moved Chrome to a four‑week stable cadence in 2021, which means a new major version every 28 days. Our target is to ship the corresponding Chroma kernel within five calendar days of Google’s stable milestone appearing on their schedule.
Junglefox kernels - every two months
According to Mozilla's rapid-release calendar, Firefox still lands major updates roughly every four weeks. Because most anti‑fraud scripts lag behind Firefox changes, we balance freshness and stability by bundling every second upstream release, resulting in a predictable 8‑week rhythm.
Frequently asked questions
Will kernels auto‑update in the middle of a session?
No. Checks occur only when a profile starts; the active session stays on the same browser kernel until you close it.
Can I pin a specific kernel version?
Kernel selection is automatically tied to the browser version specified by your fingerprint, so profiles are effectively pinned from the moment they are created. If you want to switch a profile to a newer browser version, select the profile and use the Upgrade feature to pull the matching kernel, update the fingerprint, and keep using that version for all future launches.
Does multikernel slow down startup?
The initial kernel payload is delivered through a global CDN, so the first download typically finishes anywhere in the world in just a few seconds. Once the engine is cached locally, every subsequent profile starts to reuse the file on disk and never waits on the network.