LaunchDarkly vs ConfigCat vs Flagsmith - Which Flag Tool Fits You in 2026?
Three feature-flag tools, three completely different pricing philosophies. Here is how LaunchDarkly, ConfigCat and Flagsmith actually differ, and which one to pick for your situation.
Published:
If you’re comparing LaunchDarkly, ConfigCat and Flagsmith, you’ve probably already worked out that they aren’t really three versions of the same thing. They’re three different answers to the same question: how should a feature-flag tool charge you?
LaunchDarkly is the incumbent - the deepest flag platform in the category, and the one most people are trying to leave because of the bill. ConfigCat is the flat-pricing rebel that refuses to bill per user at all. Flagsmith is the open-source underdog you can run on your own servers. The pricing model is the real decision here, not the feature checklist. Pick the philosophy that fits how you’ll grow, and the rest follows.
Every number below was read from each vendor’s own tool page. Here’s how they line up.
The short version
| LaunchDarkly | ConfigCat | Flagsmith | |
|---|---|---|---|
| Pricing model | $10/service connection + $8.33/1k client-side MAU | Flat tier, config-download volume, no MAU | Per request, per seat above Free |
| Free tier | $0 Developer, unlimited seats | $0 Forever Free, 5M downloads | $0, 50k requests/mo, 1 seat |
| Cheapest paid | Usage-based (Vendr median ~$72k/yr) | $110/mo Pro | $40/mo annual Start-Up |
| Self-host / OSS | No, closed SaaS | No, backend is proprietary | Yes, BSD-3-Clause |
| Experimentation | Yes, higher tiers, priced on top | None, no stats engine | Basic A/B from Start-Up |
| Best for | Deepest flag tooling at enterprise scale | Flat, headcount-independent pricing | Open-source flags without lock-in |
LaunchDarkly - the deepest tooling, at a price you have to model
LaunchDarkly is the category standard, and it earns that. Around 38 SDKs, advanced targeting rules, and guarded releases that automatically roll back when a metric goes bad - genuinely best-in-class, and the reason its G2 sits at 4.5 across 681 reviews. Seats are unlimited on every tier, so you’re never taxed for adding a developer.
The tax is elsewhere, and it’s the gotcha. LaunchDarkly bills $10 per service connection per month plus $8.33 per 1,000 client-side MAU, charged on your highest-volume context kind. A context can be a user, a device, an anonymous session. If you track 300,000 users but 500,000 devices, you pay for 500,000 - the bigger number - even if you only ever target users. Add-ons stack on top, and at 10M MAU they alone can exceed $33,700 a month. Vendr’s third-party contract data puts the real median around $72,000 a year, ranging from $19,500 to $165,700. Renewals are the recurring complaint, reported to double on legacy plans.
LaunchDarkly is the right call when you genuinely need the top of the feature set and can forecast your context volume. For everyone else, the two below exist for a reason.
ConfigCat - flat pricing that ignores your headcount
ConfigCat’s whole pitch is the inverse of LaunchDarkly’s meter. It charges no per-seat and no per-MAU fees. MAUs, contexts and flag reads are unlimited on every tier, including Free. You pay by config-download volume and caps on flags, environments and products instead. A consumer app with millions of users pays the same as a small internal tool, as long as their download volume sits in the same tier. It’s bootstrapped and profitable out of Budapest, founded in 2018, with no VC-driven pricing pressure.
The ladder is fully published: Forever Free at $0 (10 flags, 5M downloads, no credit card), Pro at $110/mo, Smart at $325/mo, Enterprise at $900/mo. For teams burned by MAU billing, that predictability is the entire appeal.
The catch hiding in the friendly model: pricing is gated on config downloads, so a chatty SDK polling too often can push you from Free to Pro to Smart on request volume alone, without adding a single user. The tier jumps are large - 5M to 25M to 250M downloads. The fix is real but needs attention: cache aggressively and use the SDK proxy. Do that and ConfigCat stays as cheap as it looks. There’s no experimentation and no self-host - it isn’t trying to be either.
Flagsmith - open source you can actually run yourself
Flagsmith is the answer when you want out of the SaaS relationship entirely. It’s genuinely open source under BSD-3-Clause and genuinely self-hostable via Docker, Kubernetes, on-prem and air-gapped - the thing neither LaunchDarkly nor ConfigCat can offer, since both keep their backends closed. The billing unit is requests, which is clean to reason about: no MAU trap, no highest-volume-context-kind surprise.
It’s also the most transparent on price, and the cheapest paid entry of the three. The cloud Free tier gives 50,000 requests a month with unlimited flags, environments and segments. Start-Up is $40/mo on annual billing (or $45 monthly) for 1M requests. Scale-Up is $250/mo annual for 5M+ requests. It has the highest G2 rating here at 4.8, though from only 37 reviews - read that as “small and loved,” not “battle-tested at every scale.”
The honest trade-offs: it’s a roughly 12-person bootstrapped London team, so the ecosystem is smaller; A/B testing is basic rather than a real stats engine; and self-hosting the Django and Postgres stack is real DevOps work, not a free lunch. If you have the capacity and want no lock-in, Flagsmith is the one to start with.
LaunchDarkly vs ConfigCat vs Flagsmith - which should you pick?
Match the tool to your actual constraint:
- You need the deepest targeting, guarded releases with auto-rollback, and broad SDK coverage - stay on LaunchDarkly. Nothing here matches its depth. Just price your highest-volume context kind first, because devices and anonymous sessions are what blow up the estimate.
- You want the MAU surprise to stop and you’re happy on hosted SaaS - ConfigCat. Flat, predictable, unlimited users, and the only meter that moves is config downloads. Watch your polling and it stays cheap.
- You want open source, no lock-in, and the ability to self-host - Flagsmith. Cheapest paid tier, transparent pricing, and a real self-host path if you have the DevOps to run it.
- You need serious experimentation - none of these three. ConfigCat has no stats engine, Flagsmith’s A/B is basic, and LaunchDarkly gates it behind higher tiers. That’s a different tool search.
One note on the numbers. LaunchDarkly’s contract figures - the ~$72,000 median, the $19,500 to $165,700 range - are from Vendr’s third-party buyer data, not LaunchDarkly’s pricing page, which doesn’t publish them. Every price on ConfigCat and Flagsmith was read from each vendor’s own site. The right pick is whichever pricing philosophy matches how you actually plan to grow.
Frequently Asked Questions
Which is cheapest - LaunchDarkly, ConfigCat or Flagsmith?
Flagsmith and ConfigCat are both far cheaper than LaunchDarkly. Flagsmith has the cheapest paid entry at $40/mo on annual billing for 1M requests, and its open-source self-host is free outright. ConfigCat starts at $110/mo for Pro but never charges per seat or per MAU. LaunchDarkly is usage-based on client-side MAU, and Vendr's contract data puts its median around $72,000 a year. If price is the deciding factor, it's Flagsmith or ConfigCat, not LaunchDarkly.
Can you self-host ConfigCat or Flagsmith?
Only Flagsmith. Flagsmith is open source under BSD-3-Clause and genuinely self-hostable via Docker, Kubernetes, on-prem and air-gapped. ConfigCat's SDKs are open source under MIT, but its management backend is proprietary hosted SaaS with no self-host option. LaunchDarkly is closed SaaS too - only its client SDKs are open. So if self-hosting is a requirement, Flagsmith is the only one of the three that delivers it.
Why do teams leave LaunchDarkly for ConfigCat or Flagsmith?
The bill. LaunchDarkly bills $8.33 per 1,000 client-side MAU on your highest-volume context kind, so devices and anonymous sessions can dwarf your user count, and renewals are widely reported to jump. ConfigCat removes MAU billing entirely with flat, headcount-independent pricing. Flagsmith bills on requests instead of MAU and lets you self-host. Both stop the pricing surprise that sends people searching in the first place.
Does ConfigCat or Flagsmith do experimentation?
Neither is a real experimentation platform. ConfigCat has no statistics engine at all - just percentage rollouts and targeting rules. Flagsmith has basic A/B testing from its Start-Up tier but not a heavyweight stats engine. LaunchDarkly has experimentation, but it's gated to higher tiers and priced on top. If serious A/B testing is the goal, none of these three is the right pick - look at Statsig or GrowthBook instead.
Explore More
Tool Reviews
Related Articles
- LaunchDarkly vs ConfigCat - Which Is Right for You in 2026?
- LaunchDarkly vs Flagsmith - The Honest 2026 Comparison
- Feature Flags in Python, Done Right - A 2026 Tutorial for Flask and Django
- 4 ConfigCat Alternatives When Traffic Tier Jumps Bite (2026)
- ConfigCat Pricing, Decoded - The No-MAU Model and the Trap Hiding In It (2026)
Free Newsletter
Get the Feature Flags Newsletter
Platform benchmarks, real pricing data and progressive delivery practice. No spam.
Related Articles
Multivariate Testing vs A/B Testing - When to Use Each in 2026
A/B testing changes one thing, multivariate testing varies several at once and measures how they interact. Here is the real difference, the sample-size cost of MVT, when interaction effects justify it, and when A/B/n is the smarter choice.
July 28, 2026
comparisonCanary vs Blue-Green Deployment - Which to Use in 2026 (and Where Flags Fit)
A neutral comparison of canary and blue-green deployment - how each works, the real trade-offs on cost, rollback and risk, and where feature flags change the calculus.
July 26, 2026
comparisonConfigCat vs Flagsmith (2026) - Flat Pricing vs Open Source, by Use Case
ConfigCat is hosted with no per-MAU fee. Flagsmith is open source and self-hostable from $40/mo. Both are cheap - here's which one actually fits, honestly, by use case.
July 26, 2026
LaunchDarkly Review
ConfigCat Review
Flagsmith Review