How do we request LaunchDarkly Enterprise pricing and what info do they need (MAU, services, environments)?

Moving to LaunchDarkly Enterprise is about gaining more control at runtime—not wrestling with a mystery pricing sheet. You can request Enterprise pricing in a few minutes, as long as you come prepared with a clear view of your MAU, services, and environments.

Quick Answer: To request LaunchDarkly Enterprise pricing, contact Sales via the “Contact Us” or “Request a demo” flow and share your approximate monthly active users (MAU), number of service connections (microservices/replicas/environments), and any needs around experimentation and observability. That usage picture is what determines your Enterprise pricing and entitlements.

The Quick Overview

• What It Is: A tailored LaunchDarkly Enterprise quote based on your real usage: MAU, service connections, and add-ons like experimentation and observability.
• Who It Is For: Engineering and platform teams that need enterprise-scale feature management, experimentation, and runtime control with governance, SLAs, and support.
• Core Problem Solved: Aligns cost with actual production usage, so you can safely scale feature flags and runtime controls without hitting surprise limits or read-only mode.

How It Works

Requesting LaunchDarkly Enterprise pricing is essentially a short discovery process around how you plan to use the platform in production. The more accurate your usage picture (MAU, services, environments), the more precise your quote and entitlements.

1. Initiate the request:
   Go to launchdarkly.com and use Request a demo or Contact Sales. This opens a conversation with the LaunchDarkly team rather than a self-serve calculator.

2. Share your usage profile:
   Expect questions around:

   • Monthly active users (MAU)
   • Service connections (microservices, replicas, and environments)
   • Experimentation MAU and observability volume
   • Environments (prod, staging, regions) and teams using LaunchDarkly

3. Get a tailored Enterprise proposal:
   Based on that information, LaunchDarkly will size:

   • Base entitlements (MAU, service connections, experimentation MAU, observability)
   • Plan tier (Foundation, Enterprise, or Guardian)
   • Pricing model and any overage/scale terms

From there, you review the proposal, align on scope, and finalize the plan that fits your release and governance needs.

What information LaunchDarkly needs (and why it matters)

1. Monthly active users (MAU)

What MAU means for LaunchDarkly

• MAU is the number of unique monthly active contexts evaluated by LaunchDarkly in a month—typically user contexts.
• Client-side MAU is often priced as, for example, $10/month per 1K client-side MAU on some self-serve plans. Enterprise pricing customizes around your scale and needs.

What to prepare

• Estimated monthly active users for:
  • Web apps
  • Mobile apps
  • Other client-facing surfaces that will evaluate feature flags
• Any expected growth over the next 12–24 months (for scale planning).

Why MAU matters for pricing

• It drives the size of your client-side entitlements.
• It ensures you won’t hit MAU limits and get:
  • Warning notifications about approaching entitlements
  • Read-only mode if you repeatedly exceed limits on a lower-tier plan

Enterprise plans are designed to keep your release controls available even as your user base grows.

2. Service connections (microservices, replicas, environments)

What a service connection is

• A service connection is any connected:
  • Microservice
  • Replica
  • Environment
• Pricing examples from self-serve tiers: $12/month per service connection on some plans.

What to prepare

• A high-level list of:
  • Number of microservices that will use LaunchDarkly SDKs
  • Average number of replicas per service
  • Environments (staging, prod, region-specific prod, etc.)
• Any plans to:
  • Expand from monolith to microservices
  • Add more replicas for reliability
  • Add more regions/environments

Why service connections matter

• It determines how many runtimes you’ll connect to LaunchDarkly for flag evaluations at runtime.
• It affects how LaunchDarkly sizes pricing and entitlements so:
  • You can roll out features progressively across services
  • You can flip kill switches across all replicas and environments without worrying about hitting limits

3. Experimentation MAU

What Experimentation MAU is

• Experimentation MAU = the number of users available to be targeted in experiments each month.
• Example reference: $3/month per 1K Experimentation MAU on some usage-based plans.

What to prepare

• Approximate monthly traffic that you:
  • Want eligible for A/B tests and experiments
  • Plan to segment by region, platform, or customer tier
• Whether experimentation is:
  • Front-end only
  • Back-end only
  • Full-stack across multiple services

Why Experimentation MAU matters

• It defines how many users can be included in experiments without:
  • Hitting experimentation entitlements
  • Needing to constantly re-scope tests
• It ensures product, data, and engineering teams can all experiment on the same feature flags without artificial constraints.

4. Observability usage

What observability usage covers

• Logs and traces tied to feature flags and releases.
• Example reference: some plans include 10M logs and traces with the ability to size usage higher via an Observability Usage Calculator.

What to prepare

• Expected volume of:
  • Logs
  • Traces
  • Events and metrics you want to track around releases and flags
• Whether you plan to:
  • Use observability SDKs heavily (error monitoring, performance metrics)
  • Integrate with your existing APM/logging stack

Why observability matters for Enterprise pricing

• Observability is what lets you:
  • See what’s breaking in real time
  • Tie regressions to specific flags, rollouts, or AI Config changes
• Enterprise plans size these entitlements so you don’t have to throttle visibility to fit a low ceiling.

5. Environments, teams, and governance needs

Environments

Prepare:

• How many environments:
  • Production (per region)
  • Pre-production (staging, QA, UAT)
  • Internal/testing environments
• Any need for:
  • Separate environments per business unit or team

Teams and governance

Prepare:

• Number of teams using LaunchDarkly:
  • Engineering
  • Product
  • Data/experiment teams
  • SRE/Platform/Ops
• Governance requirements:
  • Approval workflows
  • Custom roles
  • Audit logs
  • Policies for who can:
    • Create flags
    • Change targeting rules
    • Trigger kill switches
• Any compliance or change-management requirements your org has (e.g., SOC2, ISO, internal controls).

These inputs help determine whether you need Enterprise or Guardian-level governance, along with advanced release pipelines and automated rollback policies.

How to actually request LaunchDarkly Enterprise pricing

Step 1: Choose your contact path

You can start from multiple places on launchdarkly.com:

• Request a demo (recommended):
  Walk through your use cases live and get pricing contextualized to your architecture.
• Contact Sales:
  If you already know you want Enterprise and mostly need commercial details.

Both paths ultimately connect you with the same Sales/solutions team.

Step 2: Provide your core usage metrics

When you fill out the form or speak to the team, be ready with:

• MAU:
  • Current monthly active users
  • Growth expectations
• Service connections:
  • Number of microservices and typical replica counts
  • Count of environments where you’ll run LaunchDarkly
• Experimentation MAU:
  • Users you plan to target in experiments each month
• Observability usage:
  • Approximate log/trace volume tied to releases and flags

Even rough ranges are useful. You don’t need perfect numbers to start; LaunchDarkly will refine estimates with you.

Step 3: Clarify plan tier and add-ons

LaunchDarkly offers plan families like:

• Foundation:
  Feature management and experimentation for growing teams; often used as a starting benchmark.
• Enterprise:
  For organizations needing advanced governance, scale, and more generous entitlements.
• Guardian:
  For teams emphasizing automated guardrails, automated rollbacks, and strong runtime safety controls.

Discuss:

• Which teams will be in LaunchDarkly on day one vs. phase two
• Whether you need:
  • Advanced experimentation
  • AI Configs for AI behavior control
  • Strong compliance and approval workflows
  • Automated rollback policies (Guardian-style guardrails)

This shapes the exact Enterprise package and pricing.

Step 4: Review entitlements and overage behavior

For Enterprise, you’ll see:

• MAU entitlements
• Service connections entitlements
• Experimentation MAU entitlements
• Observability entitlements (logs, traces)

Clarify:

• What happens if you exceed entitlements:
  • Pricing for overages
  • Whether your account remains fully writable (vs. read-only behavior typical of constrained plans)
• How billing works:
  • Many plans bill monthly for usage exceeding entitlements from the prior month.

This is where you ensure the plan will scale with your actual production usage rather than throttling releases.

Example: How your usage profile maps to Enterprise pricing inputs

Imagine your organization has:

• 500K monthly active users today, growing to 1M+ in 18 months
• 40 microservices, each with 3–5 replicas across:
  • dev, stage, prod in two regions
• 200K users you want eligible for experiments every month
• Significant logging/observability needs due to a high-traffic mobile app
• Multiple teams:
  • 6 product squads
  • A central platform team
  • Data science and experimentation group

When you request Enterprise pricing:

• You’d share:
  • MAU: 500K today, heading toward 1M
  • Service connections: roughly 40 services × replicas × environments
  • Experimentation MAU: 200K monthly
  • Observability: high-volume, with logs and traces tied to feature flags and releases
• LaunchDarkly would:
  • Map this to Enterprise or Guardian with matching entitlements
  • Design pricing that scales as your MAU grows
  • Ensure you don’t risk hitting limits mid-release or triggering read-only constraints

Limitations & considerations

• Usage estimates matter:
  The quote’s accuracy depends on how well you estimate MAU, service connections, and observability volume. If you’re unsure, provide ranges and growth plans.
• Feature availability varies by plan:
  Not all features (like certain observability or experimentation capabilities) are available on every tier. Many advanced features are on select plans—clarify your must-haves during the pricing conversation.

Pricing & plans at a glance

LaunchDarkly’s pricing is usage-based and plan-based:

• Usage dimensions:
  • Monthly active users (MAU)
  • Service connections (microservices, replicas, environments)
  • Experimentation MAU
  • Observability (logs, traces, etc.)
• Plan tiers:
  • Foundation: For growing teams; includes feature management and experimentation.
  • Enterprise: For larger orgs with advanced governance, scale, and support needs.
  • Guardian: For organizations that want guardrail-heavy, automated rollback capabilities and strong operational controls.

Enterprise pricing will align these inputs with:

• Your scale targets
• Your team footprint
• Your governance and reliability requirements

Frequently Asked Questions

Do we need exact numbers for MAU and services before requesting Enterprise pricing?

Short Answer: No. Reasonable estimates and ranges are enough to start the conversation.

Details:
LaunchDarkly understands that usage fluctuates. When you request Enterprise pricing, the team will work with:

• Current MAU and projected growth
• Approximate service counts and environments
• Rough experimentation and observability volumes

You can refine these during the scoping process. The goal is to get close enough to size entitlements and avoid constant overages, not to lock you into a static, fragile estimate.

What happens if we exceed our MAU or service connection entitlements?

Short Answer: On self-serve plans, you’re billed for overages and may eventually hit read-only; on Enterprise, you agree on overage terms upfront so you stay operational.

Details:
Self-serve and lower-tier plans:

• Include limited monthly entitlements for:
  • MAU
  • Service connections
  • Observability
  • Experimentation
• Warn you as you approach or exceed these limits
• Can convert your account to read-only mode if you keep exceeding entitlements

Enterprise plans:

• Are structured to absorb growth with:
  • Larger entitlements
  • Clear overage pricing or scaling provisions
• Are designed so that runtime control remains available, even when your usage hits peak periods.

Summary

To request LaunchDarkly Enterprise pricing, you don’t need a perfect spreadsheet—just a realistic view of:

• Monthly active users (MAU)
• Service connections (microservices, replicas, environments)
• Experimentation MAU
• Observability needs
• Environments, teams, and governance requirements

With that, LaunchDarkly can size a plan that keeps your flags, experiments, and guardrails fully operational in production—without surprise limits or 2am fire drills over read-only mode.

Next Step

Get Started