Show HN: Feature flags on Redis you use – no new infrastructure
Redis-feature-flags offers a solution for teams already using Redis to implement feature flags without the need for additional infrastructure. This approach allows for cost savings by eliminating the need for SaaS subscriptions while maintaining control over user data. It provides features like gradual rollout, user targeting, and a kill switch, all managed through a simple CLI.
- ▪Redis-feature-flags allows teams to use their existing Redis infrastructure for feature flag management.
- ▪It is designed for startups and small teams looking to avoid new costs and maintain data control.
- ▪The tool supports gradual rollouts, user targeting, and instant feature disabling without redeployment.
Opening excerpt (first ~120 words) tap to expand
redis-feature-flags Feature flags for teams that already run Redis. No new server. No new cost. Your data stays in your infrastructure. 📦 PyPI · Maven Central · CLI · 📖 Documentation Why? Most teams already run Redis. It sits in your stack as a cache or a session store. You are already paying for it, operating it, and trusting it. Feature flag SaaS products charge hundreds of dollars a month for a server you do not need, send your user data to their infrastructure, and add another thing to monitor. redis-feature-flags uses the Redis you already have. Nothing else.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.