Comparison
Quonfig vs Unleash
Quonfig and Unleash are both self-hostable feature flag platforms with local, in-process SDK evaluation. The core difference is where your config lives. Unleash is a mature open-source FeatureOps control plane backed by an admin Postgres database. Quonfig stores every flag as a JSON file in a real git repo, so each change is a reviewable commit you can diff, blame, and clone. Choose Unleash for its proven self-host story and 25+ SDKs; choose Quonfig when you want git-native config, free seats, and a built-in audit trail that is just git log.
Side by side
Quonfig vs Unleash, feature by feature
Both tools self-host and evaluate locally. The differences are in the storage model, delivery, pricing, and platform scope. Unleash's column reflects its real, current capabilities.
| Capability | Quonfig | Unleash |
|---|---|---|
| Storage model | Git repo — one JSON file per flag, self-hosted on Gitea | Admin Postgres database |
| Config-as-code / clone your data | qfg pull or plain git clone — full history, no export step | Config lives in the DB schema; export via API or DB dump |
| Audit trail | git log — real author, exact diff, timestamp per change | Event log in the admin UI / API |
| Real-time delivery | SSE + global edge, ~1s propagation, ETag caching, 60s safety poll | SDK polling (default ~15s); streaming on newer setups |
| Local in-process evaluation | Backend SDKs evaluate locally, sub-millisecond, zero network hop | Yes — SDKs evaluate locally against a polled snapshot |
| SDK breadth | 9 native SDKs + 7 official OpenFeature providers | 25+ SDKs (community + official), broad language coverage |
| Self-host | Open-source local mode — read JSON from a directory, no account | Mature, first-class self-host story (their core strength) |
| Pricing model | Usage-based, free seats, public live calculator | Per-seat (~$75/seat/mo, 5-seat minimum on paid) |
| Unified platform | Flags + dynamic config + runtime log levels + secrets, one engine | Flags + config (constraints, strategies, variants) |
A neutral dash marks a capability Unleash offers in a different shape — not a missing feature. Unleash is a serious, credible tool.
Which to pick
Best for…
Both are strong choices. Pick based on what you care about most.
Best for teams who want their flag config to live in a git repo they own — every change a reviewable diff with an author and timestamp — plus free seats, usage-based pricing, and a unified platform that also covers dynamic config, runtime log levels, and secrets.
Best for teams that want a mature, battle-tested open-source FeatureOps platform with the broadest possible SDK coverage (25+) and a first-class self-host story, and are comfortable with a Postgres-backed control plane and per-seat pricing.
Storage model
A git repo, not an admin database
The single biggest difference is where your flags live. Unleash stores its config in an admin Postgres database — a solid, proven design, but your flag state lives inside their schema. To audit a change you read an event log; to leave you export through the API or dump the database. Quonfig stores every flag as a JSON file in a real git repo (self-hosted Gitea). That means your change history is git log — real author, exact diff, real timestamp — your rollback is git revert, and your backup is git clone. You can review flag changes in a pull request before they ship, and you can take the entire repository with you at any time. There is no proprietary export format and no export fee, because the storage format is just files in git.
Delivery & evaluation
Both evaluate locally — Quonfig pushes changes faster
Both platforms keep flag evaluation in-process: backend SDKs hold the full config and resolve every flag check as a local function call, so there is no per-evaluation network hop. That is a genuine Unleash strength and Quonfig matches it. The delivery layer differs. Unleash SDKs poll for updates on an interval (commonly ~15 seconds by default). Quonfig pushes changes over SSE through a global edge, propagating in about a second, with ETag caching and a 60-second poll as a safety net. Because backend SDKs evaluate from a locally-cached config, your app keeps serving even during a delivery outage. 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.
Scope & pricing
One targeting engine for more than flags, with free seats
Quonfig is one platform with one targeting engine and one audit trail spanning feature flags, dynamic configuration, runtime log levels (change verbosity per user or environment without a redeploy), and zero-knowledge secret management where you hold the key. Pricing is usage-based and fully public — there is a live calculator, seats are free, and there is a free, open-source local mode that reads JSON from a directory with no account. Unleash prices per seat (about $75/seat/month with a 5-seat minimum on paid plans), which is a common and predictable model but adds cost as your team grows. If you want product, ops, and support to all have access without per-head fees — and you want one tool instead of separate flag, config, and secret systems — Quonfig is the tighter fit.
Config-as-code, head to head
Both teams believe in config-as-code and local evaluation. The difference is whether your config is literally code in a repo, or rows in a database.
- Flag config stored in an admin Postgres database.
- Audit via an event log in the admin UI / API.
- Per-seat pricing (~$75/seat/mo, 5-seat minimum on paid).
- Mature, first-class self-host story.
- 25+ SDKs across many languages.
- Local, in-process SDK evaluation.
- Flag config stored as JSON files in a git repo you own.
- Audit trail is git log — author, diff, timestamp per change.
- Usage-based pricing with free seats and a live calculator.
- Open-source local mode — read JSON from a directory.
- 9 native SDKs + 7 official OpenFeature providers.
- Local, in-process SDK evaluation, sub-millisecond.
See your flags as files in a repo you own
Free seats, usage-based pricing, and an audit trail that's just git log. Get started in under 5 minutes.