LaunchDarkly Developer Documentation

Get started in under 30 minutes.
LaunchDarkly provides feature flags as a service for Java · Python · Ruby · Go · Node.js · PHP · .NET. Control feature launches -- who sees what and when -- without multiple code deploys. Easy dashboard for phased rollouts, targeting and segmenting.
Need more help? write us at support@launchdarkly.com

Get Started    Guides

Projects allow you to manage multiple different software projects under one LaunchDarkly account. For example, you can create one project called Mobile App and another project called Web App. Each project will have its own unique set of environments and feature flags. Each project should be set up to serve one set of end users - think one set of feature flags per user base. Breaking your flags up into related chunks of functionality by end user helps to organize related flags and keeps them streamlined for developers.

Project Permissions

You can use custom roles to restrict your team's access to projects or anything else within LaunchDarkly.

When you first create your LaunchDarkly account, you will start with a Default project, and all team members in your account will have access to every project within your account by default. Your current project is visible in the top of the sidebar. You must always have at least one project. You can create a new project in the Projects tab under Account Settings on the sidebar- click "New Project" and name it accordingly. You cannot change the project key after it is created, but you can modify the project name at any time.

Within your projects, you can create multiple environments. Environments allow you to manage your feature flags throughout your entire development lifecycle — from local development through production. All projects must have at least one environment. Typical environments within a project could be Production, QA, Staging, or individual environments.


What's Next

Environments

Projects


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.