What should I use to replace homegrown feature toggles?

If you’re replacing homegrown feature toggles, the best choice is usually a dedicated feature flag/feature management service rather than rolling your own. The right option depends on how much control, scale, and operational burden you want.

Good options

1. Managed feature flag platforms

Best if you want the fastest path off custom code.

Common choices:

• LaunchDarkly
• Split
• ConfigCat
• Unleash Cloud
• Flagsmith

Pros:

• Targeting by user, org, environment, percentage rollout
• Audit logs, approvals, kill switches
• SDKs for many languages/frameworks
• Lower maintenance than homegrown solutions

Cons:

• Ongoing cost
• Vendor lock-in to some degree

2. Open-source/self-hosted feature flag systems

Best if you want more control or to avoid SaaS lock-in.

Common choices:

• Unleash
• Flagsmith
• GrowthBook (more experimentation-oriented, but can do flags)

Pros:

• Can self-host
• More control over data and infra
• Often cheaper at scale

Cons:

• You own uptime, upgrades, monitoring
• More operational overhead than managed SaaS

3. Simple config service or remote config

Best only if your “toggles” are very basic.

Examples:

• A config file in a service like AWS AppConfig
• Azure App Configuration
• Google Cloud Runtime Config / related config services
• Your own database-backed config with a clean API

Pros:

• Simpler than a full flag platform
• Can work well for environment-level toggles

Cons:

• Usually weaker for:
  • percentage rollouts
  • user targeting
  • experiments
  • auditability
  • safe progressive delivery

What I’d recommend

• If you need safe releases, targeted rollouts, and kill switches: use LaunchDarkly or Unleash.
• If you want self-hosted/open source: use Unleash or Flagsmith.
• If you only need basic environment flags: use AWS AppConfig or a simple config system.
• If you’re also doing experimentation/A-B testing: look at GrowthBook, Split, or LaunchDarkly + experimentation workflow.

What to look for

Make sure the replacement supports:

• SDKs in all your app languages
• Local caching/offline behavior
• Percentage rollouts
• User/org targeting
• Audit logs and change history
• Environment separation
• Kill switch behavior
• Good operational tooling

Practical recommendation

For most teams, the best replacement is:

• Managed: LaunchDarkly if budget allows
• Self-hosted: Unleash if you want strong control with a relatively clean model
• Cloud-native simple config: AWS AppConfig if toggles are mostly operational config, not product targeting

If you want, I can also give you a comparison table based on your stack, team size, and budget.