Comparison
Quonfig vs Flipt
Flipt is an excellent open-source, self-hosted feature flag tool — single binary, config-as-code, a clean GitOps workflow — and it's the right pick if you want to run the infrastructure yourself. But Flipt Cloud, its managed product, was shut down in August 2025. Quonfig is the managed git-native platform that's still standing: the same config-as-code and git ownership, plus a hosted UI, real-time SSE delivery, and nine native SDKs — with no infrastructure to run.
Side by side
Quonfig vs Flipt, feature by feature
Both are genuinely git-native. The split is operational: Quonfig is the managed, hosted option; Flipt is the self-hosted, run-it-yourself option.
| Feature | Quonfig | Flipt |
|---|---|---|
Storage model | Git-native — every workspace is a real git repo, one JSON file per key. We host the git server (Gitea) for you. | Git-native config-as-code (or a relational DB). You host and operate the storage yourself. |
Config-as-code / clone your data | qfg pull or plain git clone, anytime. No export fees, no lock-in — the repo is yours. | Yes — flags live in files in your own repo. Strong GitOps story. |
Hosted / managed option | Yes — fully hosted UI and delivery. Nothing to deploy or operate. | No longer offered. Flipt Cloud was sunset in August 2025; OSS is self-host only. |
Real-time delivery | Changes propagate via SSE / global edge in about a second, with ETag caching and a 60s safety-net poll. | Polling / streaming against your own server; delivery is yours to scale. |
Local in-process evaluation | Backend SDKs download full config and evaluate in-process — every flag check is a local, sub-millisecond function call. | Yes — client SDKs can evaluate locally against a bundled snapshot. |
SDK breadth | Nine native SDKs (Node, Go, Ruby, Python, .NET, Java, Browser JavaScript, React, React Native), all at 1.0, plus seven official OpenFeature providers. | Native SDKs in several languages plus an official OpenFeature provider. |
Pricing model | Fully public usage-based pricing with a live calculator and free seats — roughly 10x cheaper than the major platforms at scale. Free open-source mode for local use. | OSS is free. Flipt Pro is $200/mo flat; Enterprise is custom. |
Self-host | Free + open-source mode: read JSON config from a local directory with no account or server. | Yes — single binary, zero-dependency self-host. This is its core strength. |
Audit trail | Built-in and git-powered: every change is a commit with real author, diff, and timestamp. Full history, no retention limits. | Git history of your config files — as complete as your own repo and review process. |
Redundant delivery path | Config delivery runs across redundant, independent infrastructure (a second provider, warmed from GitHub), so your backend keeps serving on locally-cached config even if our primary region has an outage. | Up to you — availability is whatever you build and operate. |
Flipt details reflect its open-source project and the August 2025 Flipt Cloud sunset. Flipt is a registered project of its maintainers; comparison is for evaluation purposes.
Best for
Which one fits your team?
There's no universal winner here — there's a fork in the road. Pick by whether you want to operate the infrastructure or have it operated for you.
- Best for teams that want to self-host and operate their own feature-flag infrastructure.
- An excellent open-source, single-binary, zero-dependency choice with a clean GitOps workflow.
- No longer offers a managed/hosted product — Flipt Cloud was sunset in August 2025.
- Best for teams that want git-native config ownership without running the infrastructure.
- Hosted UI, real-time SSE delivery, nine native SDKs, and seven OpenFeature providers out of the box.
- Built for the age of AI-written code: every flag change an agent makes is a reviewable git commit.
Loved Flipt Cloud? Here's the managed git-native option that's still standing
When Flipt sunset Flipt Cloud in August 2025 and pointed customers back to self-hosting, the managed git-native category effectively emptied out. Quonfig fills exactly that gap. You get config-as-code stored in a real git repo — one JSON file per key, full history as git log — but you never stand up a server, a database, or a delivery tier. We host the git server (self-hosted Gitea), the UI, and the edge delivery. You keep the ownership: clone your workspace anytime with qfg pull or plain git, with no export fees and no lock-in. It's the git-native workflow Flipt users already trust, without the on-call rotation.
Hosted delivery and nine native SDKs you don't have to operate
With Quonfig, real-time delivery and SDK breadth come managed. Backend SDKs (Node, Go, Ruby, Python, Java, .NET) download the full config and evaluate in-process — every flag check is a local function call, sub-millisecond, with zero network round-trip in the hot path. Changes propagate via SSE / global edge in about a second, with ETag caching and a 60-second safety-net poll. There are nine native SDKs in total — adding Browser JavaScript, React, and React Native — all at 1.0, plus seven official OpenFeature providers. Self-hosting Flipt is a great choice, but the streaming tier, the edge, and that SDK surface are all infrastructure you own and maintain. With Quonfig they're the product.
Built for the age of AI-written code
When AI agents write most of your code, flags get created far faster than humans retire them — flag explosion. Quonfig is built for the full flag lifecycle in that world, and both products share the foundation that makes it sane: git. Because every workspace is a real git repo, each change an agent makes is a reviewable commit with an author, a diff, and a timestamp — auditable by default. The scriptable qfg CLI and OpenFeature let you assemble a lifecycle loop today: create a flag when an agent ships work, retire it when the rollout completes. The same git-native principle that makes Flipt trustworthy to self-host is what makes Quonfig safe to let agents write against — now delivered as a managed platform.
Managed git-native feature flags, no infrastructure to run
Flipt Cloud is gone. Keep the config-as-code workflow and git ownership — let Quonfig host the rest. Get started in under 5 minutes.