PRICINGBLOG
Language
Multiple Environments

Multi Environment One Project.

Create separate environments for development, staging, and production. Config and secrets for each environment are isolated, no need to worry about production config leaking to development.

Multiple EnvironmentsDemo
Production
main
active
Staging
develop
active
Preview
feature/*
standby
3 environments activeIndependent configs

Why it matters

What you get

Isolated Environments

Create environments with their own config and secrets: development, staging and production, all separate.

Branch Policy

Set specific branches to specific environments. Main to production, develop to staging.

Shared Resources

Databases and caches can be shared between environments or separated as needed.

Branch per Environment

Connect different branches to different environments, for example develop to staging and main to production.

Steps

How it works

  1. 01

    Create Environment

    Open the Settings > Environments tab. Click Add Environment and give it a name (e.g., staging).

  2. 02

    Set Config

    Add different environment variables for each environment.

  3. 03

    Deploy

    Choose the target environment when deploying. You can deploy to staging first, then to production.

Blog

Read also

Guides and tutorials related to this feature.

FAQ

Frequently asked questions

How many environments can I create?
There is no limit. You can create as many environments as needed, development, staging, QA, production, etc.
Does each environment need its own resources?
Yes, each environment has its own resources. However, you can share databases between environments if needed.
Can I promote from staging to production?
Yes, you can promote config and variables from one environment to another. This feature is available in the Variables tab.

Ready to try?

Sign in with Google or GitHub, connect a repository, and pay from a Rupiah balance. No credit card needed.
WhatsApp