What Kameleo is

Kameleo presents profiles as an automation primitive across a desktop GUI, standalone Engine, and container images. Its browser kernels cover Chromium- and Firefox-derived families, while cloud profiles add portability and locks.

  • Profile model: Persistent profiles carry cookies, storage, history, bookmarks, proxies, and extensions and can use local or cloud storage.
  • Platforms: Kameleo documents Windows and Apple-silicon macOS desktop support plus official Linux and Windows container images.
  • Team model: Cloud profiles synchronize across users or devices and use locking; local profiles remain device-bound.
  • Automation: The Local Engine API, Python, JavaScript, and C# SDKs, Selenium, Puppeteer, Playwright, headless mode, and containers make automation the core workflow.

Who Kameleo fits

A browser-profile and automation engine supporting persistent local or cloud profiles, desktop and headless operation, language SDKs, and container deployment.

  • Developer-led teams prioritizing SDK automation and headless execution.
  • Teams that need Docker or both Chromium- and Firefox-derived runtimes.

Kameleo and Isoline

Kameleo is the stronger current fit for containers, SDK-led automation, and Firefox-family execution. Isoline is pursuing a narrower signed-Chromium lifecycle with recovery and governance evidence.

Isoline is in its foundation phase. Its local-first profile model, optional client-side-encrypted synchronization, recovery controls, and versioned automation interfaces are product direction until release evidence says otherwise. No public Isoline pricing or feature parity is implied.

  • Compare documented current behavior, not feature-list promises.
  • Validate migration, recovery, update freshness, permissions, and automation against the intended workflow.

What to verify before choosing Kameleo

Official documentation defines the factual starting point. A production decision still needs hands-on testing with authorized profiles, proxies, extensions, failure cases, and team permissions.

  • Match SDK and Engine versions in the compatibility plan.
  • Test profile locks and cloud write recovery under interruption.
  • Do not treat Safari or iOS-labelled environments as native WebKit or Safari execution.

Evidence and scope

This comparison uses public product information and Isoline's current foundation plan. Features, limits, and prices can change.

Before you decide

Confirm current pricing, limits, platform support, and contract terms with each vendor. Test any browser with your own authorized workflow before migrating.