Feature management

Four things a bare boolean in a config file does not: it targets variations by user, attribute, or segment rather than serving everyone the same value; it ramps exposure with a percentage rollout and cuts it with a kill switch; it keeps a separate configuration per environment with an audit trail of every change; and it ships SDKs that evaluate locally in sub-milliseconds and receive updates over a streaming connection. The feature flags concept guide covers the full model.

Most teams start with a database column and an if statement, which works until the questions get harder: how do we target one customer, keep staging and production separate, see who flipped a flag last week, update every server without a redeploy, or find the flags nobody uses anymore? Feature management is the point where the flag system itself becomes a product surface worth not building in-house. The trade-off is laid out in build versus buy for feature flags.