Blog
Developer Diary
Notes from the process of building a git-native feature flag platform.
Developer Diary: May 17, 2026
A full chaos-testing pass across every SDK, the LaunchDarkly migrator landing with a real conversion report, pack-push CLI shipped end-to-end, and fit-and-finish on the eval charts. Running out of things to add — which is exactly where I want to be.
Developer Diary: May 10, 2026
First real customer migrations off Launch, a Cmd-K palette that gets you to any flag in two keystrokes, the Java SDK is back, and metered billing wired end-to-end through Stripe.
Developer Diary: May 3, 2026
Customer dress-rehearsal migrations, atomic push-conflict detection, multi-org CLI auth, restore-from-tombstone in the UI, and a hardened CI matrix on every SDK. Ready to try.
Developer Diary: April 26, 2026
A two-host delivery split, load tests holding 9k concurrent connections, self-serve workspace creation from the CLI, dev overrides, Slack, and the close-out of the Launch migrator — all aimed at letting people try Quonfig on May 1.
Developer Diary: April 19, 2026
ForceRank.it in production on Quonfig, load testing to 8k SSE, a real qfg migrate CLI, Ruby client bootstrapping, OpenFeature reasons, and one-click restore for deleted flags.
Developer Diary: April 12, 2026
A quick weekly update on observability, OpenFeature, code generation, the Python client, the React SDK, and a lot of product polish.
Why Quonfig: A Developer Diary
I spent years building a feature flag platform backed by a database. Then I tore it all down and rebuilt it on git. Here's where things stand.