1
Feature flagging tools need a revamp. The market has been around for 10+ years, and most solutions have gone upmarket—combining flagging with experiments (great for eCommerce, useless for SaaS) and prioritizing only Enterprise needs.
Folks we chatted with decried bloated products filled with features they don’t use, complicated UIs, and unpredictable pricing.
So we’re building a focused, purpose-built tool that prioritizes developer experience.
That means tackling features like self-cleaning flags to remove obsolete flag code automatically. As well as a toolbar to toggle features locally when testing, making it easy to manage beta programs, and deep integrations with Linear (to create and manage flags from inside issues) and Slack (to keep everyone up to date with access rule changes and feedback).
It also means focused refinement, not endless features. We’re feature flagging for SaaS that run on TypeScript. That’s it.
Why just SaaS? Because SaaS customers are companies and subscribers. Yet flagging tools treat these as an afterthought. It’s weird that you have to paste lists of UUIDs to give companies access to features. We’ve made working with companies as easy as users with company-level controls.
Why only TypeScript? It’s the stack modern SaaS uses. Plus, the focus means we can create things like self-cleaning flags, as well as essential improvements, like type safety at the flag-key level.
Teams at GitBook, Code Climate, Pleo, and ai.work are already using Reflag. We’d love for you to try it, and let us know what else we can do to make working with feature flags better.
Check us out at: https://reflag.com
Watch a quick overview: https://x.com/reflagcom/status/1963542152895500397