Launch HN: DevCycle (YC W14) – a feature flag platform built for developers
Something I love about the experiment tooling I&#x27;ve used at a few places now (Thread, Google) is the fact that state has typically been stored in source control. i.e. not just the usage of flags in code, but the rollout&#x2F;experiment definitions, the state of how much traffic is allocated to each branch, eligibility requirements, etc. This makes it easy to see what the current state is (without going to a UI), and also makes it much easier to build tooling around that state, as the API data sync problem disappears.<p>Looking at DevCycle, it seems you&#x27;ve not taken this approach, is that right? Scanning your docs it seems there&#x27;s an API to update state, but that fundamentally it&#x27;s kept in your database, not in code. In my experience this isn&#x27;t the best dev experience, so as dev experience is your USP, I&#x27;m interested in why you think this is a better experience, what benefits it can bring over a &quot;git-ops&quot; style, or what I&#x27;ve missed in your docs.