Softwr

Testing · head to head

Kameleoon vs Split

Kameleoon logo

Kameleoon

Testing

A/B testing and feature experimentation with a hybrid client and server-side engine

From
On request
Rated
-
Full reviewWebsite
Split logo

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Kameleoon no rate card is published. Reported entry pricing around several hundred euros a month for the limited prompt-based tier comes from third parties rather than Kameleoon, so any budget you build before contacting sales is a guess.; Split split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract.
  • They diverge on capability: Kameleoon covers Visual A/B test editor, Split covers Feature flags with targeting.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Kameleoon and Split actually diverge.

Attributes where Kameleoon and Split differ
AttributeKameleoonSplit
PlatformsWeb, iOS, AndroidWeb, API, iOS, Android, Java, Node.js, Python, Go, .NET

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Testing).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Kameleoon

  • Visual A/B test editor
  • Server-side experimentation
  • Feature flags
  • Anti-flicker engine
  • AI personalisation
  • EU data hosting
  • Shared audiences
  • Statistics options

Only in Split

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

What people use each for

The jobs each tool is most often brought in to do.

Kameleoon

  • A European retailer whose legal team requires EU-hosted experimentation data and has ruled out US-only vendorsnot Split
  • A team running both marketing page tests and product feature rollouts that wants one results engine rather than two disagreeing onesnot Split
  • A media site where client-side flicker on a test variant is visibly damaging the reading experiencenot Split
  • An organisation re-tendering experimentation after Optimizely or VWO pricing changes and wanting an independent European vendornot Split

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Kameleoon
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Kameleoon
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Kameleoon
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Kameleoon

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Kameleoon

  • No rate card is published. Reported entry pricing around several hundred euros a month for the limited prompt-based tier comes from third parties rather than Kameleoon, so any budget you build before contacting sales is a guess.
  • Web experimentation, feature experimentation and personalisation are licensed as separate capabilities, so the unified platform story costs materially more than the entry configuration most buyers are first quoted.
  • The partner and agency ecosystem is concentrated in France and continental Europe; a buyer in North America or Asia will find fewer implementation specialists and less community knowledge than for Optimizely or VWO.
  • The integration catalogue is smaller than the market leaders, so a stack built on less common analytics or CDP tooling may need custom work that a larger vendor would cover natively.
  • Client-side visual testing still carries the structural problems of the approach, including performance cost and single-page-application fragility; the anti-flicker engine reduces the symptom but does not remove the dependency on the DOM staying stable.

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract.
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle.
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from.
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch.
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product.

Pricing, plan by plan

Kameleoon

On request
  • Kameleoon$undefined/year
    • Priced on monthly tested users and features licensed
    • Web experimentation, feature experimentation and personalisation licensed separately
    • Free trial of the prompt-based experimentation feature, with data not retained afterwards

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness Essentials$undefined/year
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness Enterprise$undefined/year
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Which should you pick?

Choose Kameleoon if

  • You need visual a/b test editor.
  • You work on Web, iOS, Android.
  • You also want server-side experimentation.
Kameleoon review

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Java, Node.js, Python, Go, .NET.
  • You also want metrics impact engine.
Split review

Questions people ask

Is Kameleoon or Split better?
Neither clearly leads. Kameleoon starts at On request and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kameleoon or Split?
Kameleoon starts at On request and Split at On request.
Does Kameleoon or Split run on more platforms?
Kameleoon runs on Web, iOS, Android. Split runs on Web, API, iOS, Android, Java, Node.js, Python, Go, .NET.
What is Kameleoon best used for?
Kameleoon is most often used for a european retailer whose legal team requires eu-hosted experimentation data and has ruled out us-only vendors, a team running both marketing page tests and product feature rollouts that wants one results engine rather than two disagreeing ones, a media site where client-side flicker on a test variant is visibly damaging the reading experience, an organisation re-tendering experimentation after optimizely or vwo pricing changes and wanting an independent european vendor. Of those, a european retailer whose legal team requires eu-hosted experimentation data and has ruled out us-only vendors and a team running both marketing page tests and product feature rollouts that wants one results engine rather than two disagreeing ones are not what Split is typically brought in for.
What can Kameleoon do that Split cannot?
Kameleoon covers Visual A/B test editor, Server-side experimentation, Feature flags, Anti-flicker engine. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Kameleoon: Does Kameleoon publish pricing?

No. Pricing depends on monthly tested users and which capabilities you licence, and requires a sales conversation.

Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

Kameleoon: Can I keep data in the EU?

Yes. EU hosting and a GDPR-first consent model are among the main reasons European buyers shortlist it.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

Kameleoon: Does it do feature flags as well as A/B tests?

Yes, through server-side SDKs, sharing audiences and results with the visual testing side.

Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

Kameleoon: How does it compare with Optimizely?

Similar capability at a smaller scale. Kameleoon's advantages are European data residency and an independent vendor; Optimizely's are ecosystem size and partner availability.

Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

Share

Related pages

More on Kameleoon

More on Split

Keep looking

Other head to heads