Nona is the open source remote config and feature flag API you run yourself. One Docker command, any language, updates live the instant you toggle them.
100% open source · Apache 2.0 · REST + 4 native clients
checkout_v2dark_modebanner_text↑ flip a toggle or edit the text
GET /parameters → checkout_v2: true, banner_text: "Summer sale"Click a toggle — watch your app change on the next request.
curl "https://nona.example.com/api/environments/production/parameters/Features%3ACheckout" \
-H "X-Api-Key: your-api-key"A straightforward runtime config system you run yourself — intentionally simpler than a full feature-management platform.
Ship code behind a flag. Enable or disable per environment from the dashboard — no redeploy. Learn more →
Use Nona behind the vendor-neutral OpenFeature API with provider packages for JavaScript backends, browsers, and .NET services — listed in the OpenFeature ecosystem. Learn more →
Update iOS, Android, React Native, and Flutter without a new build. Change copy, toggle UI, kill a broken feature — instantly. Learn more →
Something's broken in production? Flip a flag and it's off in seconds. No hotfix, no incident-driven deploy.
Separate config for dev, staging, and production, isolated by API key. Same code, different behaviour per environment.
One GET request returns all your config as JSON. Works anywhere HTTP works.
A temporary, no-login link to view or edit one parameter — scoped, expiring, revocable, audited. Learn more →
Prepare config, snapshot it as an immutable release, activate it when ready. Learn more →
Nona is built for teams who want an open source system they can inspect, self-host, and own — not for teams who want zero operational responsibility. If a globally managed, vendor-operated service is the priority, Firebase Remote Config is the stronger fit; see the full comparison below.
Firebase is stronger if you want a managed global service. Nona is stronger if you want an open source system you can self-host, inspect, and control.
Already on Firebase Remote Config? The Nona CLI can migrate your parameters automatically. For the full tradeoff, read the Firebase Remote Config alternative guide — or, if you're moving off AWS Parameter Store, the same tradeoffs apply.
Why Nona exists
Too many teams have to choose between moving fast and keeping control. We wanted a remote config system that stays simple: self-hostable, inspectable, portable across languages, and practical to migrate to from Firebase Remote Config.
The long version covers the product decisions, the open source reasoning, and the mission behind the project.
From the blog
Benchmarks, failed optimizations, and the cost of shipping a small self-hosted system in public.
61MiB idle and a container that starts instantly - and no profiler on the binary we ship, no embedded database replicas, and no building it on the machine we develop on. The whole invoice.
Read the post →The harness warmed the heap before measuring it, Docker reported page cache as our memory, port forwarding made one number six times worse, and the build system said a broken project compiled.
Read the post →We rewrote the data layer, dropped Microsoft.Data.Sqlite, went UTF-8, and streamed SQLite straight into the socket. Most of it failed. Here is what we measured and why we stopped.
Read the post →Nona is an open source remote configuration and feature flag service. Store key-value pairs in the dashboard, fetch them at runtime via a single REST API call. Update feature flags, mobile app config, and application settings instantly — no redeployment required.
Open source. Self-hosted by design.
npm install nona-clientchoco install nona-cli