We think your feature flags belong in git

Creating a flag writes a file. Flipping it in production writes a commit. Asking who changed the pricing flag at 2am is git log, not a support ticket. That is the whole trick, and everything else about Quonfig follows from it.

The rest is a normal, modern platform. There is a UI for people who would rather not hand-edit JSON, environment-scoped targeting rules, percentage rollouts, reusable segments, dynamic config values and log levels alongside the flags, and real-time delivery to processes that are already running. We simply refused to make the storage layer proprietary. Your workspace is a git repo we host for you, and you can walk away with all of it at any time.

Quonfig is built by Jeff Dwyer, who started it in 2026 after several years building Prefab, an earlier feature-flag and dynamic-config platform. Prefab taught us what teams actually do with flags at scale, and where a database-backed design runs out of road once agents start creating them. Quonfig is the second attempt, with the storage decision made the other way, and Prefab's customers moved across with it.

Feature flags are code-adjacent state. A flag decides what your users see, which makes it exactly as load-bearing as the code around it. Yet on most platforms that state lives somewhere your code review never reaches: no diff, no blame, no revert, no way to bisect a bad Tuesday. You would not accept that for a config file in your repo. We do not think you should accept it for a flag either.

The second half of the argument is newer. When agents write the code, flags get created far faster than humans retire them. A model can open a flag, ship behind it, and move on inside a single afternoon; nobody is going to remember to clean that up six weeks later. In that world the interesting problem stops being “can I toggle a boolean” and becomes lifecycle and auditability — what exists, who made it, why, and whether it is safe to delete. Git already answers those questions well for code. Keeping config in git means it answers them for config too.

So we made the storage deliberately boring: one JSON file per key, in a repository you can clone with qfg pull or with plain git. If Quonfig disappeared tomorrow you would still hold every flag, every value, and every change that was ever made to them. We would rather earn the renewal than hold the data hostage.

If you are evaluating Quonfig, migrating off something else, or you have hit an edge the docs do not cover, tell us. Email goes to the people who build the product, not to a queue. Bugs and feature requests are welcome as issues on the SDK and CLI repos, which are public.

Start at our contact page for the full list of ways to reach us, or go straight to hello@quonfig.com and github.com/quonfig.