What Is a Dark Launch?
A dark launch is the practice of deploying a feature into production but keeping it hidden from users, so you can validate it in the real environment before any public release.
Dark launching separates the act of shipping code from the act of revealing a feature. The new functionality runs in production -- exercised by tests, internal users, or background load -- but ordinary users see nothing, letting you de-risk a launch quietly before announcing it.
What dark launching means
In a dark launch, code is live in production but its user-facing effect is suppressed, typically behind a feature flag. The feature can be exercised, measured, and warmed up under real conditions while remaining invisible, so launch day is a low-risk flip rather than a leap into the unknown.
Why teams do it
Production is the only environment that truly resembles production. Dark launching lets you verify that a feature works against real data, real scale, and real infrastructure before exposing it. It also lets a large change bake in production gradually instead of arriving all at once.
How it is done
The most common approach wraps the feature in a flag that is off for users but on for internal accounts or test traffic. Backend changes can also be dark-launched by executing the new code path in parallel and comparing results, without surfacing anything to the user.
Dark launch versus shadow traffic
The terms overlap. A dark launch generally means the feature is deployed but hidden; shadow traffic specifically means duplicating real requests to the new code path without using its responses. Shadow traffic is one technique for dark-launching a backend change.
The payoff at release
Because the code has already proven itself in production, the actual release becomes a quiet configuration change rather than a deployment event. This shrinks launch risk dramatically and decouples the engineering work from the marketing or product timing of the reveal.
Key takeaways
- A dark launch deploys a feature to production but hides it from users.
- It validates code against real scale and data before any public release.
- Shadow traffic is one technique for dark-launching backend changes.