LaunchDarkly pricing explained: what you actually pay at different scales

LaunchDarkly doesn’t publish a simple price. They publish a meter. What you actually pay depends on usage that’s hard to predict and tends to grow with your product’s success: Monthly Active Users and service connections.

LaunchDarkly reworked its pricing recently — the old per-seat plans are gone, and every tier now includes unlimited seats. That’s a genuine improvement. But the part that catches teams out didn’t go away; it just became the whole model. This post breaks down how the usage meters compound and what teams typically find when they first look at the actual bill.

The meter

LaunchDarkly’s Foundation tier charges on usage:

Per MAU — Monthly Active Users, metered by how many unique contexts your client-side and edge SDKs encounter in a given month. The rate is roughly $8.33 per 1,000 client-side MAU.

Per service connection — your server-side connections, at roughly $10 per connection per month.

Foundation is billed annually, and above it sit Enterprise and Guardian on custom, sales-negotiated pricing.

Most teams hit the MAU meter long before they expect to. If you have a B2C product or a high-traffic API, your MAU count reflects your user base — not your team size. And unlike the old per-seat model, there’s no longer a fixed component you can plan around; the bill moves with traffic.

What it costs at real scale

Let’s price out a few common scenarios. These are estimates based on publicly available LaunchDarkly pricing; actual contracts vary.

50K MAU, ~5 services (Series A startup)

• MAU: 50 × $8.33 = ~$416/month
• Service connections: 5 × $10 = ~$50/month
• Estimated total: ~$466/month

200K MAU, ~10 services (growth-stage)

• MAU: 200 × $8.33 = ~$1,666/month
• Service connections: 10 × $10 = ~$100/month
• Estimated total: ~$1,766/month

500K MAU, ~15 services (scaling)

• MAU: 500 × $8.33 = ~$4,165/month
• Service connections: 15 × $10 = ~$150/month
• Estimated total: ~$4,315/month

The service-connection line is a rounding error. The MAU line is the bill — and it scales directly with your product’s success.

The renewal problem

Most LaunchDarkly customers on Enterprise are on annual contracts. You negotiate at your current scale, agree on usage tiers, and then your product grows. Twelve months later, you’re past your committed usage and the renewal negotiation starts from a higher baseline.

This is what teams mean by “renewal shock.” The number you agreed to last year no longer reflects the number you’re actually running at, and the vendor knows your migration cost is high.

Why MAU-based pricing exists

It’s worth understanding the model before you dismiss it. LaunchDarkly and older platforms were built when flag evaluation happened server-side — a request to their API for every flag check. At that architecture, MAU was a real proxy for compute cost. They served traffic; they charged for it.

Modern SDKs work differently. The SDK downloads your ruleset once and evaluates flags locally, in your app’s memory. No API call at evaluation time. The vendor’s infrastructure isn’t involved. The MAU meter is measuring something that no longer reflects the vendor’s actual cost structure.

LaunchDarkly still uses this pricing model. You can draw your own conclusions about why.

What teams tend to underestimate

MAU is hard to predict. If you’re a B2C product, a successful marketing campaign can double your MAU in a month. Your flag bill follows. The team that should be celebrating ends up reconciling an invoice.

The overage notifications come late. By the time you get a usage alert, you’ve already used the MAU. You’re not controlling spend in real time — you’re negotiating after the fact.

Governance lives on Enterprise. Audit logs, approval workflows, custom roles, and SCIM are Enterprise-tier features. So the controls your security reviewer asks for don’t come with the self-serve Foundation plan — they come bundled with the most expensive contract and a sales call. See why audit history belongs on every plan, not just the top one.

The alternative model

Flaggy charges $99/month flat for the Team plan. Unlimited seats. No MAU metering. No per-connection fees. The price doesn’t change whether you have 10K MAU or 10M.

This is possible because Flaggy also evaluates flags client-side. We never see individual evaluations. Our infrastructure costs are driven by the number of flag rules we store and sync — not by your user count. So there’s nothing to meter.

The tradeoff: Flaggy is a focused flag management platform. It’s boolean flags, segments, targeting, audit, and analytics — not multivariate experimentation at scale or a bundled session-replay/analytics suite. If you need a single tool that does everything, that’s a different evaluation. If you need feature flags that work well and don’t surprise you on renewal, the scope is the right size.

Making the switch

Most teams migrating from LaunchDarkly follow the same steps:

1. Export flags as JSON from the LaunchDarkly dashboard
2. Restructure to the target platform’s format (usually 1-2 hours of scripting)
3. Run both SDKs in parallel during transition — old flags on LD, new flags on the new platform
4. Cut over fully once you’re confident

The SDK swap is the same pattern as any dependency replacement. The main cost is time, not complexity.

If you’re mid-contract on LaunchDarkly, the math is often worth doing: what does Flaggy cost for the rest of the contract term versus staying on the meter? For most teams above 100K MAU, the delta is meaningful — and unlike the meter, it doesn’t grow.

Still weighing your options? Compare the field in our roundup of the best LaunchDarkly alternatives, or go straight to the Flaggy vs LaunchDarkly breakdown.