LaunchDarkly Pricing, Explained
LaunchDarkly does not have a price, it has two meters. Nearly every surprise bill traces back to not knowing which one is running. Figures below are from LaunchDarkly’s own pricing and billing docs, last verified 2026-06-23.
Worth knowing who wrote this: we're ShipSilently, a feature flag service that competes with LaunchDarkly. We've kept this page to things you can verify, with sources at the bottom, because a page that shades the facts is worth less to us than one you'd send to a colleague. Found something wrong or out of date? Tell us and we'll correct it.
Not affiliated with or endorsed by LaunchDarkly. LaunchDarkly is a trademark of its owner, used here to refer to their product. For official documentation see launchdarkly.com/docs.
The two meters
LaunchDarkly's paid pricing is usage-based, and the usage it measures splits along the client/server line:
- Service connections meter the server side, at roughly $12 per connection per month. This counts SDK connections, not applications, so a service running twelve pods is not one unit of anything.
- Client-side monthly active contexts (MAU) meter the browser and mobile side, at roughly $10 per 1,000. A "context" is LaunchDarkly's generalisation of a user: it can be a user, a device, an organisation, or a combination.
Seats are free on paid tiers. That sounds generous until you notice the meters are attached to the two numbers that grow when your product succeeds, which is the actual design of the pricing model.
The break-even, in one line. ShipSilently Pro stays $49/mo flat. LaunchDarkly Foundation passes $49/mo at roughly 4 service connections, or ~5,000 client-side MAU, so almost any production deployment with more than a couple of pods or a few thousand users is already paying more.
Tiers, and what each one actually gets you
Usage-based: billed per server-side service connection (~$12/connection/mo) plus per 1,000 client-side monthly active contexts (MAU). Seats are unlimited on paid tiers; experimentation is a separate add-on. Enterprise & Guardian are custom/contact-sales.
| Tier | Price | Includes |
|---|---|---|
| Developer (free) Evaluation tier with hard usage caps. | $0 free |
|
| Foundation Public, usage-metered tier, cost scales with infra + users. | $12 / connection + $10 / 1k MAU usage-based / mo |
|
| Enterprise Governance + release automation; median contract ~$72k/yr (Vendr). | Custom contact sales |
|
| Guardian Advanced progressive delivery on top of Enterprise. | Custom contact sales |
|
Two tiers are quote-only. If you need scheduled changes, approval workflows, SCIM or custom roles, you are in a sales conversation and the number is whatever that conversation produces, which is worth knowing before you build a rollout process that depends on approvals.
What it costs three real-shaped teams
Same three profiles we use on the comparison page, priced on Foundation rates. Experiments would add roughly $3 per 1,000 MAU on top of every row.
| Team | LaunchDarkly | ShipSilently |
|---|---|---|
| Tiny team, 3 engineers, one backend service, 50k MAU A handful of Kubernetes pods (≈8 service connections) and ~50,000 monthly active users on the client side. | ≈ 8 × $12 + 50 × $10 = $96 + $500 ≈ $596/mo on Foundation ≈12× cheaper on ShipSilently before any experimentation add-on. | $49/mo flat |
| Scaling SaaS, 8 engineers, microservices, 250k MAU Autoscaling microservices average ~30 service connections; 250,000 client-side MAU. | ≈ 30 × $12 + 250 × $10 = $360 + $2,500 ≈ $2,860/mo on Foundation The per-connection charge is the trap: each pod is billable, so autoscaling inflates the bill. | $49/mo flat |
| Enterprise renewal A team on a legacy plan being moved to current pricing, a widely reported pattern. | Vendr lists a median LaunchDarkly contract of ~$72k/yr (range ~$19.5k–$165.7k) Renewal shock, reported 10–20% step-ups and "doubling" off legacy plans, is the #1 reason teams evaluate alternatives. | Enterprise: custom, flat |
Want these numbers with your own pod count and MAU in them? The flag cost calculator does the arithmetic and shows its working.
Why the bill moves when you didn't touch anything
The per-connection meter is the one that surprises people, because Kubernetes is designed to change the number it measures. Scale a deployment from 6 pods to 30 during a traffic spike and you have, briefly, 30 service connections. Nobody made a purchasing decision. The autoscaler did.
The MAU meter is more intuitive but has the same property in slower motion: it grows with the thing your whole company is trying to grow. Budgeting against it means forecasting user growth accurately a year out, which nobody does.
Then there is renewal. Teams on older LaunchDarkly plans being moved onto current pricing is a widely reported pattern, and it is the single most common reason people land on pages like this one. One publicly documented case went from about $10k to about $45k a year.
Bringing it down, if you're staying
Most of this page is a competitor writing about a competitor, so here is the part that is useful whether or not you ever talk to us. Four things reliably move a LaunchDarkly bill:
- Put a Relay Proxy in front of your fleet. Instead of every pod holding its own connection, the proxy holds the connection and your services talk to it. This is the single biggest lever on the server-side meter, and it is also the reason the Relay Proxy exists.
- Audit what is actually client-side. Contexts evaluated server-side don't hit the MAU meter. Teams that started with a client-side SDK for convenience and never revisited it are often paying MAU rates for evaluations that could happen in their own backend.
- Delete dead flags. Flag debt doesn't bill directly, but stale flags keep services connected and contexts active for code paths nobody ships anymore. We wrote about the cleanup process in managing feature flag technical debt.
- Ask for the usage breakdown before renewal, not during. Going into a renewal knowing your own connection and MAU curves is worth more than any negotiating tactic, and you can pull both from the REST API yourself.
When LaunchDarkly is worth it
We are not going to pretend the answer is never. LaunchDarkly is the most mature product in this category and there are teams for whom the price is straightforwardly correct:
- Experimentation depth, the most mature stats engine in the category (CUPED variance reduction, sequential testing, SRM detection).
- Advanced progressive delivery, guarded rollouts with automatic rollback and failure detection (Guardian tier).
- Enterprise governance available today, SAML, SCIM, custom RBAC, scheduled changes and approval workflows.
- Compliance, annual SOC 2 Type II, ISO 27001 and a FedRAMP path.
- 25–30+ battle-tested SDKs across nearly every language and platform.
If two or more of those are what your shipping process runs on, pay them. The teams who should be looking hard at the bill are the ones running core flagging (booleans, percentage rollouts, a kill switch) on pricing built for a platform they don't use.
That second group is who we built ShipSilently for: you want predictable flat pricing that does not balloon with microservices or user growth, a flag tool that runs on any runtime, and a 5-minute setup. The full comparison shows both sides of it, including the parts where we come off worse.
FAQ
How much does LaunchDarkly cost?
There is a free Developer tier ($0, capped at 3 environments, 5 service connections and 1,000 client-side MAU). The entry paid tier, Foundation, is usage-based: roughly $12 per service connection per month plus roughly $10 per 1,000 client-side monthly active contexts. Enterprise and Guardian are quote-only; Vendr's marketplace data puts the median LaunchDarkly contract around $72,000/year, with a range of roughly $19,500 to $165,700.
What is a service connection in LaunchDarkly billing?
It is the unit LaunchDarkly meters server-side usage in, and it tracks SDK connections rather than applications. In practice each server-side SDK instance that connects (each pod, container, VM or Relay Proxy) counts toward it, which is why horizontally scaling a service raises the bill even though your user count is unchanged. Check their calculating-billing doc for the current definition before you model a budget on it.
Does LaunchDarkly charge per seat?
Not on the paid tiers. Seats, projects and environments are unlimited on Foundation and above. The metering happens on service connections and client-side MAU instead, so "unlimited seats" is true and also not where the money goes.
Is LaunchDarkly free?
The Developer tier is genuinely free and has no time limit, but its caps (3 environments, 5 service connections, 1,000 client-side MAU) are sized for evaluation rather than production. A single autoscaling deployment will pass 5 service connections on its own.
Why did my LaunchDarkly bill go up when nothing changed?
Usually one of three things: autoscaling added server-side SDK connections, client-side monthly active contexts grew with your user base, or a legacy plan was moved onto current pricing at renewal. The first two happen without anyone making a decision, which is what makes usage-based pricing hard to budget against.
Is experimentation included in LaunchDarkly pricing?
No, it is a paid add-on on top of the tier price, metered at roughly $3 per 1,000 MAU. Guarded rollouts and automatic rollback sit higher still, on the Guardian tier. If experimentation is why you are looking at LaunchDarkly, price it separately.
How does ShipSilently price against this?
Flat $49/month on Pro, with unlimited seats, no per-connection charge and no per-MAU charge. Pro includes 10M evaluations/month, overage at $0.01 per 10k. We also do not ship experimentation, SCIM or custom RBAC today, so the honest comparison is on our /compare/shipsilently-vs-launchdarkly/ page rather than in a pricing headline.
More on LaunchDarkly
A flag bill you can predict a year out
ShipSilently is $49/month flat: no per-connection meter, no per-MAU meter, unlimited seats. We are also younger and thinner than LaunchDarkly, no experimentation, no SCIM, no custom RBAC yet, and our comparison page lists every one of those gaps next to the places we win. If a missing piece is the thing standing in your way, email us, it genuinely shapes what we build next.
$49/month is the 2026 price. List goes to $89/month on January 1, 2027, and subscriptions started before December 31, 2026 stay at $49.
Sources
- LaunchDarkly pricing page: https://launchdarkly.com/pricing/
- LaunchDarkly billing definitions (service connections, MAU): https://launchdarkly.com/docs/home/account/calculating-billing
- LaunchDarkly Cloudflare edge SDK: https://launchdarkly.com/docs/sdk/edge/cloudflare
- LaunchDarkly SAML / SCIM (Enterprise gating): https://launchdarkly.com/docs/home/account/sso
- Vendr, LaunchDarkly contract medians & ranges: https://www.vendr.com/marketplace/launchdarkly
- Tier contents, per-unit rates and contract medians above are the same dataset that powers our LaunchDarkly comparison, re-verified quarterly. Last verified 2026-06-23. LaunchDarkly's pricing page blocks automated crawlers, so list rates are corroborated across their billing documentation, Vendr marketplace data and public pricing write-ups.
Checked against the linked sources on 2026-06-23. LaunchDarkly changes its docs and pricing without notice, so treat their pages as authoritative over ours and email us when we drift.