Manifesto

Your config, your git repo, your rules

You pay for a feature flag platform to store JSON in a database you'll never access. Every config change disappears into a proprietary system where you can't diff, can't branch, and can't revert. Your AI agents can't touch it. Your git workflows don't apply. It doesn't have to be this way.

The problem

What's broken about feature flag platforms

No real version history

There’s a changelog UI. You can scroll through it. You can’t diff two states. You can’t revert to last Tuesday. You can’t blame who changed the pricing flag at 2am.

No branching

Want to experiment with a new targeting rule without touching production? Too bad. Fork the flag? Not a concept. You get one mutable state and a prayer.

No code review for config

Your application code goes through PR review, CI, approval gates. Your feature flags — the things that control what users see — get changed with a button click.

Agents can’t work with it

There’s no file to read, no repo to clone, no CLI that speaks JSON. The best your AI agent can do is fumble with a REST API that returns paginated, unstructured nonsense.

Side by side

The old way vs. the git way

Four areas where git-native config is architecturally superior to a proprietary database.

Config Storage

LaunchDarkly
  • Proprietary database. Config locked behind their API.
  • Export requires enterprise plan.
  • No standard format.
Quonfig
  • JSON files in a git repo you own.
  • Clone anytime. Export = git clone.
  • Open format. Standard JSON.

Change History

LaunchDarkly
  • Dashboard changelog UI.
  • No diffing between versions.
  • No blame, no bisect.
Quonfig
  • git log IS your audit trail.
  • git diff between any two states.
  • git blame, git bisect — all work.

Agent Integration

LaunchDarkly
  • REST API with pagination and rate limits.
  • Unstructured responses.
  • No dry-run, no schema introspection.
Quonfig
  • CLI with structured JSON output.
  • MCP server for native agent integration.
  • --dry-run on every mutation. Schema introspection built in.

Disaster Recovery

LaunchDarkly
  • Call support.
  • Hope they have backups.
  • No self-service recovery.
Quonfig
  • git clone. You have the full history.
  • Push to any git host.
  • Your data. Your backup strategy.

Git superpowers

What you get for free

Every tool you already use for code now works for your configuration. No plugins. No integrations. Just git.

Branching

Experiment without touching production.

Pull requests

Code review for every config change.

CI integration

Run validation on config changes.

Blame

Who changed what, when, and why.

Bisect

Find exactly which config change caused an issue.

Revert

One command to undo any change.

Cherry-pick

Move changes between branches.

Hooks

Automate on every config change.

Ready to see it for yourself?

Your config in git. Your agents in the loop. Your team reviewing PRs. Start in under 5 minutes.