LaunchDarkly

Overview

LaunchDarkly is a leading feature flagging and experimentation platform designed to empower engineering and product teams to manage the software development lifecycle with greater control and confidence. It provides a centralized service that allows developers to create, manage, and deploy feature flags, which are essentially conditional toggles that can turn specific features of an application on or off remotely. This capability decouples feature releases from code deployments, enabling teams to test new features with a subset of users, perform gradual rollouts, conduct A/B tests, and quickly disable problematic features in production without requiring a new code push.

Key Features

• Feature Flagging: The core functionality allows for the creation and management of feature flags to control the release of new features. This includes targeting specific user segments based on attributes like location, user ID, or custom attributes.
• Experimentation (A/B Testing): LaunchDarkly integrates experimentation capabilities, allowing teams to run A/B tests and multivariate tests directly within their applications to measure the impact of different feature variations on user behavior and business metrics.
• Progressive Rollouts: Safely release new features to a small percentage of users first, gradually increasing the rollout as confidence grows. This minimizes the risk of introducing bugs or performance issues to the entire user base.
• Kill Switches: In case of critical issues with a newly released feature, it can be instantly disabled via its feature flag, acting as a production kill switch without the need for emergency code deployments.
• Permissions and Audit Logs: Robust access control features ensure that only authorized personnel can manage feature flags, and comprehensive audit logs track all changes for compliance and debugging.
• Integrations: LaunchDarkly integrates with a wide range of development tools, CI/CD pipelines, monitoring systems, and analytics platforms to fit seamlessly into existing workflows.
• SDKs: Provides SDKs for numerous programming languages and platforms, making it easy to integrate feature flagging into virtually any application.

Typical Use Cases

• Controlled Feature Releases: Safely introduce new features to production by gradually rolling them out to increasing percentages of users.
• A/B Testing and Experimentation: Test different versions of a feature or UI element to determine which performs best against key metrics.
• Beta Programs: Grant early access to new features for a select group of beta testers.
• Trunk-Based Development: Enable developers to merge code to the main branch frequently, keeping unfinished features hidden behind flags until they are ready for release.
• Operational Toggles: Quickly disable non-critical features that may be causing performance issues or bugs without redeploying code.
• Personalization: Tailor user experiences based on user attributes or segments.

Pricing & Hosting Model

LaunchDarkly operates on a SaaS (Software as a Service) model. Pricing is typically based on the number of monthly trackable users (MTUs) and the features or environments required. They offer different tiers, including a free tier for small teams or individual use, and paid plans for businesses of various sizes. Hosting is entirely managed by LaunchDarkly, meaning customers do not need to manage any infrastructure for the feature flagging service itself. The SDKs communicate with LaunchDarkly's cloud-based platform to evaluate flag states.

Alternatives

Several other platforms offer feature flagging and experimentation capabilities, including:

• Optimizely: A comprehensive experimentation platform that includes feature flagging.
• Split: Focuses on feature delivery and experimentation with a strong emphasis on data-driven decision-making.
• Flagsmith: An open-source feature flagging tool with a cloud-hosted option.
• ConfigCat: A fast, reliable, real-time feature flag service.
• Firebase Remote Config: Part of Google's Firebase platform, offering remote configuration for app features.
• Custom-built solutions: Some organizations opt to build their own internal feature flagging systems, though this requires significant development and maintenance effort.