Two feature flag tools can advertise almost the same headline number and bill you wildly differently a year later. The reason is the pricing model, not the sticker. One tool charges a flat monthly fee. The next charges per engineer who can edit a flag. The third charges per evaluation, per monthly active user, or per API request. Same job, three meters, and the meter you pick decides whether the bill stays still or climbs every time you hire someone or get more traffic.
This is a guide to those models. It explains how flat, per-seat, and usage-based feature flag pricing actually work, why per-seat is the one that quietly punishes growing teams, where “free” open source hides its real cost, and what a single mid-size team would pay across six real vendors. Every price below is each vendor’s published list pricing as of June 2026; pricing pages change, so treat the figures as a snapshot and check the live page before you commit.
Key Takeaways
- Feature flag pricing comes in three meters: flat (a fixed monthly fee), per-seat (a fee for every editor), and usage-based (a fee per evaluation, MAU, or API request). The meter, not the headline price, decides how the bill behaves as you grow.
- Per-seat is the model that scales against you on team size. At $40 to $75 per seat, a team of 8 pays 8 times the list price, and the bill grows with every hire whether or not the new engineer touches a flag.
- Usage-based pricing tracks traffic, not headcount, so it starts cheap and gets unpredictable: a successful launch that triples client-side traffic also triples the flag bill.
- Flat pricing is the only model where the plan number is the bill. It is the wedge Featureflip is built on: $0 / $49 / $149 per month with no per-seat or per-MAU charges, the same bill whether you have one engineer or twenty-five.
- “Free” open source is a real option, but the license fee is the small number. You pay in hosting, upgrades, and on-call instead.
1. The three ways feature flag tools charge you
Strip away the marketing and every feature flag tool meters you one of three ways, sometimes two at once.
Flat (subscription). You pay a fixed monthly or annual fee for a tier. The tier caps something (projects, flags, environments, retention), but within those caps the number on the invoice does not move. Featureflip and ConfigCat sit here. Adding engineers or traffic does not change the bill until you outgrow a capacity limit and step up a tier.
Per-seat. You pay for every user, or every editor, who can touch a flag. The headline looks small ($40 to $75 per seat per month is the going rate), but the invoice is headcount times that number. GrowthBook Cloud, Unleash, and Flagsmith all meter seats in some form. This is the model that turns a hiring win into a line-item increase.
Usage-based. You pay for what the system does: evaluations, monthly active users (MAU), or API requests. LaunchDarkly bills per service connection plus per client-side MAU; PostHog bills per flag request. The bill is decoupled from your team and coupled to your traffic, which is great at zero and tense at scale.
A fourth path, open-source self-hosting, looks free because the license fee is zero. It is a real choice, covered in section 5, but the cost moves from an invoice to your infrastructure and your on-call rotation rather than disappearing.
The rest of this guide takes the three metered models one at a time, then runs one team’s numbers through all of them.
2. Per-seat pricing: the tax on adding engineers
Per-seat is the most common model in the category and the one most likely to surprise you, because the unit price is designed to look reasonable in isolation. Forty dollars a seat sounds fine. The catch is that the thing being multiplied (your team) is the thing you are actively trying to grow.
Walk a single team up the seat count. GrowthBook Cloud Pro is $40 per editor per month. One editor is $40. Five is $200. Ten is $400. Twenty-five is $1,000 a month, $12,000 a year, for the same product the first editor used. Unleash’s cloud Pay-As-You-Go plan is steeper at $75 per seat per month with a five-seat minimum, so eight engineers is $600 a month and twenty-five is $1,875 a month, $22,500 a year at list. Flagsmith bundles a few seats into each tier and then charges roughly $50 to $60 for each additional seat, which produces the same upward slope once your team passes the bundled count. None of these is hidden. They are all on the pricing pages. The point is that the slope is the product of a number you control downward (price per seat) and a number you are pushing upward (engineers), and the second number wins over time.
There is a softer version of the problem too. Per-seat pricing pushes teams to ration access, because every additional login costs money. So the product manager who wants to flip a flag during a launch, or the support lead who needs to read targeting rules, gets left off the license to control spend. Flags work best when the people closest to a release can operate them, and a meter that taxes each of those people works against that. The honest defense of per-seat is that GrowthBook bills per editor, not per viewer, so read-only access can be free, which softens the rationing problem if your tool draws that line. But for the engineers who actually ship behind flags, the seat is unavoidable, and that is the population that grows.
3. Usage-based pricing: the bill that moves with your traffic
Usage-based pricing swaps the headcount meter for a traffic meter. Instead of paying per engineer, you pay per unit of work the flag system does: an evaluation, a monthly active user, or an API request. It is the model with the friendliest on-ramp and the least predictable cruise.
LaunchDarkly’s Foundation plan is the textbook case. It bills $12 per service connection per month plus $10 per 1,000 client-side monthly active users per month, with experimentation MAU metered separately on top. PostHog meters flags by the request: the first million requests a month are free, then it is $0.0001 per request from one to two million, sliding down to $0.00001 per request above fifty million, a curve the Featureflip and PostHog cost comparison walks through against a flat plan. Both pricing pages reward you for being small. A side project pays nothing. A pre-launch app pays close to nothing. The meter only becomes a budgeting problem when the product works, which is the point at which teams tend to start weighing the flat-rate alternatives to LaunchDarkly.
That is the structural tension. The success case and the expensive case are the same event. A feature you launch behind a flag, that then drives a traffic spike, raises the flag bill at exactly the moment the flag did its job. With per-seat you can at least forecast cost from a hiring plan. With usage-based the input is your own growth curve, which is the number you are least able to predict and least want to suppress. Usage pricing also tends to interact badly with client-side evaluation, where every browser or device that checks a flag is a billable event; server-side local evaluation, where flags are checked in-process against a cached ruleset, usually sidesteps per-check billing, which is why the same vendor can be cheap for one architecture and expensive for another.
Usage-based is not a trap, to be clear. For a genuinely small or server-side-heavy workload it can be the cheapest option on the board, sometimes literally free. It just trades a predictable bill for a cheap-when-small one, and you should know which of those two properties you are actually buying.
4. Feature flag flat pricing: the plan number is the bill
Flat pricing is the model where the invoice holds still. You choose a tier, the tier sets some capacity ceilings, and inside those ceilings nothing you do to your team size or your traffic changes the number. There is no per-seat multiplier and no per-evaluation meter, so the only way the bill moves is when you deliberately step up a tier for more capacity.
This is the feature flag flat pricing wedge, and it is a real gap in the market: flat, predictable billing is the thing growing teams want, and the big platforms mostly do not offer it because per-seat and per-usage meters earn them more as you scale. Featureflip is built on this model: the Solo plan is $0 a month forever, Pro is $49 a month ($39 billed annually), and Business is $149 a month ($119 annually), with no per-seat fees, no per-MAU fees, and unlimited evaluations on every plan. Ten engineers cost the same as one. A traffic spike costs nothing extra. The plan number is the bill.
ConfigCat is the other major vendor in the flat camp, and including it keeps this honest: flat pricing is not unique to one tool. ConfigCat’s tiers ($0 Free, $110 Pro, $325 Smart, and up) are flat per month with unlimited seats, which is genuinely attractive for a team that wants headcount off the meter. The difference is where the ceilings sit. ConfigCat gates hard on product count and flag count (its Pro tier caps at 3 products and 100 flags), so a multi-app team can be pushed up a tier by hitting a capacity limit rather than by growth in users or traffic. Flat pricing does not mean no limits; it means the limits are capacity ceilings you can see in advance, not a meter that ticks in the background. Teams that bump into those product or flag ceilings often start weighing the flat-rate ConfigCat alternatives at that point.
The catch worth naming on flat pricing is the reverse of usage-based: a very small or very low-traffic team can occasionally pay more on a flat plan than it would on a metered one that bills near zero at low volume. Flat pricing optimizes for predictability, not for being the rock-bottom cheapest at tiny scale. If you are below a metered tool’s free ceiling and expect to stay there, usage-based can win. The flat-pricing argument is for everyone who plans to grow and would rather not re-forecast the flag bill every quarter.
5. “Free” open source isn’t free: the self-host model
There is a fourth option that does not fit the three meters: run an open-source flag system yourself. Unleash (AGPL-3.0), Flagsmith (BSD-3-Clause community edition), and GrowthBook (MIT core) all ship a self-hostable version with a license fee of exactly zero. For a team with a platform function and a preference for owning infrastructure, this is a legitimate and sometimes correct choice. Teams that adopted Flagsmith’s community edition and later found the operational tax too high tend to shop the hosted Flagsmith alternatives once those staff hours start to bite.
It is just not free, and the pricing-model framing makes the trade visible. The license is the small number. The real cost moves off the invoice and onto your team: you run the database, you run the upgrades, you run the proxy or edge layer some of these need for streaming, and you own the on-call when flag delivery breaks at 2 a.m. There are usually feature ceilings on the free edition too. Unleash’s open-source tier limits you to one project and two environments and reserves SSO, custom roles, and SSE streaming for Enterprise; GrowthBook self-host wants you to operate its proxy and ideally a data warehouse. The decision here is the same one covered in the build vs buy feature flags framework: if feature management is not your product, the engineering hours you spend operating a flag platform are hours not spent on what your customers pay for. Self-hosting is buying with labor instead of dollars, and labor is rarely the cheaper currency once you price it honestly.
6. A real cost comparison: one team, six vendors
Models are easier to judge against one concrete team. Take a mid-size SaaS app: 8 engineers shipping behind flags, around 50,000 client-side monthly active users, and a handful of backend services. Here is roughly what each vendor’s published list pricing produces for that single profile per year. The figures come straight from each vendor’s pricing page as of June 2026 and from the worked examples on our own comparison pages.
A few honesty notes, because a pricing comparison is worthless if it quietly stacks the deck. The numbers are not strictly apples-to-apples, because the models meter different things. GrowthBook’s figure assumes all 8 engineers need editor seats at $40 each; if half of them are read-only, it drops. PostHog’s figure is driven by flag requests, not MAU, so it swings hard on how chatty your client-side flag checks are, and a server-side-heavy setup could land near zero. LaunchDarkly’s figure is the Foundation per-MAU and per-connection math before any experimentation usage. Unleash’s is the cloud Pay-As-You-Go list rate, which an Enterprise contract would renegotiate. The per-vendor breakdowns, with the exact arithmetic, live on the individual comparison pages: LaunchDarkly, Flagsmith, ConfigCat, Unleash, GrowthBook, and PostHog. What survives all the caveats is the shape: flat pricing clusters at the bottom and stays there, while per-seat and usage-based climb with the two things you are trying to grow.
7. How to choose a model that won’t surprise you
The right model is the one whose meter is attached to something you are not trying to maximize. Run your situation through three questions in order.
Is your team going to grow? If you plan to add engineers, per-seat is the model most likely to outrun your budget, because the meter is the headcount you are deliberately increasing. A growing team is the strongest case for flat pricing, where adding people is free.
Is your client-side traffic going to grow, and is it unpredictable? If yes, usage-based pricing converts your success into a variable bill you cannot easily forecast. If your usage is genuinely small or mostly server-side, the same model can be the cheapest thing available, sometimes free. Match the meter to whether your traffic is steady and small or spiky and large.
Do you want the bill to be a fixed line you can forecast a year out? If predictability is the priority, flat pricing is the only model that delivers it, and the question becomes whether a given vendor’s capacity ceilings fit your project and flag counts. Read the tier limits, not just the price.
The cross-cutting rule underneath all three: read what the meter is attached to, then ask whether that thing moves in the direction you are pushing your business. A flag tool should get cheaper to operate as you succeed, or at least hold steady. A meter bolted to your headcount or your traffic does the opposite.
The shorter version
Feature flag pricing comes in three meters and a fourth path. Flat pricing fixes the bill to a tier and lets your team and traffic grow underneath it for free, which is why it is the wedge newcomers compete on and the model Featureflip is built around ($0 / $49 / $149 a month, no per-seat or per-MAU charges). Per-seat pricing ($40 to $75 a seat at GrowthBook, Unleash, and Flagsmith) looks cheap per unit but multiplies by the headcount you are trying to grow, so it scales against you. Usage-based pricing (LaunchDarkly’s per-MAU, PostHog’s per-request) starts cheap and turns your own success into an unpredictable bill. Open-source self-hosting is zero in license and real in operational cost. For one 8-engineer team, the flat tools landed near $468 to $1,320 a year while the per-seat and usage-based tools stacked up to $3,840 to $7,200 for the same work. Pick the model whose meter is attached to something you are not actively trying to increase.
Frequently asked questions
What is flat feature flag pricing?
Flat feature flag pricing is a fixed monthly or annual fee for a tier, with no per-seat or per-evaluation meter on top. Within the tier’s capacity ceilings (projects, flags, environments), the bill does not change when you add engineers or get more traffic. Featureflip uses this model ($0 Solo, $49 Pro, $149 Business per month, unlimited evaluations), as does ConfigCat. It is the model that keeps the invoice predictable as a team grows, which is why teams that expect to scale headcount or traffic tend to reach for flat pricing over a per-seat or per-usage meter.
Why is per-seat feature flag pricing more expensive as you grow?
Because the bill is the per-seat price multiplied by your team size, and team size is something you are actively trying to increase. At $40 per editor (GrowthBook) or $75 per seat (Unleash), one engineer is cheap but ten engineers is ten times that, and twenty-five is twenty-five times. The unit price stays small while the multiplier climbs, so per-seat pricing scales against a growing engineering org. It can also push teams to ration flag access to control spend, which works against letting the people closest to a release operate it.
Is usage-based feature flag pricing cheaper than flat pricing?
It depends on your traffic. Usage-based pricing (per evaluation, per MAU, or per API request) bills near zero at low volume, so for a small or server-side-heavy workload it can be the cheapest option, sometimes free. The trade is predictability: the bill rises with client-side traffic, so a successful launch increases your flag cost at the same time. Flat pricing costs more at tiny scale but stays fixed as you grow. Choose usage-based if your volume is small and likely to stay small; choose flat if you expect to grow and want a forecastable bill.
How much does a feature flag tool cost per year?
For one mid-size team (8 engineers, around 50,000 client-side MAU) on list pricing as of June 2026, the range is wide because the models differ. Flat-priced tools landed lowest: roughly $468 a year for Featureflip Pro and about $1,320 for ConfigCat Pro. Per-seat tools ran higher: about $3,840 for GrowthBook, $4,800 for Flagsmith, and $7,200 for Unleash cloud. Usage-based tools depend on traffic but reached roughly $5,520 for PostHog and $6,864 for LaunchDarkly Foundation at that profile. The same team, the same job, an order-of-magnitude spread driven entirely by the pricing model.
Is open-source feature flagging actually free?
The license is free; the system is not. Unleash, Flagsmith, and GrowthBook all offer self-hostable open-source editions with no license fee, but you take on hosting, database operation, upgrades, any proxy or edge layer they need, and the on-call when flag delivery fails. There are usually feature ceilings on the free edition too (Unleash limits open source to one project and two environments, with SSO and streaming reserved for Enterprise). Self-hosting trades a subscription for engineering labor, which is the right call when you have a platform team and feature management is core to your product, and the wrong call when those hours would be better spent on what your customers pay for.
If you are mid-evaluation, the comparison pages break down each vendor’s pricing and features side by side, and the build vs buy decision framework covers the case where the real alternative is a homegrown system rather than another vendor.
Featureflip is the focused, flat-priced answer this guide points toward: $0 / $49 / $149 a month with no per-seat fees, no per-MAU charges, and unlimited evaluations on every plan, so the bill stays still while your team and traffic grow. The pricing page has the full numbers, and you can start on the free Solo plan without a credit card.