Kameleo

Kameleo describes its browser as designed to handle anti-bot defenses and says it supports scraping, automation, and multi-account management. For a profile, the practical question is what browser data carries across sessions.

The vendor says profiles persist across sessions and can retain cookies, local storage, and extensions. This makes persistence a concrete part of the workflow to clarify: which data the team expects to retain, and how it relates to its own account-handling practices.

Kameleo’s Knowledge Base covers fingerprint settings for browser profiles. Its developer page states that 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 performance evidence.

Ask support how a plan’s concurrent-browser and API limits apply to the intended mix of manual and automated sessions; Kameleo counts both kinds of active session toward concurrency. The pricing page lists plan-specific concurrency and RPM limits, so a concrete workload is more useful than a general question about capacity.

The Support Center is one contact route, while the Knowledge Base covers common questions, troubleshooting, usage, limits, and policies. The vendor also lists Discord, Telegram, a Help Center, and SDK repositories as community or support resources. Ask which route handles account questions and which handles technical troubleshooting.

Before registering, ask what customer service includes for your integration and who handles issues in proprietary code or connections to other systems; the terms exclude those areas from customer-service support. For billing questions, the Knowledge Base covers payments, subscriptions, invoices, and account details.

Kameleo frames pricing around concurrent browsers, and its pricing page lists the Free plan at €0 per month with two concurrent browsers. The provider says the Free plan includes 300 minutes of browser usage time, while paid plans have no usage time limits. Treat usage time and concurrent sessions as separate checks: the vendor states that active manual and automated sessions count toward concurrency.

The terms say a qualifying payment method may trigger automatic renewal at the end of each billing cycle. They direct customers to the Pricing sub-page for fees, while the vendor describes costs as fixed by concurrent browsers. For Enterprise, the pricing page lists a 60-minute call with experts and package customization.

A refund request must go through customer service within 24 hours of activating the service, according to the terms. Refund claims are manually processed and may be accepted or rejected at the provider’s discretion. Before payment, ask how renewal applies to the chosen billing cycle and how to submit a refund request.

The Local API and SDK packages connect Kameleo with Python, JavaScript, and C#, according to the pricing page. The vendor says existing Selenium, Puppeteer, and Playwright scripts can connect through its WebSocket endpoint; its Docker image is also described as supporting those frameworks without changes to existing automation code.

For teams choosing between a GUI workflow and scripts, Kameleo says users can test workflows in the GUI before writing code. The vendor lists Windows, macOS, and Docker, and describes Docker-ready deployment and an SDK. It says Docker runs on Linux and Windows servers; its Linux container uses Ubuntu 22.04, while the Windows container uses Server Core 2022.

Kameleo says the Docker service runs scraping on customers’ own infrastructure without routing traffic through vendor APIs. The vendor also describes Kubernetes and Docker Swarm integration for scaling. For container deployments, its documentation says each container should have its own named volume and that the data directory should be mounted on every container so kernels persist across recreations. Sharing one volume across containers can cause issues, according to the vendor.

The terms restrict use to customers’ own business purposes and prohibit agency use. They also prohibit deciphering program code or searching for source code or internal structures related to the service. These conditions should be checked against the intended business arrangement before registration.

The provider may terminate the agreement with 15 days’ notice without explaining why. Refund claims are manually processed and may be accepted or rejected at the provider’s discretion, while a refund request must be sent through customer service within 24 hours of activation. Customer service excludes support for proprietary code and integrations to other systems.

Plan limits also matter: active manual and automated sessions count toward concurrent-browser capacity, and API throughput varies by plan. Docker documentation advises a separate named volume for each container and warns that sharing one volume can cause issues. Several details are missing; they are listed under What we could not confirm. Check the agreement’s use, termination, and refund conditions before signing up.

The vendor and its documentation describe these controls for browser workflows.

• Existing Selenium, Puppeteer, and Playwright scripts can connect through Kameleo’s WebSocket endpoint, according to the provider.
• The vendor says teams can test workflows in the GUI before writing code.
• Profiles can persist across sessions and retain cookies, local storage, and extensions, according to the vendor.
• The vendor says Kameleo supports Docker deployment and offers an SDK.
• The Knowledge Base covers installation, basic settings, payments, subscriptions, account details, groups, cloud, and proxies.

These controls describe workflow options, not evidence of performance; compare them with the documented terms and support boundaries before registration.

Kameleo’s terms limit use to customers’ own business purposes and prohibit agency use. That makes the intended business arrangement a threshold check, whether browser sessions are handled by one operator or shared across a team.

For workload planning, distinguish manual sessions from automated ones: both count toward the concurrent-browser limit. API request volume is another plan condition, so map expected activity to the plan’s concurrency and request limits before deciding whether the license fits.

Compare browser tools by profile persistence, automation compatibility, concurrent-session and request caps, deployment model, support scope, and acceptable-use terms. In general, the right comparison follows the actual workflow: what data a profile retains, how scripts connect, and which business uses the agreement permits.

What counts toward the concurrent-browser limit?

Each active browser session counts toward the concurrent-browser limit, whether it is manual or automated. Include both kinds of work when estimating the sessions that need to run at the same time; the plan’s capacity is not limited to scripted activity.

What does the Free plan include?

The Free plan costs €0 per month, includes two concurrent browsers, and provides 300 minutes of browser usage time, according to the pricing page. Treat the time allowance and concurrent-browser count as separate conditions when assessing a workflow.

How do automation frameworks connect?

Kameleo supports existing Selenium, Puppeteer, and Playwright scripts through its WebSocket endpoint, according to the provider. The vendor also says its SDKs support these frameworks and are available for Python, JavaScript, and C#. Check that the integration route matches the scripts and language your team uses.

What does profile persistence mean?

The vendor says profiles persist across sessions and can retain cookies, local storage, and extensions. For a workflow that reuses browser contexts, clarify which data needs to carry over and how that fits your own account-handling practices.

Is agency use permitted?

No: the terms say customers may use Kameleo only for their own business purposes and prohibit agency use. A team should compare its actual service arrangement with that restriction before registering, rather than treating team-member capacity as permission for every business model.

How do withdrawal and refund-request terms differ?

The terms say consumers using the service for private purposes may withdraw within 14 days of registration, subject to stated conditions. Separately, a refund request must be sent through customer service within 24 hours of activation. Check which provision applies to your circumstances and the conditions in the terms.

Fits if… your intended business use complies with the terms and you have matched expected sessions and API request volume to the applicable plan limits.

Probably not if… the work depends on agency use, which the agreement prohibits.

Main risk… is committing before understanding renewal and refund conditions; check the billing terms and request process before registering.