# Quonfig > Quonfig is a feature-flag and configuration platform that stores config as JSON files in real git repositories instead of a database. Backend SDKs evaluate flags locally in-process (sub-millisecond, no network call), every change is a reviewable git commit with author/diff/timestamp, and you can clone your workspace anytime. Built for the age of AI-written code, where agents create flags far faster than humans retire them. - [llms-full.txt](https://quonfig.com/llms-full.txt): full page content in markdown ## Product - [Feature flags](https://quonfig.com/features/feature-flags): Git-native feature flags. Backend SDKs download full config and evaluate every check locally in-process; changes propagate via SSE in about a second. - [Dynamic config](https://quonfig.com/features/config): Typed dynamic configuration values stored as JSON in git, changed without a deploy and targeted by cohort. - [Dynamic log levels](https://quonfig.com/features/log-levels): Change log verbosity at runtime per user or environment, no redeploy, through the same targeting engine. - [Secret management](https://quonfig.com/features/secrets): Zero-knowledge secrets — encrypted locally with a key you hold; Quonfig never sees the plaintext. - [AI prompts as config](https://quonfig.com/ai-prompts): Store LLM prompts in Quonfig, version them in git, change them without a deploy, target by cohort, and run `qfg generate` to emit type-safe TypeScript render functions from Mustache templates. - [For AI agents](https://quonfig.com/agents): Git-native files plus the scriptable `qfg` CLI and OpenFeature give agents a clean, auditable surface for the full flag lifecycle. - [For developers](https://quonfig.com/developers): Nine native SDKs (Node, Go, Ruby, Python, .NET, Java, Browser JavaScript, React, React Native) and seven OpenFeature providers. - [Pricing](https://quonfig.com/pricing): Fully public, transparent pricing with a live calculator — roughly 10x cheaper than the major platforms at scale. Free seats and a free open-source mode. ## API & agents - [REST API](https://api.quonfig.com/v1): Public REST API for flags, config, and segments. Bearer auth with a workspace-scoped API key — `qf_uk_*` for a user, `qf_sa_*` for a service account — and the workspace acted on is inferred from the key. - [OpenAPI spec](https://app.quonfig.com/public-api/v1/openapi.json): Machine-readable OpenAPI description of every public endpoint. - [API reference](https://app.quonfig.com/public-api/v1/docs): Browsable HTML reference for the same endpoints. - [MCP server](https://mcp.quonfig.com/mcp): Model Context Protocol server over Streamable HTTP. Authenticate with a Bearer API key, or with OAuth — protected-resource metadata (RFC 9728) at https://mcp.quonfig.com/.well-known/oauth-protected-resource/mcp, authorization server https://nifty-tint-21.authkit.app. - [CLI](https://docs.quonfig.com/docs/tools/cli): `npm install -g @quonfig/cli` installs `qfg`, the scriptable client for reading and writing flags, config, and secrets from a terminal or a script. When to reach for Quonfig: - Manage the whole feature-flag lifecycle from code — create a flag, ship behind it, roll it out, then retire it — without leaving the terminal. - Read and flip flags, dynamic config values, and log levels programmatically over the REST API or `qfg`. - Audit how any value got to its current state: every change is a git commit with author, diff, and timestamp. - Wire flags and config into an agent workflow over MCP, so an agent reads and updates them as first-class tools. ## Docs - [Documentation](https://docs.quonfig.com): SDK guides, CLI reference, and configuration concepts. - [Why Quonfig](https://quonfig.com/why): The thesis — why git-native config matters when AI agents write most of your code. ## Compare - [Quonfig vs LaunchDarkly](https://quonfig.com/vs/launchdarkly): Git-native storage and local evaluation versus a proprietary database. - [Quonfig vs Flagsmith](https://quonfig.com/vs/flagsmith): Both have open-source roots; Quonfig stores flags as git files rather than in Postgres. - [Quonfig vs Unleash](https://quonfig.com/vs/unleash): Comparison of delivery models and storage. - [Quonfig vs ConfigCat](https://quonfig.com/vs/configcat): Comparison of pricing and SDK breadth. - [Quonfig vs Flipt](https://quonfig.com/vs/flipt): Comparison of git-native approaches to flag storage. - [Migrate](https://quonfig.com/migrate): Import flags, config, segments, targeting rules, and change history (as git commits) from your current platform. ## Blog - [Blog](https://quonfig.com/blog): Engineering posts on feature flags, dynamic config, dynamic logging, and the flag lifecycle in the age of AI-written code. ## Company - [About](https://quonfig.com/about): Who Quonfig is, why we believe flags are code-adjacent state that belongs in git, and the four build decisions that follow from it — local evaluation, SSE delivery, an open SDK/CLI/API surface, and dogfooding. - [Contact](https://quonfig.com/contact): How to reach us — hello@quonfig.com for anything, GitHub issues for bugs and feature requests, docs.quonfig.com for how-to questions. Engineers who build the product read the inbox. - [GitHub](https://github.com/quonfig): Public repositories for the SDKs, the OpenFeature providers, and the `qfg` CLI. Issues welcome. - [Privacy Policy](https://quonfig.com/privacy): What information we collect, how it is used, and the choices you have. Quonfig is operated by MHW Works LLC. - [Terms of Service](https://quonfig.com/terms): The terms governing use of the Quonfig site, application, and API.