---
title: "Feature Flags (Feature Toggles) — Definition & Engineering Context"
description: "Feature flags are configuration switches that enable or disable specific application features at runtime without deploying new code — enabling trunk-based development, gradual rollouts, A/B testing, and instant rollback of problematic features."
canonical: https://erpstack.io/glossary/feature-flags
markdown_url: https://erpstack.io/glossary/feature-flags.md
publisher: ERPStack
---

# Feature Flags (Feature Toggles)

> **Definition:** Feature flags are configuration switches that enable or disable specific application features at runtime without deploying new code — enabling trunk-based development, gradual rollouts, A/B testing, and instant rollback of problematic features.

## In depth

In large ERP teams, deploying untested features to all users simultaneously is risky. Feature flags allow features to be deployed in a 'dark' state, then gradually enabled for specific user segments (e.g., beta customers, specific tenant IDs). If a bug is detected, the flag is toggled off in seconds — no code redeployment required. Feature flags are a prerequisite for continuous deployment in regulated environments where rollback capability must be demonstrated.

## How ERPStack applies this

We implement feature flag infrastructure using LaunchDarkly or open-source Unleash, integrated with our PostgreSQL tenant tables so flags can be enabled per-customer with zero code changes.

## Related reading

- [CI/CD Deployment Pipelines](https://erpstack.io/glossary/ci-cd)
- [Multi-tenant Architecture](https://erpstack.io/glossary/multi-tenant)
- [Technical Debt](https://erpstack.io/glossary/tech-debt)