Betterflag
Back to blog

Why LaunchDarkly Bills You for Your Architecture

LaunchDarkly service connections and client-side MAUs price your topology and your success, not your flag usage. Worked math for 25k and 100k MAU, and the one-meter alternative.

Mehdi
August 23, 2026
#launchdarkly#pricing#feature-flags#comparison

LaunchDarkly does not charge you for feature flags. It charges you for how you built the app and whether the app worked.

That sentence sounds like a dunk. It is just their pricing page. Two meters, billed separately:

  1. Service connections. Each SDK context that connects, at about $10 per connection per month on Foundation (list, mid-2026). A connection is roughly one service × one environment.
  2. Client-side MAUs. $8.33 to $10 per 1,000 monthly active users who hit a client-side SDK, cheaper on annual.

Seats are unlimited on current LaunchDarkly tiers, including free. If you still think the fight is a seat tax, you are arguing with 2023. I was, for a while. The live hook is this: you are billed for your architecture, and then billed again for getting users.

I am building Betterflag, a flags-only alternative with one meter (evaluations). Discount accordingly. Numbers below are list prices as of July 2026. Check launchdarkly.com/pricing before you commit. The long table is Betterflag vs LaunchDarkly.

What a service connection actually is

If you have:

  • 5 backend services
  • a web app
  • a worker
  • staging and production

you are looking at something like 7 runtimes × 2 environments = 14 connections, before preview apps, before that extra cron, before someone adds a second region.

Kubernetes and serverless make this worse on purpose. Autoscaling is more connections. A lambda per function is more connections. Preview environments for every PR are more connections. None of that made your flags more valuable. It made your topology more fashionable.

The vendor has a fair point: persistent streaming connections cost money. The argument is not "connections should be free." It is that $10 as the multiplier, and punishing ephemeral architectures, prices the wrong thing. A boolean lookup's cost-to-serve tracks evaluations, not pod count.

The MAU line is the one that grows forever

Client-side MAUs bill your success. 25,000 users at $10 / 1,000 is $250/mo, on top of connections. 100,000 users is $833–$1,000/mo in MAUs alone.

You did not add flags. You got featured. The bill went up.

Server-side evaluation can dodge some of this, at the cost of putting flag logic only on the server. Plenty of teams then discover their mobile app or marketing site is the expensive part.

Worked math (please steal this table)

We plan using ~200 flag evaluations per MAU per month. That is a planning number, not a law. Cache more, pay less. Evaluate in a render loop, pay more. Put the conversion next to every quote so nobody can accuse you of picking a convenient tier.

Shape A: 10-person startup, 25k MAU, 5 services, staging + prod

| | LaunchDarkly Foundation (monthly) | Betterflag | |---|---|---| | Connections | 5 × $10 = $50 (web + mobile often extra) | $0 | | MAUs | 25 × $10 = $250 | $0 | | Evaluations (~5M) | included in the above | $24.99 Launch (5M included) | | Total | ~$300/mo | $24.99/mo |

Shape B: same app, 100k MAU, ~20M evaluations

| | LaunchDarkly | Betterflag | |---|---|---| | MAUs | 100 × $8.33 to $10 = $833–$1,000 | $0 | | Connections | still there | $0 | | Evaluations | n/a | $84.99 Launch + 15M overage | | Total | ~$900–$1,100+ / mo | $84.99/mo |

That is the 10x line. Quoting Betterflag Launch at $24.99 (5M included) against a 100k-MAU app would be a lie. 20M evaluations is Launch plus overage, or Scale if you want 50M included. Honest comparisons survive a spreadsheet.

What LaunchDarkly is still the right buy for

A platform team, multivariate experiments, change management, a procurement process, 500 engineers. They built that product on purpose. If that is you, stay. You are not the customer a $9.99 flags-only tool is for.

If you are 2 to 50 people, you use four primitives (on/off, percentage, a little targeting, a kill switch), and your bill jumped because you split a monolith or shipped iOS, you are paying for a graph that is not the product.

Plug your numbers in. Connections times $10, plus MAU, versus evaluations.

Your shape

LaunchDarkly Foundation

$370.00/mo

  • 12 connections × $10 = $120.00
  • 25,000 MAU × $10 / 1k = $250.00

Betterflag Launch

$24.99/mo

  • 5,000,000 evaluations
  • 5,000,000 included, no overage

Same shape on Betterflag is $345.01/mo less, about 15× cheaper on this input. Connections and MAUs do not appear on the Betterflag bill.

LaunchDarkly list prices as of July 2026. Service connections ≈ each SDK instance × each environment. Betterflag overage is rounded up to the next 1M evaluations. Always verify against their pricing page.

Open full calculator

One meter

Betterflag charges evaluations. Unlimited flags, seats, environments. Starter $9.99/mo (1M), Launch $24.99 (5M), Scale $99.99 (50M). Overage is published. Agents do not create connections. Preview apps do not create line items.

The rest of the 2026 landscape, with the same honesty about when they win: feature flag pricing compared.

If you want a second reason people leave, it is not the meter. It is that the audit log and approvals sit on Enterprise. The safety mechanism, upsold.

Alpha waitlist members lock in 50% off for life. Join if the architecture bill is the thing you are tired of explaining to finance.

FAQ

What is a LaunchDarkly service connection?
A service connection is roughly one SDK instance per environment: each backend service, worker, or client application that connects to LaunchDarkly, in each environment. A modest setup (5 services × 2 environments) is already 10 connections. On Foundation, connections are billed around $10 each per month, on top of MAU charges.
How do LaunchDarkly service connections affect serverless and Kubernetes?
Ephemeral and autoscaled architectures create more connections for the same product. More pods, more lambdas, more preview environments: the flag bill grows even if user-facing flag usage does not. You are billed for topology, not for the boolean.
How much is LaunchDarkly for 100k MAU?
Client-side MAUs at $8.33 to $10 per 1,000 are $833 to $1,000 per month before service connections. If those users produce ~20M flag evaluations, the cheapest Betterflag bill is Launch plus overage at $84.99/mo, not the $24.99 included price. Always convert MAU to evaluations before comparing tiers.
Is LaunchDarkly's free tier actually free?
The Developer plan is generous on paper: unlimited seats and flags, an MCP server, many SDKs. It is sized as an on-ramp. Real traffic and a real service graph put you on Foundation meters: connections plus MAUs. Read the paid columns, not only the free card.