Eppo Feature Flags

Feature flags enable you to easily toggle features on and off, conduct A/B/n testing, gradually roll out new functionality, and personalize user experiences — all without the need for extensive code deployments. With feature flags, you can empower your team to make dynamic changes, iterate quickly, and deliver enhanced user experiences with ease.

info

This section of the docs covers configuring feature flags and experiments in Eppo's UI. For developer guides on integrating Eppo into your tech stack, please see the SDKs section.

Concepts

The following are the central feature flagging concepts in Eppo:

• Variations
• Allocations
• Environments
• Targeting rules
• Audiences
• Mutual exclusion

Flag archival is irreversible

Archiving a feature flag is a permanent action — archived flags cannot be unarchived. Before archiving, ensure no running experiments or rollouts depend on the flag. If you need to temporarily disable a flag, turn off all allocations instead.

The flag key of an archived flag can be reused when creating a new flag. However, reusing a key that existing SDK clients may still reference can cause unexpected behavior (the new flag's configuration will be served for the same key). Prefer choosing a new key unless you are certain no deployments reference the old one.

Use cases

Feature flags are applicable for a number of use cases:

• Feature gates
• Experiment assignment
• Progressive rollouts
• Kill switches
• Dynamic configuration