IT Glossary
What is a feature flag?
A switch inside the code that turns a piece of functionality on or off in a live application, without a new release and without a developer being involved.
Release night used to mean the whole change went live for everyone at once, and the only way back was another release. Feature flags dismantle that. A flag is a condition in the code — is this capability enabled, and for whom — controlled from outside the application, so functionality can ship in a dormant state and be switched on later for one internal team, then five percent of customers, then everyone, and switched off again in seconds if the support queue starts filling. Deployment and release stop being the same event, which is the whole point. Three consequences follow that matter outside engineering. Risk drops sharply, because the response to a problem discovered at scale is a toggle rather than an emergency deployment. Timing moves to the people who own the outcome: marketing can enable a campaign feature on the morning of the launch without booking a developer. And experimentation becomes cheap, because showing two variants to two audiences is the same mechanism with a different rule. The cost is discipline — flags left switched on forever quietly become the most confusing kind of technical debt.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Instant withdrawal when something breaks
A problem found in production is switched off in seconds rather than waiting for a hotfix build, review and deployment cycle.
Gradual rollout with controlled risk
New functionality reaches a small share of users first, so defects surface at a scale where they are annoying rather than expensive.
Business decides the moment, not IT
Launch timing sits with the team responsible for the campaign or the contract, without a release window to negotiate.
Frequently asked questions
How are feature flags managed in practice?
Small teams start with configuration entries or database rows and an internal admin screen, which is entirely adequate for a handful of flags. Dedicated services add targeting rules, gradual percentages, audit history and experiment reporting, priced per seat or per monthly user. The upgrade usually becomes worthwhile when non-technical staff need to operate the switches themselves.
Do feature flags complicate code maintenance?
They do if nobody removes them. Each flag doubles the paths through a piece of code, and a system with forty stale flags has an untestable number of combinations. The working rule is that every flag is created with an expiry date and an owner, and that removing it is part of finishing the feature rather than a task that waits for a quiet week.
Can I use feature flags for A/B testing?
Yes — the targeting machinery is identical, and most commercial flag services include experimentation for that reason. The difference is intent: a release flag protects a rollout and is removed afterwards, while an experiment flag exists to measure two variants against a metric and ends with a decision. Keeping the two categories labelled separately prevents an unfinished experiment from becoming permanent.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247