Skip to main content
Open Settings → Advanced settings → Variables. Only site members with Full Access can add, change, or remove variables. Each row is one key and Environment pair, so Production, Preview, and custom Environments can each hold their own value.

​
Public or private

Choose when you add a variable. You cannot switch it later: delete the variable and add it again. Variables go wherever your site’s code runs: Studio previews, schedules, hosted previews, and production. Fimo never writes a private value to an env file or the browser bundle, and hides it from logs. Private values are kept out of the commands agents run on your site, and they test through the preview. Agents still work in the same sandbox as your preview’s server, so keep live keys in Production.
Use a test key for Preview and the live key for Production. Production values are only used to build and run the live site.

​
Add a variable

Choose Add variable, select the Environment, enter an uppercase key such as STRIPE_SECRET_KEY, enter the value, and turn on Private if the value must stay hidden. Add the same key again when another Environment needs its own value. Use the row menu to change a value or delete the variable. Hosted previews of the Environment’s Branches rebuild with the change on their own, within a couple of minutes. The Studio preview picks it up on your next deploy, even with no code change. The live site changes only on your next publish. A variable set by an integration shows a Managed badge and has no row menu. Disable that integration to change or remove it. Names that control how your site’s processes run, such as PATH, NODE_ENV, NODE_OPTIONS or HTTPS_PROXY, cannot be private variables. A public variable with such a name is kept but never reaches your site’s processes, and fimo vars pull leaves it out of .env.local.

​
Variables or secrets

Secrets are for Fimo itself: webhook headers, schedules, and agents. Your site never receives them. If your site’s code needs the key, use a private variable. Developers and coding agents can manage the same variables with fimo vars. Pass --env production to change the live site’s values; without --env, fimo vars changes the Environment of the checked-out Branch, which for main is Preview.