LaunchDarkly pricing in 2026, and how service connections add up
LaunchDarkly doesn't charge per seat. Every plan has unlimited seats. Instead, the bill comes from usage: mainly service connections, which are server-side SDKs connected to an environment, and client-side monthly active users. That makes it cheap to start and easy to underestimate as you grow. This post explains how each unit is counted, what it costs, and where the bill grows.
All prices below were checked on LaunchDarkly's pricing page on 16 November 2026.
LaunchDarkly's plans
| Plan | Price | Seats |
|---|---|---|
| Developer | $0, no credit card | Unlimited |
| Foundation | Pay as you go | Unlimited |
| Enterprise | Custom, with volume discounts | Unlimited |
Developer and Foundation include the same free usage each month, listed below. Developer stops there and is never billed. Foundation charges for usage above it.
What's included free
| Usage | Included each month |
|---|---|
| Service connections | 5 |
| Client-side MAU | 1,000 |
| AI runs | 5,000 |
| Session replays | 5,000 |
| Errors captured | 5,000 |
| Trace spans | 10 million |
| Log lines | 10 million |
On Developer, you're limited to 1 project and 3 environments, with 14 days of data retention.
Foundation usage rates
Above the free allowance, Foundation charges:
| Usage | Billed yearly | Billed monthly |
|---|---|---|
| Service connection | $10 each | $12 each |
| Client-side MAU | $8.33 per 1,000 | $10 per 1,000 |
| Session replays | $2.92 per 1,000 | $3.50 per 1,000 |
| Errors captured | $0.25 per 1,000 | $0.30 per 1,000 |
| Trace spans | $1.25 per million | $1.50 per million |
| Log lines | $1.25 per million | $1.50 per million |
| AI runs | $5 per 1,000 | $5 per 1,000 |
The page says yearly billing saves 17% on usage rates. Its own example: 10 connections and 2,000 MAU cost $58.33 a month billed yearly, or $70 billed monthly.
What each plan adds
Developer ($0):
- Unlimited flags with targeting
- A/B tests and multi-armed bandits
- AI configs and evaluations
- Observability for apps and LLMs
- Community support
Foundation (pay as you go):
- Unlimited projects and environments
- Approval requests with 1 to 5 reviewers
- 30-day data retention and data export
- Annual billing discount, and billing through the AWS or Vercel marketplaces
Enterprise (custom):
- SSO/SAML and SCIM
- Custom roles and unlimited audit history
- Required approvals, scheduling and workflows
- Code references and bulk targeting
- 100+ days of retention, a CSM and premium support
SSO is Enterprise only. If your security policy requires SSO for every tool, the published rates don't apply to you, so get an Enterprise quote early.
How service connections add up
This is the line that grows fastest. The page defines a service connection as one server-side SDK connected to one environment, counted over time and averaged across the month. It says replicas, workers and dev or staging environments all count.
So a modest backend can use far more than you'd guess. Five services, each running 3 replicas, across production, staging and development, is 45 connections, not 5.
What teams pay
Foundation, billed yearly, after the free allowance:
| Setup | Connections above 5 | MAU above 1,000 | Monthly total |
|---|---|---|---|
| 10 connections, 2,000 MAU | $50 | $8.33 | $58.33 |
| 40 connections, 20,000 MAU | $350 | $158.27 | $508.27 |
| 100 connections, 100,000 MAU | $950 | $824.67 | $1,774.67 |
On monthly billing, the same three setups cost $70, $610 and $2,130 a month. Observability, session replays and AI runs above the free allowance are extra.
How to keep the bill in check
- Count connections before you commit. Multiply services by replicas by environments. That number drives most of the bill.
- Question every non-production environment. Dev and staging connections are billed like production. Turn off SDKs in environments that don't need live flags.
- Watch client-side MAU. Each user of a front-end SDK counts. If only some features need client-side flags, keep the rest server-side.
- Bill yearly once usage is stable. Yearly rates are about 17% lower.
- Set a budget for observability. Session replays, errors, traces and logs each have their own meter. Check them monthly.
- Bring a competing quote. Our guide to negotiating a SaaS renewal covers the timing, and our Sentry pricing breakdown covers the error-tracking side.
What to do with this
Work out your real connection count first, including replicas and non-production environments. Then add client-side MAU. Those two numbers will tell you whether Developer, Foundation or an Enterprise quote fits.
See how LaunchDarkly compares, or post an RFP with your connection count, MAU and current spend, and let feature-flag vendors bid. Our software RFP template shows what to include. It's free, and you can post anonymously.
Paying too much for a tool?
Post what you pay and the features you use. Sellers bid to replace it for less. Free, and you can post anonymously.