Manifesto

Your config, your data, 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 with no real audit trail. Your AI agents can't touch it. If you want to leave, good luck exporting. 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 see who changed the pricing flag at 2am.

You don’t own your data

Your config lives in their database. Want to export? Contact sales. Want to migrate? Good luck. Want a backup? Hope they have one.

No real audit trail

Your application code has git history with diffs, authors, and timestamps. Your feature flags — the things that control what users see — have a changelog you can’t diff or revert.

Agents can’t work with it

There’s no CLI that speaks JSON, no MCP server, no structured output. The best your AI agent can do is fumble with a REST API that returns paginated, unstructured responses.

Side by side

The old way vs. the Quonfig way

Four areas where Quonfig 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.
  • Export anytime. Your data, your terms.
  • Open format. Standard JSON.

Change History

LaunchDarkly
  • Dashboard changelog UI.
  • No diffing between versions.
  • No blame, no bisect.
Quonfig
  • Built-in audit trail powered by git history.
  • See the exact diff between any two states.
  • Every change has an author, timestamp, and reason.

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
  • Clone your repo. You have the full history.
  • Migrate to any git host anytime.
  • Your data. Your backup strategy.

What you get

Three things other platforms can't offer

Because your config is stored in a real git repo, you get guarantees no proprietary platform can match.

You own your data

Your config lives in a git repo you can clone anytime. No vendor lock-in, no export fees, no enterprise plan required to access your own data. If you want to leave, take your repo and go.

A real audit trail

Every config change has an author, a timestamp, and an exact diff of what changed. Not a proprietary changelog — a real version history you can query, diff, and revert with tools you already know.

True disaster recovery

If Quonfig disappears tomorrow, your config doesn’t. Your SDKs keep working from cached config. Clone your repo and you have everything — full history included.

Ready to see it for yourself?

Full UI. Real-time delivery. Agent-ready. Your data in a git repo you own. Start in under 5 minutes.