Two stealth browser engines. One container.
Chroma and Junglefox stealth browsers on any Docker environment. No GPU. No display server. Your existing Playwright, Puppeteer, or Selenium code connects without changes.

Get running in 3 steps
Create your account, spin up a container, and connect your automation script. That's all it takes to start running browser instances at scale.
Create a Kameleo account
Start the container
Automate with Playwright
Your automation stack deserves a real anti-detect browser. In a container.
Most anti-detect tools ship as desktop apps for manual use. Running them in production means X11-over-SSH tunnels, Windows VMs bolted onto Linux infrastructure, or DIY stealth wrappers that break every time Chrome updates.
Kameleo Docker runs on Linux and Windows servers. It brings the full fingerprint masking stack — real device profiles, C++ engine-level patches, automatic geo-location matching — into a container you can drop into any server, CI pipeline, or Kubernetes cluster.
Unlimited, real browser fingerprints
Profiles sourced from millions of real devices, not static templates. Every session gets a unique, convincing fingerprint that reflects how real hardware actually looks to anti-bot systems.
Fast release cycles for browser updates
Chroma kernels ship within 5 days of every Chrome stable release. Junglefox follows every 2 months. Your scrapers keep running when browsers update — no manual patching required.
Continuously auto-tested stealth mode
Every release is validated against real anti-bot systems and fingerprint detectors before it ships. You get a browser that's confirmed undetected, not one you have to test yourself.
Linux and Windows containers
One image, two platforms. Docker pulls the right variant automatically: Linux (Ubuntu 22.04) or Windows (Server Core 2022). Same Local API, same fingerprint database, same two browser engines on both.
Drop into your existing stack
Works with Playwright, Puppeteer, and Selenium out of the box. Point your existing automation at the container's WebSocket endpoint. No framework rewrite, no new SDK to learn.
Your data stays on your servers
All scraping runs on your own infrastructure. No traffic routed through vendor APIs, no per-request pricing. Cost is fixed by concurrent browsers, predictable at any scale.
Questions
Everything you need to know about running Kameleo in Docker
No. Docker is included in every plan. Same concurrent browser limits, same RPM limits, no additional cost.
Yes. Give each container its own named volume to avoid conflicts when working with profiles simultaneously. Sharing a single volume across containers can cause issues. Mount the data directory on every container so kernels persist across recreations.
Same Local API, same fingerprint database, same two browser engines. The difference is the host OS: Linux (Ubuntu 22.04, amd64) vs Windows (Server Core 2022). Automation code works identically on both.
Use Kubernetes or Docker Swarm to orchestrate thousands of instances. Kameleo integrates with standard container orchestration platforms without special configuration.
Need more help?
Check our documentation or reach out







%201.png)
