Developer tools
Nona
Open Source Remote Config and Feature Flags
- Category
- Developer tools
- Stage
- Beta
- For
- Developer teams seeking self-hosted remote configuration and feature flags for mobile, backend, and cross-platform applications.
About
Open source remote configuration and feature flags for teams that want to run the system themselves. Self-hostable via Docker, works with any language or platform.
Features
- Problem
- Shipping a toggle change normally requires a new build or deployment.
- How it works
- Stores boolean feature flags and typed config entries that apps fetch at runtime.
- Result
- Faster releases, operational toggles, and production kill switches.
- Why
- Teams can enable, disable, or change behavior from the dashboard or CLI without redeploying.
- Problem
- Mobile, backend, and cross-platform apps need a common low-level integration path.
- How it works
- Exposes configuration through a REST API, with JavaScript, .NET, Android, Swift, and OpenFeature integration paths documented.
- Result
- Apps can adopt Nona with or without an SDK.
- Why
- HTTP works in any language, while clients add runtime-specific conveniences.
- Problem
- Frontend-readable settings and backend-only settings require different access controls.
- How it works
- Uses client, server, and shared scopes, with API keys limited by project, environment, and read scope.
- Result
- Narrower configuration access across frontend and backend workloads.
- Why
- Applications receive only values appropriate for their configured access level.
- Problem
- Teams need controlled, reversible configuration changes.
- How it works
- Keeps entry history and rollback, and can snapshot config as immutable releases that can be activated or pinned by clients.
- Result
- Safer production changes and predictable release reads.
- Why
- Operators can review, restore, and promote tested configuration states.
- Problem
- External collaborators may need to review or edit one value without full account access.
- How it works
- Creates scoped, expiring, revocable, audited parameter share links.
- Result
- More focused collaboration without broad dashboard access.
- Why
- Sharing is limited to a specific parameter and can be withdrawn.
- Problem
- Moving off existing configuration services can be operationally difficult.
- How it works
- Provides CLI migration workflows with dry runs for Firebase Remote Config and AWS Parameter Store values referenced by ECS task definitions.
- Result
- A repeatable path to self-hosted configuration.
- Why
- Migration plans can be reviewed before changes are applied.
Screenshots
