At LaunchDarkly, our mission has always been to give platform teams runtime control over their software. To do that reliably tens of trillions of times a day, our own internal "source of truth" for system health must be beyond reproach.
For the past several years, we have utilized a variety of observability tools to monitor our global flag delivery network. However, as the landscape of software delivery evolves, so must our internal stack.
Today, we are announcing that LaunchDarkly is officially moving its primary observability and telemetry workloads to New Relic.
Why the Shift? Why Now?
Software is no longer just built and monitored, it is adjusted and tuned in real-time. This shift requires a level of transparency between the feature management layer and the observability layer that a "jack-of-all-trades" provider simply cannot offer.
Our decision to standardize on New Relic was driven by three core architectural principles:
1. Integrity of Data
In the modern SaaS ecosystem, neutral observability is paramount. As other providers in the space move toward vertically integrated, black box models that attempt to bundle feature management and monitoring, LaunchDarkly remains committed to a best-of-breed approach.
By moving to New Relic, we ensure our telemetry is managed by a partner whose sole mission is intelligent observability, turning data into actionable intelligence. This avoids any conflict of interests that may arise when evaluating feature performance.
2. Scalability at the Edge
LaunchDarkly serves tens of trillions of flag evaluations daily. Our infrastructure demands an observability partner that can handle massive cardinality without trade-offs on cost at scale New Relic’s consumption-based model and Intelligent Observability platform provide the high-fidelity data our engineers need to maintain 99.99% uptime for our customers.
3. A Closed Loop Between Control and Visibility
We believe the "Golden Signal" stack of 2026 is LaunchDarkly + New Relic.
- LaunchDarkly provides the control plane for feature flags
- New Relic provides the feedback loop and automated actions
By migrating our operations to this stack, we are proving that the most sophisticated software delivery platform in the world runs best when it is unburdened by legacy monitoring silos.
What This Means for Our Customers
For our customers, this migration is a win for stability and innovation. Our engineering teams can see, in real time, how a flag rollout affects latency, error rates, and throughput across our global network. That kind of closed-loop visibility changes how we operate — and it's the same capability we want our customers to have
We are deepening our technical integration with New Relic so that what we’ve done internally becomes a repeatable path for every enterprise looking to pair best-of-breed feature management with best-of-breed observability.
"As AI accelerates how fast software gets written and shipped, engineering leaders need an observability layer they can fully trust, one with no stake in the decisions it's helping them make. LaunchDarkly runs some of the most demanding infrastructure in software delivery, and its decision to standardize on New Relic is a meaningful signal to the industry that the best teams are choosing depth over breadth, and a neutral source of truth over a competitor. We are proud to be that platform and excited about what we'll build together."
— Michael Frendo, Chief Technology Officer at New Relic
The Road Ahead
The migration is already underway. By standardizing on New Relic, LaunchDarkly is doubling down on our commitment to an open, interoperable ecosystem where the best tools win—and where your data always belongs to you. As our teams work together on deeper integration between our platforms, we’ll share updates on what that unlocks.
Like what you read?
