Nona Docs
Nona is an open source, self-hosted remote config and feature flag service for web, mobile, and backend apps.
Important product scope: Nona is remote config plus simple on/off flags, not a runtime targeting engine. It does not do built-in per-user evaluation, segments, cohorts, or percentage rollouts on the read path.
Use Nona when you want to:
- manage runtime configuration on your own infrastructure
- ship feature flags without a hosted control plane
- expose config over plain HTTP
- separate frontend-readable and backend-only values
- migrate away from Firebase Remote Config
Why teams use Nona
Section titled “Why teams use Nona”Nona is built for teams that want remote config without platform lock-in. The core product traits are self-hosted deployment, open source code, Docker-first operations, plain HTTP plus official clients, projects and environments, client/server/shared scopes, config history and rollback, and Firebase migration tooling.
If you are evaluating alternatives, start with Firebase Remote Config alternative.
Start here
Section titled “Start here”- Why Nona
- Get started
- Feature flags
- Remote config
- Firebase Remote Config alternative
- Open source feature flags
- Open source remote config
- Deployment
- Migration
Quick path
Section titled “Quick path”If you want the shortest route to a working setup:
- Deploy with Docker
- Create your first project
- Add your first parameter
- Create an API key
- Fetch your first config value
- Continue with HTTP client, JavaScript client, or .NET client
What you can do with Nona
Section titled “What you can do with Nona”Common remote config and feature flag use cases:
- add a kill switch for risky features
- update mobile app behavior without a store release
- separate production and staging values cleanly
- expose app settings over HTTP
- keep client-readable config separate from server-only config
- roll back a bad parameter change quickly
See Remote config use cases for more examples.
Feature flags
Section titled “Feature flags”Nona is not only a remote config tool. It is also a feature flag system for teams that want self-hosted flags, kill switches, frontend and backend flag separation, OpenFeature support, and simple boolean release gates without a hosted control plane.
The tradeoff is intentional: Nona keeps feature flags simple. A flag read is not evaluated against user context, segments, cohorts, or percentage rules at runtime.
Start here:
- Feature flags overview
- What are feature flags?
- Feature flags vs remote config
- Kill switches
- Open source feature flags
- Self-hosted feature flags
- OpenFeature
Remote config
Section titled “Remote config”Nona also works as a self-hosted remote config system for teams that want runtime values outside deploy-time env vars, environment-specific behavior, client and server scope separation, server-side remote config, and one system for config plus feature flags.
Start here:
- Remote config overview
- What is remote config?
- Remote config vs environment variables
- Server-side remote config
- Open source remote config
Key concepts
Section titled “Key concepts”- Client vs server scope
- Parameters and content types
- Projects
- Environments
- API keys
- History and rollback
- Parameter share links
- Users and project access
Integration paths
Section titled “Integration paths”Use the smallest integration path that fits your app:
- HTTP for direct reads without an SDK
- JavaScript for Node.js and TypeScript apps
- .NET for C# services and applications
- OpenFeature if you want a vendor-neutral application interface
- CLI for admin workflows and migration work
Migration and comparisons
Section titled “Migration and comparisons”If you are replacing an existing hosted setup:
- Migrate from Firebase Remote Config
- Firebase concept mapping
- Migration validation
- Firebase Remote Config alternative
Production and operations
Section titled “Production and operations”For production deployment and operations:
- Deployment overview
- Standalone production
- Primary/replica production
- Security and authentication
- Backups
- Upgrades
- Audit logs
- Users and project access
What is Nona in one sentence?
Section titled “What is Nona in one sentence?”Nona is an open source, self-hosted remote config and feature flag service for web, mobile, and backend applications.
Is Nona only for remote config?
Section titled “Is Nona only for remote config?”No.
Nona supports both feature flags and broader runtime config in the same system.
Does Nona support per-user targeting or percentage rollout?
Section titled “Does Nona support per-user targeting or percentage rollout?”No.
Nona does not evaluate flags against userId, request context, segments, cohorts, or percentage rules on the read path. The built-in model is environment plus key lookup with scope and API-key access control.
What is the fastest way to understand whether Nona fits my team?
Section titled “What is the fastest way to understand whether Nona fits my team?”Deploy the Docker image, create one project, add one boolean flag and one non-boolean value, then read both over HTTP or a client.
Who is Nona best for?
Section titled “Who is Nona best for?”Teams that want self-hosted runtime control, plain HTTP access, Docker-first deployment, and a smaller product model than a hosted control plane are usually a strong fit.