ConfigCat Pricing, Decoded - The No-MAU Model and the Trap Hiding In It (2026)

Almost every feature-flag tool bills you on monthly active users, seats, or both. ConfigCat does neither, and that’s the entire reason to read a pricing decode about it. MAUs, contexts and flag reads are unlimited on every tier, including Free. You are never taxed for adding a user or for how often your app checks a flag. For anyone burned by an MAU bill, that’s a genuine relief.

But the friendly model has one trap in it, and if you don’t see it coming it quietly moves you up the ladder. This is a neutral walkthrough: what ConfigCat actually bills on, the full ladder, how to estimate your bill, the trap, and cheaper picks. Every figure is from our ConfigCat review.

What ConfigCat bills on

Two things it does not charge for: seats and MAUs. No per-seat fee, no per-MAU fee, unlimited on every tier. What you pay for instead is config-download volume and caps - the number of flags, environments and products you can create, plus how much config-download traffic your SDKs generate.

So the meter is traffic, not people. A consumer app with millions of users pays the same as a small internal tool, as long as their download volume and flag counts sit in the same tier. That’s the flip that makes ConfigCat unusual.

ConfigCat is bootstrapped and unfunded, founded in 2018 in Budapest, roughly 14 people. No VC means no venture-driven pressure on the pricing, and it shows.

The pricing ladder

Here’s the full ladder. Every tier has unlimited MAUs, contexts and flag reads.

Tier	Monthly	Key limits
Forever Free	$0	10 flags, 2 environments, 2 products, 5M downloads/mo, 20 GB
Pro	$110	100 flags, 3 environments, 3 products, 25M downloads/mo, 100 GB
Smart	$325	Unlimited flags and environments, 250M downloads/mo, 1 TB
Enterprise	$900	Unlimited, 1B downloads/mo, 4 TB
Dedicated	$4,500	Unlimited, 6B+ downloads/mo, 24 TB

The Forever Free tier is genuinely generous and needs no credit card. Annual billing is offered, but there’s no published discount figure, so treat monthly-times-twelve as the reference, not a saving.

The trap: traffic-driven tier jumps

Here’s the catch hiding inside the friendly model. Because pricing is gated on config downloads and traffic, your bill is driven by how often your SDKs poll, not by how many users you have. A chatty SDK can push you across a tier without adding a single user.

Watch the jumps. Free caps at 5M downloads, Pro at 25M, Smart at 250M - those are 5x and 10x steps. An app with many SDK instances polling on a short interval can blow through the 5M cap and land on the $110 Pro plan, then keep climbing toward $325 Smart, purely on request volume. The fix is real but requires attention: cache aggressively and use the SDK proxy to cut download volume. Do that and flat stays flat. Ignore it and traffic quietly moves you up.

How to estimate your own bill

The sequence is refreshingly short, because you can ignore the two things that dominate other tools’ bills:

1. Ignore your user count and seat count. Both are unlimited and free. Add every teammate, target every user - it doesn’t move the bill.
2. Count your flags, environments and products. 10 flags fits Free. Up to 100 flags needs Pro. Unlimited flags needs Smart or above.
3. Estimate your monthly config downloads. This is the meter that moves. Multiply your number of SDK instances by their polling frequency across the month. This is where teams under-count.
4. Match to the tier that fits both caps. You need the tier that covers your flag count and your download volume, whichever pushes you higher.
5. Then cut your downloads. Before you accept the tier, cache and proxy your SDK polling - you may drop a tier just by being less chatty.

The output is a predictable monthly number, as long as you keep the download meter under control.

Cheaper alternatives, and when they win

ConfigCat is already one of the cheapest predictable options. But depending on what you need, two other tools change the calculation:

• Flagsmith - if you want open source and an even cheaper paid entry. It bills on requests, not MAU, and it’s genuinely self-hostable under BSD-3-Clause. The free tier is 50,000 requests a month with unlimited flags; paid Start-Up is $40/mo on annual billing for 1M requests - the cheapest paid entry in the category, below ConfigCat’s $110 Pro. Self-host the OSS build and the software is free outright, paid for in DevOps time on a Django and Postgres stack. Pick this if you want no lock-in.
• LaunchDarkly - only if you need the depth ConfigCat lacks. It’s the opposite trade: far deeper targeting, governance, guarded releases and real experimentation, but it bills on client-side MAU on your highest-volume context kind, and Vendr’s contract data puts the median around $72,000 a year. You’d move to it for capability, not to save money. If simple flags at a predictable price is the goal, ConfigCat wins this outright.

The bottom line on ConfigCat pricing: the no-seat, no-MAU model is a real differentiator and a relief for teams tired of usage-based surprises. Just remember the meter that does move is config downloads. Count your flags, estimate your download volume, cache well, and it stays as cheap and predictable as it looks.

---

Pricing verified against configcat.com on 26 July 2026. Feature-flag pricing changes often - we re-verify regularly. LaunchDarkly contract figures ($72,000 median) are from Vendr’s third-party buyer data and attributed as such.