ConfigCat vs Flagsmith (2026) - Flat Pricing vs Open Source, by Use Case

ConfigCat and Flagsmith get compared because they’re the two tools people reach for after LaunchDarkly’s bill scares them off. Both are cheap, both are simple, both publish their prices. But they solve the “I want affordable flags” problem in opposite ways, and picking the wrong one means either paying for infrastructure you didn’t need or self-hosting a stack you didn’t want to run.

The core split: ConfigCat is hosted SaaS with no per-MAU fee. Flagsmith is genuinely open source and self-hostable. That one difference drives almost every other decision here.

The short version

	ConfigCat	Flagsmith	Unleash
Best for	Flat, headcount-independent pricing	Open-source flags without lock-in	Pure self-hosting in your infra
License	Proprietary (SDKs MIT)	BSD-3-Clause	AGPL-3.0
Self-host	No	Yes (Docker, K8s, air-gapped)	Yes (air-gapped)
Billing model	Config downloads, no MAU	Requests	Per seat + API requests
Free tier	10 flags, 5M downloads	50k requests/mo	$0 self-hosted
Paid entry	$110/mo (Pro)	$40/mo annual (Start-Up)	$75/seat/mo (5-seat min)
G2 rating	-	4.8 (37 reviews)	4.7 (122 reviews)

ConfigCat’s strength: pricing that ignores your headcount

ConfigCat’s whole pitch is its pricing model, and it’s a genuine relief. It charges no per-seat and no per-MAU fees, and 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. The ladder is fully published: Forever Free at $0 (10 flags, 2 environments, 5M downloads), Pro at $110/mo, Smart at $325/mo, Enterprise at $900/mo. It’s bootstrapped and profitable out of Budapest, so there’s no VC-driven pricing pressure.

The gotcha hides inside that friendly model. Because pricing is gated on config downloads, 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 jumps are large - 5M to 25M to 250M downloads. The fix is real but requires attention: cache aggressively and use the SDK proxy to keep download volume down. Do that and the flat pricing stays flat.

Flagsmith’s strength: real open source, real self-host

Flagsmith does the one thing ConfigCat structurally can’t. It’s genuinely open source under BSD-3-Clause and genuinely self-hostable via Docker, Kubernetes, on-prem and air-gapped. The open-source build is a real product - flags, remote config, segmentation, basic A/B testing and 15+ SDKs - not a crippled teaser. And its pricing is the most transparent in the category, with every core tier published: Free at $0 (50,000 requests, unlimited flags), Start-Up at $40/mo annual (the cheapest paid entry here), Scale-Up at $250/mo annual. The billing unit is requests, which is clean to reason about - no MAU trap. It has the highest G2 rating in this set at 4.8, albeit from only 37 reviews, so read that as “small and loved.”

The gotcha is that “free and open source” hides a cost. Flagsmith is a Django and Postgres stack, and running it in production is real DevOps - container orchestration, a database, upgrades, scaling. Third-party comparisons call it “tricky to get right.” It’s also a roughly 12-person bootstrapped London team, so the ecosystem is smaller than the giants’. If you have DevOps capacity and want no lock-in, that’s a great trade. If you don’t, the paid cloud tiers - which are cheap anyway - are usually the better call.

The third option: Unleash, if self-hosting is the whole point

If you’re comparing these two because you specifically want to run flags in your own infrastructure, Unleash deserves a seat at the table. It’s AGPL-3.0, has an 11-year track record, roughly 13.7k GitHub stars, and a G2 of 4.7 across 122 reviews. The open-source edition is a capable product - flag management, activation strategies, gradual rollouts, kill switches, canary - runnable air-gapped.

But read the catch before you commit. RBAC, SSO/SAML, SCIM and extra environments are all gated to paid tiers, not in the free AGPL build. A recurring complaint is being surprised you can’t use SSO without a paywall. There’s also no read-only seat, so once PMs and QA need access, every one is a paid seat at $75/mo with a 5-seat minimum. Unleash is free if you can live inside the OSS feature set, and a real bill the moment you need enterprise access controls.

ConfigCat vs Flagsmith: which should you pick?

• You want zero infrastructure work and predictable flat pricing - ConfigCat. Hosted, no self-host burden, no MAU meter. Just watch your config-download volume.
• You want open source and no vendor lock-in - Flagsmith. BSD-3, self-hostable, and the code outlives the company. The trade is running a Django stack.
• You want the cheapest paid cloud tier - Flagsmith at $40/mo annual undercuts ConfigCat’s $110/mo Pro.
• You have millions of users but modest SDK traffic - ConfigCat, because unlimited MAUs on a flat tier is exactly what its model rewards.
• You need to self-host air-gapped for compliance - Flagsmith or Unleash. ConfigCat can’t do it at all.
• You need enterprise access control in your own infra - Unleash Enterprise, and price it before you commit, because SSO and RBAC aren’t in the free build.

The bottom line: ConfigCat and Flagsmith are both excellent, cheap, flags-first tools, and they rarely lose to each other on capability - they lose on fit. Pick ConfigCat if you want a hosted service with headcount-independent pricing and no ops. Pick Flagsmith if you want open source you can self-host with no lock-in and you have the DevOps capacity to run it. And if self-hosting in your own infra is the entire reason you’re reading this, put Unleash on the shortlist too.

---

Pricing verified against each vendor’s own site on 26 July 2026. Feature-flag pricing changes often - we re-verify regularly.