LaunchDarkly Pricing in 2026: What You Actually Pay
LaunchDarkly pricing in 2026 runs on three tiers: a free Developer plan, a pay-as-you-go Foundation plan metered on service connections and client-side monthly active users, and a custom-quoted Enterprise plan. There is no per-seat charge on any of them. The number that actually lands on your invoice depends on two definitions LaunchDarkly’s own docs spell out precisely: what counts as a connection, and what counts as a monthly active user. This post works through both, plus five smaller meters most teams never check, and runs the math for three real team sizes.
Key Takeaways
- LaunchDarkly Developer is free forever: unlimited seats and flags, capped at 5 service connections and 1,000 client-side MAU a month.
- Foundation meters seven things. Annual-billing rates: $10 per service connection past 5, $8.33 per 1,000 client-side MAU past 1,000, plus AI runs, session replays, errors, trace spans, and log lines.
- A service connection is billing time, not a seat: one server-side SDK instance connected to one environment for a month. A dev or staging environment counts the same as production.
- A 7-connection, 20,000-MAU team lands around $224/mo on Foundation. A 15-connection, 220,000-MAU team runs past $2,400/mo, almost all of it the MAU meter.
- Guardian (automated rollback) and Enterprise (SSO, audit logs) are both custom quotes, not listed rates.
LaunchDarkly’s 2026 pricing, in plain numbers
Developer is free, no credit card required. It includes unlimited seats, unlimited flags with targeting, and unlimited A/B tests and multi-armed bandits. The caps are the plan: 5 service connections a month, 1,000 client-side MAU a month, 5,000 AgentControl AI runs, 5,000 session replays, 5,000 errors captured, 10 million trace spans, and 10 million log lines.
Foundation is pay-as-you-go. Billing annually cuts the rate about 17% versus month-to-month. LaunchDarkly’s own example on its pricing page: 10 connections and 2,000 MAU comes to $58.33/mo billed yearly, which checks out as 5 billable connections at $10 plus 1,000 billable MAU at $8.33 per 1,000.
Enterprise is a custom quote: SCIM provisioning and IdP team sync, custom roles, unlimited audit history, and required approvals and workflows. Guardian, automated rollback on metric regression, is a separately priced add-on on top of either paid plan, also quote-only.
The full rate card is at LaunchDarkly’s pricing page.
What a service connection actually counts
A service connection is “one instance of one server-side SDK connected to one LaunchDarkly environment for a time period measured in minutes,” per LaunchDarkly’s own documentation. Three things follow from that definition, and each one changes a real bill:
- Every replica counts separately. Three pods running the same service are three connections, not one.
- Pre-production environments count. A staging SDK connected all month bills the same as production.
- Serverless bills fractionally. A one-minute invocation counts as 1/43,800 of a connection (a month runs about 43,800 minutes), so a Lambda that fires constantly can still add up to a full connection or more.
Client-side MAU is simpler: each unique client-side user or device is one monthly active user, counted once regardless of how many sessions they open.
The five meters most teams never check
Past connections and MAU, Foundation bills five more things, each with its own free allowance and annual-billing rate:
- AgentControl AI runs: 5,000 free, then $5 per 1,000
- Session replays: 5,000 free, then $2.92 per 1,000
- Errors captured: 5,000 free, then $0.25 per 1,000
- Trace spans: 10 million free, then $1.25 per 1 million
- Log lines: 10 million free, then $1.25 per 1 million
None of these move a bill much on their own, but stack them on a team that also ships observability traffic through LaunchDarkly and they add up to a line item nobody budgeted for. One date worth noting: Release Autopilot is free on Foundation and Developer through February 1, 2027, then priced separately on those plans (Enterprise gets a custom quote from the start).
Three teams, three different LaunchDarkly costs
All annual-billing rates, rounded for readability.
A three-person app, inside the free tier. 3 connections, 700 client-side MAU, 1,200 AI runs, under every other cap. Total: $0/mo, on Developer.
A mid-size product team. 7 connections, 20,000 client-side MAU, 9,000 AI runs, 12,000 session replays, 8,000 errors, 14 million log lines.
- Connections: 2 billable × $10 = $20
- MAU: 19,000 billable × $8.33/1,000 = $158.27
- AI runs: 4,000 billable × $5/1,000 = $20
- Session replays: 7,000 billable × $2.92/1,000 = $20.44
- Errors: 3,000 billable × $0.25/1,000 = $0.75
- Log lines: 4M billable × $1.25/1M = $5
- Total: about $224/mo
A scaling platform team. 15 connections, 220,000 client-side MAU, 30,000 AI runs, 60,000 session replays, 40,000 errors, 80 million trace spans, 100 million log lines.
- Connections: 10 billable × $10 = $100
- MAU: 219,000 billable × $8.33/1,000 = $1,824.27
- AI runs: 25,000 billable × $5/1,000 = $125
- Session replays: 55,000 billable × $2.92/1,000 = $160.60
- Errors: 35,000 billable × $0.25/1,000 = $8.75
- Trace spans: 70M billable × $1.25/1M = $87.50
- Log lines: 90M billable × $1.25/1M = $112.50
- Total: about $2,419/mo
The pattern holds across all three: connections and the smaller meters barely move the number. Client-side MAU is the line that decides the bill.
Where a flat rate changes the math
dif takes a different shape: flags and experiments are Markdown files in your repo, not a hosted platform with meters. The CLI and SDK are free and MIT licensed. Assignment runs locally with no network call, so there is no connection or MAU to count. dif Cloud pricing is flat: $50/mo for 1 million events, unlimited seats, no per-connection or per-MAU line. For a team the size of the scaling example above, that is a fixed number instead of a usage curve.
That is not the full comparison. LaunchDarkly’s streaming updates propagate a flag change in under a second; dif’s rollback is a commit and a deploy, so your worst-case kill is however long your build takes. LaunchDarkly pricing alternative covers that tradeoff side by side with the dollar figures.
FAQ
How much does LaunchDarkly cost in 2026? Developer is free forever, capped at 5 service connections and 1,000 client-side MAU a month. Foundation is pay-as-you-go: $10 per service connection and $8.33 per 1,000 client-side MAU past those caps (annual billing), plus smaller meters for AI runs, session replays, errors, trace spans, and log lines. Enterprise is a custom quote.
What counts as a LaunchDarkly service connection? One server-side SDK instance connected to one environment for a month, counted by connection time. Every replica counts on its own, a dev or staging environment counts the same as production, and serverless invocations bill fractionally by runtime.
Is there a free LaunchDarkly plan? Yes, Developer. It includes unlimited seats and unlimited flags, A/B tests, and multi-armed bandits, capped at 5 service connections, 1,000 client-side MAU, and smaller caps on AI runs, replays, errors, spans, and log lines.
Does LaunchDarkly charge per seat? No. Every tier, including Foundation and Enterprise, includes unlimited seats. The meter is on service connections, client-side MAU, and the five smaller usage metrics.
What is LaunchDarkly Guardian and does it cost extra? Guardian adds automated rollback on metric regression, release monitoring, and guardrail metrics. It is a separately priced add-on on top of a paid plan, quoted by sales rather than listed on the pricing page.
Is there a cheaper alternative to LaunchDarkly? dif’s CLI and SDK are free and open source with no usage meter, since assignment runs locally. dif Cloud is a flat $50/mo for teams that want hosted analytics. For a team past LaunchDarkly’s Developer caps, that flat rate replaces a connections-and-MAU bill that scales with growth.
The number before you commit
LaunchDarkly pricing in 2026 has no per-seat line, which is the part most teams notice first. The part that actually decides the bill is client-side MAU, with service connections a distant second and the five smaller meters rarely more than a rounding error. Run your own connection count and MAU through the math above before signing an annual contract, since the gap between a small team’s $0 and a growing team’s $2,400/mo is the MAU curve, not anything you negotiate.
If a flat number matters more than streaming-speed rollback, dif Cloud runs $50/mo regardless of MAU, and the CLI is free to try with no account: npm install -g @dif.sh/cli, then dif init. The feature flags page covers the file-based model if you want to see what you’d be moving to.