Anti-detect browsers
Kameleo
A browser profile groups browser settings and retained session data, giving a workflow a distinct environment to manage. Kameleo describes its profiles as fingerprinted and says they can retain cookies, local storage, and extensions across sessions. The key buying distinction is that profile and team-member counts do not tell you how many browsers can run at once; Kameleo’s pricing counts each active session, including manual use.
This is relevant to media buyers comparing profile organization with the capacity their automation or manual work actually needs.
Editorial review based on public sources, without hands-on testing; facts checked on 2026-10-31.
This page contains no partner link to this service.
- Logo
Service logos remain the property of their owners; we use them for identification only.
- Name
- Kameleo
- Category
- Anti-detect browsers
- Official site
- kameleo.io · No link provided
- Facts checked
Which Kameleo limits shape the plans?
The pricing page lists plans for browser automation and profile management, including Free, Startup, Business, and Enterprise tiers, according to the pricing page checked 2026-10-31.
- Plans: Free, Startup, Business, and Enterprise (pricing page, checked 2026-10-31).
- Free price: €0 per month (pricing page, checked 2026-10-31).
- Free concurrent browsers: two (pricing page, checked 2026-10-31).
- Free browser usage time: 300 minutes (pricing page, checked 2026-10-31).
- API throughput: 60 to 1200 requests per minute, depending on plan (pricing page, checked 2026-10-31).
Each active browser session counts toward the concurrent browser limit, whether manual or automated.
What does a Kameleo profile organize?
A Kameleo profile is presented as a fingerprinted browser environment, with session data that can persist between uses. The vendor says profiles can retain cookies, local storage, and extensions across sessions, separating saved profile state from the number of sessions running concurrently.
The Knowledge Base covers fingerprint settings for profiles, alongside separate material on groups, cloud, and proxies.
For buyers, the practical distinction is between organizing a browser environment for later use and paying for simultaneous browser activity. Kameleo’s plan terms count each active browser session toward concurrency, whether it is opened manually or through automation.
Which questions belong with support?
Ask support to define what each plan’s concurrency allowance covers, including whether manual browser use shares capacity with automation. Kameleo states that every active session counts, while its Knowledge Base covers usage, limits, and policies.
Clarify which channel handles your issue before registering. The provider lists a Support Center, while its developer materials list Discord, Telegram, a Help Center, and SDK repositories as community or support resources.
If your workflow depends on proprietary code or an integration with another system, ask who will troubleshoot it. Kameleo’s terms exclude support for customers’ proprietary code and integrations to other systems. The Knowledge Base offers troubleshooting checks and solutions, but that is not the same as support for custom code.
Questions about billing, profile-data handling, and support availability by plan also belong in that conversation. The Knowledge Base covers payments, subscriptions, invoices, and account details; the available plan and billing facts do not settle every operational detail.
How do Free and paid limits differ?
The Free plan pairs two concurrent browsers with a browser-usage allowance, so compare session capacity and usage time as separate limits. Kameleo describes paid pricing as concurrency-based and says costs are fixed by concurrent browsers; the agreement says fees are listed on the provider's Pricing sub-page.
Each active browser session, manual or automated, counts toward the concurrent browser limit.
Billing terms matter alongside the plan allowance. A qualifying payment method may trigger automatic renewal at the end of a billing cycle, and customers may terminate an agreement at any time, effective at that cycle’s end. Consumers using the service privately may withdraw within 14 days of registration, subject to the stated conditions.
A refund request must go through customer service within 24 hours of service activation. The provider says refund claims are processed manually and may be accepted or rejected at its discretion, so submitting a request does not itself establish that a refund will be granted.
How do scripts connect to profiles?
Kameleo describes a path from GUI workflow testing to script-based automation: users can test workflows in the GUI before writing code, then connect scripts through a Local API or SDK packages. The provider also says existing Selenium, Puppeteer, and Playwright scripts can connect through its WebSocket endpoint.
The listed SDK languages are Python, JavaScript, and C#, and the developer materials describe framework support for Selenium, Puppeteer, and Playwright. These are the named integration options to match against a team’s existing automation stack before choosing a plan.
Kameleo says its Docker image supports those frameworks without changes to existing automation code. The vendor also describes Docker-ready deployment and lists Windows, macOS, and Docker. Its page says users can start the engine and connect an automation script without an account, then create an account later.
What supports automation work?
Kameleo says its browser kernels ship with continuously updated, authentic fingerprints, and that canvas, WebGL, CDP, timezone, geolocation, and fonts are handled out of the box. These are vendor descriptions, not independent validation of how those signals behave in a particular workflow.
The provider says browser updates are released on fast cycles and that stealth mode is continuously auto-tested. Its Docker page gives separate update schedules: Chroma kernels ship within 5 days of each Chrome stable release, while Junglefox updates every 2 months.
Docker deployment is described as running scraping on customers’ own infrastructure without routing traffic through vendor APIs. That deployment model gives teams a concrete point to assess against their infrastructure requirements, while the claimed behavior remains the provider’s description.
Which conditions narrow Kameleo use?
A paid plan’s concurrency capacity also covers hands-on browsing, not only automated sessions, so manual work uses the same allowance. The terms also limit use to customers’ own business purposes and prohibit agency use.
Kameleo’s terms permit the provider to terminate the agreement with notice, without explaining why. They also prohibit customers from deciphering program code or searching for source code or internal structures related to the service.
Docker deployment has a storage condition: each container should have its own named volume to avoid profile conflicts, and sharing one volume can cause issues. The data directory should also be mounted on every container so kernels persist across recreations.
Customer service excludes help with proprietary code and integrations to other systems. Several other purchasing details remain open; they are listed under What we could not confirm.
Who fits the stated browser workflows?
Kameleo’s stated scope is web scraping, browser automation, and multi-account management, making it relevant to teams whose work uses those workflows. Its vendor-described options include an SDK, Docker deployment, and support for Selenium, Puppeteer, and Playwright scripts.
Docker may suit teams that want scraping to run on their own infrastructure; Kameleo says its Docker service integrates with Kubernetes and Docker Swarm for scaling. Before choosing it, check that your deployment and automation tooling match the documented options, and that your use follows platform rules and local law.
Which criteria should alternatives match?
Compare profile and concurrent-session limits separately, then check team access, automation interfaces, acceptable-use terms, and deployment requirements. In general, a close alternative should fit the workflow and operating conditions you need, rather than matching a feature list alone.
What we could not confirm
- Paid-tier profile counts and seat allowances
- Accepted payment methods, taxes, and billing-cycle schedule
- Profile-data storage location, retention, deletion, and privacy controls
- Support response times and availability by plan
- Independent evidence for fingerprint, stealth, and uptime claims
What do Kameleo’s terms answer?
Do manual sessions count toward the browser limit?
Yes. Kameleo’s pricing terms count each active browser session toward the concurrent-browser limit, whether the session is manual or automated. This means hands-on browsing and scripted use draw on the same session capacity rather than separate allowances.
What does the Free plan include?
The pricing page lists the Free plan at €0 per month with two concurrent browsers. It also lists 300 minutes of browser usage time for Free. These are separate limits: one concerns simultaneous sessions, while the other concerns usage time.
Which automation connections does Kameleo list?
Kameleo says existing Selenium, Puppeteer, and Playwright scripts connect through its WebSocket endpoint. It also lists a Local API and SDK packages for Python, JavaScript, and C#. The developer materials describe framework support through SDKs for those languages.
Is agency use allowed?
No. The terms say customers may use the service only for their own business purposes and prohibit agency use. Teams assessing a client-services workflow should settle that contractual condition before registering, rather than treating technical access as permission for that use.
How do renewal and refund requests work?
A qualifying payment method may trigger automatic renewal at the end of each billing cycle, according to the Terms. A refund request must go through customer service within 24 hours of activation. The provider says claims are handled manually and may be accepted or rejected at its discretion.
What does customer service exclude?
Customer service excludes support for customers’ proprietary code and integrations to other systems, according to the Terms. If a workflow relies on either, clarify who will maintain and troubleshoot that part before committing to the service.
Is Kameleo ready for a trial?
Fits if… your workflow matches the stated automation or scraping scope, and you have resolved the first support questions about limits, support channels, and custom-code coverage.
Probably not if… your use depends on agency work, which the terms prohibit, or on support for proprietary code and third-party integrations.
Main risk… is treating profiles as a measure of simultaneous capacity: Kameleo counts every active session, including manual use. The provider says users can start without an account and create one later, but check the usage terms before proceeding.
Sources
The facts above were taken from the public pages listed here, and each entry shows the date it was read.
- developer.kameleo.iochecked
- kameleo.io/pricingchecked
- help.kameleo.iochecked
- kameleo.io/terms-conditionschecked
- kameleo.io/dockerchecked
- kameleo.iochecked
- kameleo.io/about-uschecked
How we put this page together
Editorial team of Stack Shelf. Prepared by the editorial team of Stack Shelf from the public sources listed above; the facts were checked on 2026-10-31. Nobody tried the service in practice. We revise the text whenever those sources are updated.
Last updated:
Right of reply
If you represent Kameleo and think this entry is inaccurate or out of date, write to us and attach evidence. After the refutation is documented, the entry is corrected or removed. Entries are not removed or toned down in exchange for money.
- Our contact for replies
- No data available
- Response time
- No data available