Feature Management Platforms
Can you help me estimate LaunchDarkly Foundation cost for 20 service connections and 500k client-side MAU?
7 min read
LaunchDarkly’s Foundation plan is designed to give you fast release control and experimentation without forcing you into an enterprise-style buying process. If you already know your rough architecture—how many backend services and how many client users—you can get to a pretty accurate cost estimate in a few minutes.
Quick Answer: For 20 service connections and 500k client-side MAU on the LaunchDarkly Foundation plan, the list-price estimate is:
- Service connections: 20 × $12/mo = $240/mo
- Client-side MAU: 500k / 1k × $10/mo = $5,000/mo
- Estimated total (Foundation): ~ $5,240/month (before any annual discounts or custom terms)
Below is a more detailed walkthrough of how that number is calculated, what each metric really means in production, and what to consider before you lock in a plan.
The Quick Overview
- What It Is: A cost estimate for running LaunchDarkly’s Foundation plan with 20 backend service connections and 500,000 client-side monthly active users (MAU).
- Who It Is For: Engineering and product leaders who want a clear, numbers-backed view of what LaunchDarkly might cost in a realistic production setup.
- Core Problem Solved: Translating abstract pricing metrics (“service connections” and “client-side MAU”) into a concrete monthly dollar figure you can use for budgeting.
How It Works
LaunchDarkly Foundation pricing is built around two main usage measures:
- Service connections – how many backend service instances are connected.
- Client-side MAU – how many unique client-side users/devices encounter flags in a month.
Once you understand those two dials, estimating your Foundation cost is just basic multiplication.
Step 1: Understand service connections
From LaunchDarkly’s official docs:
- Service connections measure back-end feature management.
- A service connection is:
- “One instance of one server-side SDK connected to one LaunchDarkly environment for a time period measured in minutes.”
- Foundation pricing (from the knowledge base context):
- $12 per service connection / month
In practice, that means if you have a microservice running in production and it connects to LaunchDarkly via a server-side SDK, that’s one service connection for that environment. If you run multiple replicas or multiple environments (for example, prod + staging), you’ll have multiple service connections.
For this estimate, you’ve specified:
- 20 service connections
So the monthly cost for service connections is:
- 20 × $12/mo = $240 per month
Step 2: Understand client-side MAU
From LaunchDarkly’s official docs:
- Client-side MAU are:
- “The client-side users, devices, organizations, or other defined entity that encounter feature flags in your product in 1 month.”
- Foundation pricing (from the knowledge base context):
- $10 per 1,000 client-side MAU / month
Important nuance: MAU are counted as unique entities per month, not total sessions or pageviews. A user who sees 20 flags in a month still counts as a single MAU.
For this estimate, you’ve specified:
- 500,000 client-side MAU
First, convert MAU to units of 1,000:
- 500,000 MAU ÷ 1,000 = 500 units of 1k MAU
Now multiply by the rate:
- 500 × $10/mo = $5,000 per month
Step 3: Combine for the Foundation estimate
Add the two components together:
- Service connections: $240/mo
- Client-side MAU: $5,000/mo
Estimated LaunchDarkly Foundation cost:
$240 + $5,000 = $5,240 per month (list price)
This is the straightforward, documentation-based estimate—no discounts, no overage considerations, and assuming all your usage fits inside the plan’s standard model.
Features & Benefits Breakdown (Why These Metrics Matter)
| Core Feature | What It Does | Primary Benefit |
|---|---|---|
| Service connections (server-side) | Connects each microservice / replica / environment to LaunchDarkly at runtime | Lets you control backend features, kill switches, and guardrails after deploy, no redeploys required |
| Client-side MAU | Tracks unique users/devices that evaluate client-side flags each month | Gives you fine-grained control over customer experience, UI rollouts, and front-end performance risks |
| Foundation plan pricing model | Simple per-connection and per-1k-MAU pricing at list rates | Makes it easy to forecast costs as you grow, without waiting on an enterprise quote to model basic scenarios |
Ideal Use Cases for This Configuration
-
Best for growing B2C or B2B apps at scale:
Because 500k MAU and 20 service connections often map to a product with multiple services (auth, core API, notifications, billing) and a large active user base. You get runtime control over high-risk changes with meaningful coverage across your user population. -
Best for teams moving from “deploy-driven” to “runtime-controlled” releases:
Because this size of investment pays off when you’re shipping frequently and want to avoid 2am fire drills—using feature flags, targeting, and progressive rollouts instead of “ship and hope” deploys.
Limitations & Considerations
-
This is a list-price estimate, not a quote:
LaunchDarkly often offers automatic discounts for annual billing or custom terms for higher volumes. Your actual price may be lower if you commit annually or negotiate based on usage. -
Overages and growth can change the bill:
If you exceed your committed service connections or client-side MAU, LaunchDarkly will bill for overage usage. If you’re close to 500k MAU today and growing quickly, it’s worth modeling 750k or 1M MAU as well so you’re not surprised later.
Pricing & Plans Context
From the official pricing context:
- Foundation
- $12 per service connection / month
- $10 per 1k client-side MAU / month
- Designed for “feature management and experimentation for growing teams.”
Using your numbers:
- Service connections: 20
- 20 × $12 = $240/mo
- Client-side MAU: 500k
- 500 units of 1k MAU × $10 = $5,000/mo
Total estimated Foundation cost: ~ $5,240/month at list price.
Plan-positioning summary:
- Foundation: Best for teams that already have multiple services and real user volume, and who need robust feature management plus experimentation.
- Enterprise / Guardian / Platform tiers: Better suited for organizations needing advanced governance (custom roles, policies, audit logs at massive scale), Guardian-style automated rollbacks, or broad platform-wide runtime control—but those require talking to sales for detailed pricing.
Frequently Asked Questions
Does each replica count as a separate service connection?
Short Answer: Yes, each instance of a server-side SDK connected to one environment is a service connection.
Details:
Docs define a service connection as “one instance of one server-side SDK connected to one LaunchDarkly environment.” If you scale a service horizontally (for example, 5 replicas of your API in production, each running the LaunchDarkly SDK), those contribute to your service connection count. Similarly, if you run separate environments (prod, staging, dev) with their own SDK instances, each of those connections counts. For estimation, many teams start with peak replica counts in production and a trimmed-down count in non-prod.
How accurate is this $5,240/month estimate in real life?
Short Answer: It’s directionally accurate at list price, but final numbers can vary with discounts, exact usage, and contract terms.
Details:
The math is pulled directly from LaunchDarkly’s published Foundation pricing:
- $12 per service connection / month
- $10 per 1k client-side MAU / month
If your 20 service connections and 500k MAU assumptions are correct, this is a solid baseline. However, your final price may differ because:
- Annual billing often comes with discounts.
- You may negotiate a contract that includes higher committed usage at a blended rate.
- Your actual MAU may be lower or higher once flags are implemented (e.g., only certain parts of your app use LaunchDarkly).
- You might add Experimentation MAU or Observability usage later, which can introduce additional line items.
For anything beyond rough budgeting, it’s worth validating the estimate with a LaunchDarkly representative.
Summary
Using LaunchDarkly’s Foundation pricing model, a setup with 20 service connections and 500,000 client-side MAU lands at an estimated $5,240 per month at list price:
- $240/mo for server-side service connections
- $5,000/mo for client-side MAU
This configuration gives you runtime control over both backend services and a large client user base—so you can roll out features progressively, flip kill switches, and run experiments in production without redeploys.
Next Step
If you want a precise quote, factor in experimentation and observability needs, or talk through how service connections map to your specific architecture, the fastest path is to talk to the team directly: