Welcome to LaunchverseQuickstartDashboard Overview
Deployment GuideEnvironment Variables & SecretsCustom DomainsTeam ManagementPreview EnvironmentsRollback & PromoteWeb ShellHow Builds Work (Forge)
AuthenticationProjectsDeploymentsDomainsDatabasesError Codes & Conventions
JavaScript SDKPython SDK
Changelog
API Reference (Redoc)

Environment Variables & Secrets

Environment variables let you configure your application for different environments without hardcoding values.

Adding Variables

  1. Navigate to your project's Settings → Environment Variables.
  2. Click Add Variable.
  3. Enter the variable name and value.
  4. Choose whether it's available at build time, runtime, or both.

Build-Time vs Runtime

    1. Build-time variables are available during the build phase. Use these for values your framework inlines at build time (e.g., NEXT_PUBLIC_* in Next.js).
    2. Runtime variables are available to your running application. Use these for API keys, database URLs, and other secrets.

Masking Secrets

Toggle the Mask option to hide the variable's value in logs and the dashboard. Masked values appear as •••••••• and cannot be viewed after save.

Best Practices

    1. Never commit secrets to version control.
    2. Use masked variables for API keys, tokens, and passwords.
    3. Prefix public client-side variables with NEXT_PUBLIC_ (Next.js).
    4. Rotate credentials regularly using the dashboard.
Edit this page on GitHub↗