Feature flags or toggles configured for high-risk deployments; toggleable without code redeployment

Deploying a high-risk feature without a feature flag means the only remediation for a bad release is a full rollback — redeploying old code, re-running migrations in reverse, and potentially incurring downtime. NIST CM-3 covers controlled configuration changes; feature flags implement that control at runtime without touching infrastructure. A flag that can be toggled in a dashboard in seconds is vastly safer than a rollback that takes 15 minutes. Teams without feature flags tie their deployment risk directly to their rollback speed.

Integrate a feature flag service such as LaunchDarkly (free tier) or self-hosted Unleash for high-risk or experimental features.

npm install @launchdarkly/react-client-sdk

Wrap high-risk features in a flag check:

import { useFlag } from '@launchdarkly/react-client-sdk';

export function CheckoutFlow() {
  const newCheckout = useFlag('new-checkout-flow', false);
  return newCheckout ? <NewCheckout /> : <LegacyCheckout />;
}

Configure the flag default to false (off) and enable it incrementally: 1% → 10% → 50% → 100% of traffic. If error rates spike at any stage, toggle the flag off in the LaunchDarkly dashboard — no code change, no deployment, no downtime.