Configs
Stop managing application configs in environment variables and spreadsheets nobody owns. Configs gives you versioned, targeted, governed runtime configuration, with the proven reliability of Harness' flag delivery network.
Roll out any config value with the same rigor as a feature flag release, from approval to real-time delivery.
Config changes propagate in real time, no restart, no redeploy, with every version logged and one-click rollback.
Every config change is approved before it releases, with RBAC, policy enforcement, and a full audit history.
Serve the right value to the right user with per-environment targeting rules, the same bucketing engine as feature flags.
Versioned and reversible. Every save increments the version with a full audit log. Roll back to any prior state in one click, no incident, no redeploy.
Streaming updates via SSE. Changes reach your app without a restart or redeploy. Sub-second propagation.
Use any config as an experiment assignment source. Turn a config variation into an A/B test. Assign users to different values, connect your metrics, and measure exactly what the change did to your business.
RBAC with five granular permissions. Create, edit, delete, archive, unarchive. Control who can change what, down to the individual config level.
Approval workflows. Submit a change, lock the config while pending, accept or withdraw. Same pattern as feature flag approvals.
OPA policy enforcement. Config changes evaluated against your organization's policies before they reach production.
Multiple variations per config. Define different values for different user segments, geographies, or custom attributes. Same rule syntax as feature flags.
Same targeting engine as feature flags. Any rule you can write for a flag, you can write for a config. No new syntax to learn.
Promote across environments in one click. When dev is ready for production, promote values without copy-paste. Versioned and reversible.
increase in release velocity
risk-controlled deployments per month
“Split provides so much more than just a tool set ... It's transformative in terms of the teams, in terms of the culture that we adopt.”
— Mirza Baig, Senior VP of Engineering, Experian
Config management is the practice of controlling application behavior through runtime config values rather than hardcoded settings or environment variables. A platform like Harness Configs lets you update values like timeouts, rate limits, feature thresholds, and service endpoints instantly, target different values to different environments or user segments, and track every change with a full audit trail. The result is faster iteration and safer production changes without redeployments.
Environment variables are set at deploy time and require a redeployment to change. They have no versioning, no approval workflow, no targeting, and no rollback mechanism. Harness Configs delivers values at runtime through a low-latency SDK, so a change takes effect instantly without touching your deployment pipeline. You also get per-environment config hierarchies, RBAC-enforced approvals, and a complete audit log of every change, none of which are possible with environment variables.
Yes. Harness Configs supports per-environment targeting rules and multi-variant configs using the same bucketing engine as feature flags. You can serve one set of values to your development environment, a different set to staging, and a third to production, all from a single config definition. You can also target specific user segments or percentage rollouts for gradual config changes before a full rollout.
Every config change in Harness can be gated by a configurable approval workflow before it reaches production. You define which roles can propose changes, which roles must approve them, and whether OPA policy checks need to pass first. Once approved, the change is applied immediately with no deployment required. The full approval chain is recorded in the audit log alongside the before and after values of the config.
Harness maintains a version history for every config. If a change causes unexpected behavior, you can roll back to any previous version with a single click. The rollback takes effect instantly through the runtime SDK with no redeployment. You can also use Harness Release Monitoring to correlate a config change to a spike in errors or latency, which surfaces the problem and the fix in the same workflow.
No, it complements one. Feature flags control which code paths run for which users. Configs control the values those code paths use at runtime. Harness bundles both under the same SDK, targeting engine, governance layer, and experimentation platform. That means a single integration gives your team feature flags, remote configuration management, and A/B testing with one consistent set of rules for access, approval, and observability.
Live updates, environment hierarchies, and approval workflows. No redeploy required.