What Are Feature Flags?
Code-controlled switches that change behavior without deployments
A feature flag is a conditional in your code that controls behavior at runtime:
The flag value comes from a remote service (like Flipswitch), not from your code. Change the value in the dashboard, and your running application changes behavior immediately.
Why Use Them?
Deploy code, enable later. Ship code to production without exposing it to users. Enable the feature when you're ready, not when the deployment finishes.
Gradual rollouts. Release to 1% of users first. If metrics look good, increase to 10%, then 50%, then 100%. If something breaks, roll back to 0% instantly - no code deploy needed.
Target specific users. Show features to your team first. Then beta testers. Then premium customers. Then everyone.
Kill switches. Something broke? Disable the feature in milliseconds. No rollback, no hotfix, no 3am panic.
Common Use Cases
| Use Case | How It Works |
|---|---|
| Canary releases | Ship to 1% of traffic, monitor, expand |
| A/B testing | Split users between variants, measure results |
| Kill switches | Instant disable when things go wrong |
| Gradual rollouts | Gradual release from 0% to 100% |
Flag Types
Flags aren't just on/off switches. Flipswitch supports all OpenFeature flag types:
| Type | Example | Use Case |
|---|---|---|
| Boolean | true / false | Feature on/off |
| String | "blue" / "green" | UI variants |
| Number | 100 / 500 | Limits, timeouts |
| Object | {"theme": "dark"} | Complex config |
Next Step
Ready to try it? Create your first flag.