To test a new feature in production with limited user exposure, reducing risk before a full rollout.

To refer to the practice of releasing a feature silently to a subset of users for testing.

When a team wants to validate a feature under real production load with limited user exposure before a full launch.

Software engineering, DevOps, continuous delivery, feature flagging, canary releasing, A/B testing.

adjective + noun

adjective + noun

[adjective] launch where adjective can be 'dark', 'silent', 'soft'

• feature flag
• canary release
• beta
• production
• deployment

• silent launch
• soft launch
• canary launch

Confusing dark launch with a public launch, confusing it with canary release, assuming dark launch means hidden from all users

canary release, feature flag, blue/green deployment, A/B testing

Confusing with dark pattern (malicious UX) or dark mode (UI theme)

• feature flag
• canary release
• blue/green deployment
• A/B testing

Implies the feature is active in production but invisible to most users, often controlled via feature flags or percentage rollouts.

Signals that a feature is being tested in production without broad user awareness, indicating caution and experimentation.

Think of launching a rocket into the dark sky—only a few see it.

Often implemented using feature flags or percentage-based rollouts to limit exposure.

canary release → feature flag → progressive delivery