LaunchDarkly

“Now that we can join our LaunchDarkly experiments to our Snowflake data, we can measure real user and business outcomes. We can take bigger risks in the kinds of AI features we build, and we can validate that they're worth it because we can see downstream impacts all the way through.”

“With [LaunchDarkly], pinpointing and resolving issues within our portals has never been more efficient.”

“The true value of LaunchDarkly is that our product teams can look at their events without getting blocked by analytics, prioritization, and bandwidth.”

“We were able to launch our generative AI feature without turning it into a massive engineering project. Product teams can experiment directly, so we're not spending hours deploying updates just to test prompt changes.”

“We've received some questions from customers and all we've had to do is adjust an ops flag. We can increase a limit very quickly.”

“We were able to prevent multiple outages and reduce resolution time by 50% when a flag was used compared to a classic deployment of new code.”

“LaunchDarkly gave the business teams the confidence that experiments could be run reliably and the data could be trusted.”

“At times, we would put so much time and effort into a release only to have it roll back and [negatively] impact our customer experience. The fact that at a click of a button avoiding an outage can save us revenue and lower our mean time to recovery by 66% is game-changing for us.”

“LaunchDarkly helps us deploy to smaller user groups that can help us address issues before they become problematic for the business.”

“LaunchDarkly has helped us reduce the back and forth between product and engineering. The Jira integration makes it easy for all teams to know the status of a flag at any point of a feature release.”

“We needed a solution that benefited our tech stack and multiple languages as well as a solution that not only had robust targeting but could help teams test their code safely across environments.”

“Before LaunchDarkly, we had several bottlenecks in the way we delivered software across our user base. Teams couldn’t target a feature and roll it out to only that set of users. In our space, we only have certain features that are allowed in certain states, so it's more than just releasing to the right customers—it's a matter of compliance.”

“LaunchDarkly lets us move quickly but with control. Our engineers can deploy features as soon as they're done building them. And we [on the release team] can gradually release those features at a pace that matches our enterprise customers' tolerance for change.”

“Now, when we deploy new functionality, we have all the documentation ready, the training on it has already been completed, and everything is caught up on the back-end.”

“We use LaunchDarkly’s feature flags to turn features on and off, enabling our engineering team to go as fast as they possibly can. At the same time, this allows those of us on the release team to control the flow of changes and information that are rolled out to our customers, which makes it easier for them to adjust to new features and versions.”

“That's why we really push the use of feature flags for all of our teams—not just in production, but in development too.”

“It becomes a natural place for any infrastructure change.”

“From your teams all the way to your execs, it's just a given that you're continually deploying.”

“Production deployments are a non-event. There's not this celebration anymore, because deployments have become a way of life,”

“Let's say we realize, 'Oh, this month, we have N million more invoices to issue, and so we need to scale up even more than we usually do.' That difference will be captured in some state, and that state is now still in LaunchDarkly,”

“During the first of the month, we want to scale really aggressively because we have a huge backlog of invoices to get through. We flip a flag in LaunchDarkly, and that orchestrates which services are scaling in what way.”

“We have a LaunchDarkly configuration for what should be the state of the service depending on where we are in the month,”

“We have this sophisticated reporting feature set where your finance team needs to be able to look at revenue in real time,”

“With billing, even 15 minutes is significant—you could issue hundreds or thousands of invoices in that time.”

“For this given account, for this given migration, how quickly are we going to progress through all the invoices and subscriptions and customers and move things around from one version to another.”