How-to

Set environment variables

Add variables one by one or paste a .env file. Changes apply on the next deploy.

Environment variables hold settings and secrets your app reads at runtime, such as database URLs and API keys. Keep them out of your repository and set them in Kubana instead.

Add variables

Open your app → Environment, then either:

  • add a single KEY=value, or
  • paste a block in .env format to add many at once.

Changes apply on the next deploy

Kubana stores your changes straight away, but the running app only sees them after the next deployment. Each variable shows whether it is deployed or has pending changes. Deploy from the dashboard when you're ready.

Find and edit variables

  • Search by key. Values are not searched.
  • Edit a page of variables at once.
  • Show / Hide values when you need to read them.

Build time or run time?

  • Most frameworks: variables are available both during the build and in the running app.
  • Laravel: variables are available at run time only. VITE_* variables are not available during the asset build yet.

Reserved names

You can't use GIT_SSH_KEY_B64 or any key starting with KUBANA_. Kubana uses those itself.

Anyone with access to the app can reveal its values. Use separate keys for production and staging, and rotate a key if someone who could see it leaves your team.

Last updated 19 October 2026 · Something missing or wrong? Tell us