Flexible Pricing for Every Team

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.

Each team member who logs in with a unique email address counts as a seat.

To align with security best practices, we recommend unique logins for each team member responsible for any of the following:

• Creating flags, generally engineers
• Making changes to flag state (on/off, percentage rollout, targeting rules, etc.), often members of the product or growth team
• Team members requiring a unique API token, typically engineers or automation tooling
• Responsible for team management and LaunchDarkly Administration, such as folks in operations roles

We find that teams also see increased value from the platform as they make use of delegation and our advanced audit logging features. This is increasingly true of larger teams starting at around 10 team members.

Client-Side MAUs are calculated by counting the number of unique end users evaluating flags from client-side SDKs (JavaScript, iOS, Android, Xamarin, C/C++, React, etc.) over a 30-day period. We only count unique end users that evaluate a flag, so even if a single user account evaluates flags from multiple device types or over multiple sessions, we only count that user as 1 MAU over the 30-day period. For anonymous users, we can track them by session so if they visit multiple times they will only be counted as 1 MAU over a 30-day period.

To estimate the number of Client-Side MAUs you'll need, you can count the number of unique monthly active users that would use your application where the LaunchDarkly SDKs are installed. If you're unsure about the number of connections, you can also see how many connections you have historically made in the usage section of our application.

We provide 1,000 Client-Side MAUs on Starter plans and 10,000 MAUs on Professional and Enterprise plans with the core platform. The Client-Side MAUs add-on is intended for teams that need to scale their usage beyond this level.

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.

In most cases, yes. Please contact us to see if your organization is eligible.

Yes. All Enterprise plans are based on annual contracts. For Starter and Professional plans, 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.

The number of Experimentation Events you will need can be estimated by the number of Experiments that you plan to run in a month multiplied by the number of Users that you will include in the Experiments. Since Experimentation Events are only enabled for flags that are actively being used in experiments, you are able to forecast and control your costs without impacting the adoption of the core platform.

Yes. Experimentation can be added to a trial by contacting sales. The trial will be limited to 100,000 Experimentation events.

Yes, you pay per event that is sent for Experimentation and/or to the Data Export add-on.