Skip to main content
Configs are key-value settings - database hosts, API base URLs, timeout values, and anything else that should vary per environment without a code change. Unlike secrets, configs are not encrypted and are available to both backend and frontend services.

​
Steps

1

Open your service

Navigate to your project, click on your service, and select the Configs tab.Configs list
2

Create a new config

Click + New Config. A form appears at the top of the list.New config formFill in the fields:Click Create.
3

Config is created

The config appears in the list with its key, type, and current value. Click the edit icon to update the value at any time - changes propagate to all connected SDK clients within milliseconds, no restart required.

​
Template references

Config values can embed secrets and feature flags using {{...}} syntax: Example:
Resolution happens server-side. The SDK receives the resolved string - the raw secret is never exposed.

​
Inherited configs

Configs marked INHERITED come from a linked umbrella service. To override the value for this service only, create a config with the same key - it takes precedence over the inherited one.

​
Next steps

Create a feature flag

Roll out features gradually with targeting rules.

Create a secret

Store an encrypted value and reference it from configs.

Configs reference

Full reference: types, template syntax, umbrella inheritance, live updates.