Testing · head to head
GitHub Actions vs Kameleoon
Kameleoon
Testing
A/B testing and feature experimentation with a hybrid client and server-side engine
- From
- On request
- Rated
- -
The short version
- Only GitHub Actions has a free tier, so it costs nothing to try first.
- Each has a real cost: GitHub Actions private repository usage is capped at 2,000 minutes per month on GitHub Free and 3,000 on Pro and Team, with anything beyond billed; 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.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which GitHub Actions and Kameleoon actually diverge.
| Attribute | GitHub Actions | Kameleoon |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | subscription | quote |
| Free tier | Yes | No |
| Platforms | Web | Web, iOS, Android |
| Founded | 2008 | Unknown |
Identical on both: 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 GitHub Actions
Nothing recorded that Kameleoon does not also cover.
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
What people use each for
The jobs each tool is most often brought in to do.
GitHub Actions
- Running CI builds and tests on pushes and pull requestsnot Kameleoon
- Automating releases, container image builds and deployments from a repositorynot Kameleoon
- Scheduled maintenance jobs and repository automationnot Kameleoon
Kameleoon
- A European retailer whose legal team requires EU-hosted experimentation data and has ruled out US-only vendorsnot GitHub Actions
- A team running both marketing page tests and product feature rollouts that wants one results engine rather than two disagreeing onesnot GitHub Actions
- A media site where client-side flicker on a test variant is visibly damaging the reading experiencenot GitHub Actions
- An organisation re-tendering experimentation after Optimizely or VWO pricing changes and wanting an independent European vendornot GitHub Actions
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
GitHub Actions
- Private repository usage is capped at 2,000 minutes per month on GitHub Free and 3,000 on Pro and Team, with anything beyond billed
- Artifact storage is only 500 MB on GitHub Free and 2 GB on Team, and it is shared with GitHub Packages storage
- Larger runners are always charged for, even on public repositories and even when plan quota remains
- Windows runners cost $0.010 per minute against $0.006 for a 2-core Linux runner, so the same workflow costs more per platform
- macOS runners are charged at a higher per-minute rate than Linux runners
- Failed runs consume minutes, so a job that fails after 5 minutes and is re-run for 10 uses 15 minutes of quota
- Storage is billed on hourly accrual in GB-Hours, so deleting artifacts stops future charges but does not remove charges already accrued in the cycle
- Cache storage is a separate 10 GB per repository allowance and peak hourly usage above it is charged
- Minutes are charged to the repository owner, not the person who triggered the run, and anyone with write access can trigger runs
- Without a valid payment method on file, workflows are blocked as soon as the quota is exhausted
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.
Pricing, plan by plan
GitHub Actions
Free- FreeFree
- 2,000 CI/CD minutes per month
- Free for public repositories
- Team$4/month
- 3,000 CI/CD minutes per month
- Free for public repositories
- First 12 months at promotional rate
- Enterprise$21/month
- 50,000 CI/CD minutes per month
- Free for public repositories
- First 12 months at promotional rate
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
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.
Questions people ask
- Is GitHub Actions or Kameleoon better?
- Neither clearly leads. GitHub Actions starts at Free and Kameleoon at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, GitHub Actions or Kameleoon?
- GitHub Actions has a free tier; the other does not. Paid plans start at Free for GitHub Actions and On request for Kameleoon.
- Does GitHub Actions or Kameleoon run on more platforms?
- GitHub Actions runs on Web. Kameleoon runs on Web, iOS, Android.
- Can I use GitHub Actions for free?
- Yes. GitHub Actions has a free tier, so you can try it without paying. Kameleoon starts at On request.
- What is GitHub Actions best used for?
- GitHub Actions is most often used for running ci builds and tests on pushes and pull requests, automating releases, container image builds and deployments from a repository, scheduled maintenance jobs and repository automation. Of those, running ci builds and tests on pushes and pull requests and automating releases, container image builds and deployments from a repository are not what Kameleoon is typically brought in for.
- What can GitHub Actions do that Kameleoon cannot?
- Kameleoon covers Visual A/B test editor, Server-side experimentation, Feature flags, Anti-flicker engine.
Answered from the vendors’ own pages
GitHub Actions: How much does GitHub Actions cost?
GitHub Actions is free for public repositories. For private repositories, the Team plan costs $4 per user per month (first 12 months) with 3,000 CI/CD minutes, and the Enterprise plan costs $21 per user per month (first 12 months) with 50,000 CI/CD minutes.
SourceKameleoon: Does Kameleoon publish pricing?
No. Pricing depends on monthly tested users and which capabilities you licence, and requires a sales conversation.
GitHub Actions: Is there a free version of GitHub Actions?
Yes, GitHub Actions is free for all public repositories. The Free plan for private repositories includes 2,000 CI/CD minutes per month. All tiers include free CI/CD minutes for public repository workflows.
SourceKameleoon: 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.
GitHub Actions: What does the Team plan add to GitHub Actions?
The Team plan provides 3,000 CI/CD minutes per month compared to 2,000 on the Free plan. It costs $4 per user per month for the first 12 months. Minutes apply only to private repository workflows.
SourceKameleoon: 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.
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.
Related pages
More on GitHub Actions
Other head to heads
- GitHub Actions vs CircleCI
- GitHub Actions vs Insomnia
- GitHub Actions vs BrowserStack
- GitHub Actions vs BugHerd
- GitHub Actions vs TestRail
- GitHub Actions vs k6
- GitHub Actions vs Testsigma
- GitHub Actions vs Appium
- GitHub Actions vs Robot Framework
- GitHub Actions vs Katalon
- GitHub Actions vs GrowthBook
- GitHub Actions vs mabl
- GitHub Actions vs Tricentis Tosca
- GitHub Actions vs Xray Test Management
- GitHub Actions vs Zephyr Scale
- GitHub Actions vs JUnit
- GitHub Actions vs Qase
- GitHub Actions vs WebdriverIO
- GitHub Actions vs Split
- GitHub Actions vs Eppo
- GitHub Actions vs Applitools
- GitHub Actions vs Vitest
- GitHub Actions vs PractiTest
- GitHub Actions vs Ranorex
- GitHub Actions vs Sauce Labs
- Kameleoon vs CircleCI
- Kameleoon vs Insomnia
- Kameleoon vs BrowserStack
- Kameleoon vs BugHerd
- Kameleoon vs TestRail
- Kameleoon vs k6
- Kameleoon vs Testsigma
- Kameleoon vs Appium
- Kameleoon vs Robot Framework
- Kameleoon vs Katalon
- Kameleoon vs GrowthBook
- Kameleoon vs mabl
- Kameleoon vs Tricentis Tosca
- Kameleoon vs Xray Test Management
- Kameleoon vs Zephyr Scale
- Kameleoon vs JUnit
- Kameleoon vs Qase
- Kameleoon vs WebdriverIO
- Kameleoon vs Split
- Kameleoon vs Eppo
- Kameleoon vs Applitools
- Kameleoon vs Vitest
- Kameleoon vs PractiTest
- Kameleoon vs Ranorex
- Kameleoon vs Sauce Labs