Pricing
Flexible pricing for every team.
Simple. Predictable. No hidden fees.
Developer
Feature flagging and experimentation for your project.
Free forever
Pay only when you exceed Developer tier limits.
- Unlimited Seats
Includes
- One project
- 3 environments
- 5 service connections per month
Service connections are the number of microservices, replicas, and environments connected to LaunchDarkly for 1 month. - 1k contexts per month Each client side user or device creates a context.
- 10k experimentation keys per month Keys are used to measure targeting for experiments. They allow you to target specific groups of contexts or segments to experiments.
Foundation
Feature management and experimentation for growing teams.
per Service Connection Service connections are the number of microservices, replicas, and environments connected to LaunchDarkly for 1 month.
or 1K contexts Each client side user or device creates a context.
Enterprise
Advanced feature management and experimentation at scale.
Custom
Contact sales for more information.
- Unlimited Seats
Everything in Foundation plus +
- Advanced user targeting
- Release automation
- Workflows, scheduling, & approvals
- SAML / SCIM
- Release Assistant
- Custom roles & teams
Guardian
Monitor and guard your releases at scale.
Custom
Contact sales for information on usage-based subscriptions.
- Unlimited Seats
Everything in Enterprise plus +
- Guarded Releases
- Application Performance Thresholds
- Release Auto-Remediation
- Release Health Metrics
Compare all features
Platform
—Feature management
+
Experimentation
+Release observability
+Release automation and collaboration
+Security & compliance
+Integrations & API
+Support and SLAs
+FAQ
Pricing
Months are calculated based on when you start your plan. If you start a plan on September 18th, you'll be charged on the 18th of every month. If you start on the 31st, you'll be charged on the last day of every month. If you upgrade your plan, you'll be charged a prorated amount for the partial month, and your next month's bill will include the upgrade as part of your monthly charge.
Client-Side Contexts are calculated by counting the number of unique contexts evaluating flags from client-side SDKs over a given month Typically, customers will send user contexts and we count unique end users that evaluate a flag, so even if a single user evaluates flags from multiple device types or over multiple sessions, we only count that user as 1 client-side context over the calendar month. For anonymous traffic, we can track them by session or device contexts so if they visit multiple times they will only be counted as 1 client-side context over the monthly period.
To estimate the number of client-side contexts you’ll need, first determine what context you primarily aim to target (e.g. users, devices, accounts). Your goal is to use the context(s) that provide you with the control points necessary to support the power of LaunchDarkly’s targeting. If primarily targeting users, for example, you can count the number of unique monthly active users that would use your application(s) where the LaunchDarkly client-side SDKs are installed. In addition to your primary context—often users—you can also include any other contexts you want (devices, accounts, etc.), but your estimate needs to only count the context with the highest volume.
Yes. All Enterprise plans are based on annual contracts. For the Foundation plan, you can select a yearly option when you sign up or at any time from the billing page in our app. There is an automatic discount on all plans set up with annual billing.
Usage metrics
Service connections are used to measure back-end feature management. Service connections are the number of microservices, replicas, and environments connected to LaunchDarkly for 1 month. Only server-side SDKs count toward measuring service connections. Read the docs to learn more.
Each client-side user or device creates one context. Read the docs to learn more.
Experimentation keys are the number of users or contexts bucketed in an experiment on a monthly basis. Experimentation keys allow you to target specific groups of contexts or segments to experiments, refining your testing audience. Read the docs to learn more.
We provide visibility on all of your usage metrics. You can learn more about usage metrics in our documentation.
Foundation & Developer
You only get charged when you exceed the Developer tier limits for environments (3), service connections (5), contexts (1k), or experimentation keys (10k).
We offer monthly and annual billing options for credit card purchases. Monthly billing will be charged in arrears at the end of each month. Annual billing will be paid up front, and any monthly overages will be billed at the end of each month.
Account management
Usage metrics are visible in the account settings section of the application. If your team exceeds one of the licensed limits there will be a notification in the application and an email sent to all team Administrators. Professional plans are able to add more events or MAUs as needed up to the specified limits. Enterprise plans will receive the same notifications and our customer success team will work with them to correctly size their licensed limits.
Yes. We provide visibility on all of your usage metrics. You can learn more about usage metrics in our documentation.
LaunchDarkly's basic role-based permission system provides global access control levels for team members based on a set of built-in roles (reader, writer, or admin/owner). Customers on enterprise plans also have access to LaunchDarkly's custom roles system. Custom roles allow you to create flexible policies that provide fine-grained access control to everything in LaunchDarkly—from feature flags and metrics to environments and teams. With custom roles, it's possible to enforce access policies that meet your exact workflow needs.
Data
Yes. Experimentation can be added as an unlimited 30-day trial by contacting sales.
Yes, you pay per event that is sent for experimentation and/or to the data export add-on.
Other
Yes. Please contact us to see if your organization is eligible.
Case study
Paramount improves developer productivity 100X.
/ /The ability to ship and merge code to environments safely without wincing every time we hit the ‘deploy’ button has been huge for us.
Dan Skaggs
Technical Director, Content Engineering, Paramount
Case study
CCP Games creates self-serve experimentation.
/ /LaunchDarkly has enabled self-serve experimentation. You don’t have to be a data scientist to run valid, actionable experiments. This is unbelievably powerful.
Nick Herring
Technical Director of Infrastructure, CCP Games
Case study
Christian Dior shortens time to market from 15 minutes to instant updates
/ /LaunchDarkly allowed us to progressively deliver key features with confidence, creating a safety net for developers.
Fabien Gasser
Retail Lead System Architect, Christian Dior Couture
Case study
Bayer’s digital farming arm improves reliability for critical apps.
/ /I can change a flag status in LaunchDarkly and see it reflected in our mobile apps instantly. I’ll pay for that any day.
Artie Lee
Director of Engineering, Climate LLC, Bayer
Case study
HP standardizes and scales releases with LaunchDarkly.
/ /The team can switch back to a feature behavior without doing code changes.
Brent Foley
Software Engineer - Platform Infrastructure Team, HP
.svg?ixlib=gatsbyFP&auto=compress%2Cformat&fit=max)
Take a tour.
