LaunchFlag

Free tool

LaunchDarkly pricing calculator

LaunchDarkly has no per-seat price and no flat monthly number. It meters two different things, client-side MAU and service connections, and which one bills you depends on where your flags run. Enter your usage and this shows the estimate, the arithmetic, and whether the free Developer tier already covers you.

Unique context keys seen by browser, mobile, edge or AI SDKs. Zero if your flags only run on a server.

Running processes with a server SDK: replicas, workers, lambdas that stay warm. Zero if you have none.

Production, staging, dev. Each instance times each environment is one service connection.

AgentControl only. Leave at zero if you are not using it.

Rates checked 8 September 2026. Pro rata per 1,000; if LaunchDarkly bills whole blocks, round each line up.

Foundation tier, estimated

$83.30per month

Or $74.97 if Foundation keeps the first 1,000 MAU free the way Developer does. Their pricing page does not say which, so ask them before you budget. Billed yearly, so roughly $999.60 a year (or $899.64).

Client-side MAU10,000 ÷ 1,000 × $8.33, or $74.97 if the first 1,000 are included
$83.30
Service connections2 instances × 2 environments = 4, within the 5 included
$0.00
AI runs0 of 5,000 included
$0.00

The MAU meter is the bill. It counts unique context keys, not people, so anonymous visitors with a fresh id per session inflate it.

Same usage on LaunchFlag

$12 a month on Pro or $29 on Launch, flat. No MAU meter and no connection meter, because flags are evaluated inside your own process and traffic never reaches us. Free is $0 for one person and one project. What you give up is the platform: no experimentation, session replay, approvals, scheduling or SCIM. LaunchFlag pricing.

How the two meters work

Client-side MAU meters people. Browser, mobile, edge and AI SDKs report every unique context key they evaluate, deduplicated over a calendar month. A consumer app pays here. The trap is that the key is the identity: a logged-out visitor with a fresh id per session is a new MAU every session.

Service connections meter processes. One instance of one server-side SDK connected to one environment is one connection, so the number is instances times environments and never depends on traffic. A backend service pays here, and autoscaling or adding a staging environment is what moves it.

Five connections, 1,000 client-side MAU and 5,000 AI runs are included free. Under all three you are on Developer and pay nothing. Over any one you are on Foundation, which is pay-as-you-go and billed yearly. The longer explanation, with worked examples, is in LaunchDarkly pricing explained.

Where this estimate can be wrong

Two things the public page does not settle. First, whether Foundation keeps the first 1,000 MAU free once you upgrade; the calculator shows both readings when they differ. Second, how concurrency is sampled for short-lived instances, which decides what a fleet of lambdas counts as. Both are worth an email to LaunchDarkly before you commit to a number. Prices are US dollars and move without notice.

Questions

How is LaunchDarkly pricing calculated?
On usage, never on seats. The free Developer tier includes unlimited flags, unlimited seats, 5 service connections and 1,000 client-side MAU a month. Past that, Foundation is pay-as-you-go, billed yearly: $8.33 a month per 1,000 client-side MAU, $10 a month per service connection beyond the included five, and $5 per 1,000 AI runs beyond the included 5,000. Enterprise is custom quoted. Figures checked against launchdarkly.com/pricing on 8 September 2026.
What counts as a client-side MAU?
LaunchDarkly's billing docs define it as the number of unique monthly active contexts evaluated by client-side, AI and edge SDKs, deduplicated by context key over a calendar month. Server-side SDK evaluations do not count. Changing a context key mints a new MAU, so anonymous visitors with a fresh id per session can push the number well past your real user count.
What is a service connection?
One instance of one server-side SDK connected to one LaunchDarkly environment. Count running instances and multiply by the environments they connect to: one service on three replicas talking to production and staging is six connections. Five are included on Developer and Foundation, and each additional one is $10 a month.
Does Foundation include the first 1,000 MAU for free?
LaunchDarkly's public pricing page does not say. Developer includes 1,000 client-side MAU, and Foundation lists a per-1,000 rate, but whether the first thousand stay free once you upgrade is not stated. This calculator shows both readings whenever they differ. If you are near the boundary, ask LaunchDarkly before you budget.
How does LaunchFlag pricing compare?
LaunchFlag is flat: Pro is $12 a month and Launch is $29 a month, per account, with no MAU meter, no connection meter and no per-seat charge, because flags are evaluated inside your own process. The trade is scope. LaunchFlag is a switch with environments and an audit log; it has no experimentation, session replay, approvals, scheduling or SCIM. If you need those, LaunchDarkly is the right tool and the meter is the price of it.

Not affiliated with LaunchDarkly

This is an independent, unofficial calculator built by LaunchFlag, who make a competing product. We are not affiliated with, endorsed by, or sponsored by LaunchDarkly, and LaunchDarkly is their trademark, not ours. Every figure here is read from their public pricing page and billing documentation on the date below, and usage pricing changes without notice, so this is an estimate and not a quote. For a number you can rely on, use their official pricing page.

Sources

Rates and tier contents from launchdarkly.com/pricing, checked 8 September 2026. MAU and service connection definitions from LaunchDarkly's billing documentation, checked the same day. LaunchFlag prices are on our pricing page, and the fair-comparison version of this is LaunchDarkly alternatives.

Back to LaunchFlag