Capability
Remote Config
Change runtime behavior without a redeploy by serving operational and product configuration through the same evaluation path as flags.
Why remote configuration
Configuration locked in code or environment variables creates a deployment cost for every change. Need to adjust a rate limit? That's a code change, a PR, a review, a build, and a deploy. Need to tune a threshold or change copy? Same process. Configuration changes feel like code changes because they are — they require the full release cycle.
Remote configuration through the flagging platform eliminates that overhead. String flags can serve copy, theme keys, or API endpoint overrides. Numeric flags control rate limits, timeouts, retry counts, or percentage values. All of this is configuration, delivered at runtime without touching code or restarting services.
The key advantage: remote config through Zenmanage uses the exact same evaluation engine as feature flags. You get targeting (different config per segment), environment scoping (different production and staging values), an audit trail (who changed what, when, and why), and the same permissions model. It's not a separate, unmanaged config store — it's configuration with the same controls as your flags.
Key capabilities
-
String and numeric flags as config
Use string flags for copy, theme keys, or API endpoint overrides; numeric flags for rate limits, timeouts, or thresholds - no special config type required.
-
Targeted configuration
Apply different config values per segment - serve a higher rate limit to enterprise users or a different onboarding copy to new signups.
-
Environment-aware config
Serve different configuration values per environment so development, staging, and production each have appropriate settings.
-
Same audit trail as flags
Every config change is tracked the same way flag changes are - who changed what, when, and why.
-
No-deploy updates
Push configuration changes instantly to all connected SDKs without restarting services or triggering a deploy pipeline.
See it in action
Use string and numeric flags as runtime configuration — change values in the dashboard, and connected SDKs pick up the update immediately.
const rateLimit = await client.getValue('rate-limit-max', {
type: 'service',
identifier: 'checkout-api'
});
// → Returns 1000 (numeric) — adjustable at runtime without redeploying
Related capabilities
-
Feature Flags
The same flag types that power remote config
-
Integrations
Connect config delivery to your stack
Developers
For developers
Config values are just flags under the hood - the reference covers value types, defaults, and how the SDK resolves them at evaluation time.
Stop redeploying for configuration changes
Push config updates instantly without restarting services or running deploy pipelines.