Using Environments

Railway supports complex development workflows through environments, giving you isolated instances of all services in a project.

Create an Environment

1. Select + New Environment from the environment drop down in the top navigation. You can also go to Settings > Environments.

2. Choose which type of environment to create -

   • Duplicate Environment creates a copy of the selected environment, including services, variables, and configuration.

     When the duplicate environment is created, all services and their configuration will be staged for deployment. You must review and approve the staged changes before the services deploy.

   • Empty Environment creates an empty environment with no services.

---

Sync Environments

You can easily sync environments to import one or more services from one environment into another environment.

1. Ensure your current environment is the one that should receive the synced service(s)
2. Click Sync at the top of the canvas
3. Select the environment from which to sync changes
4. Upon sync, each service card that has received a change will be tagged "New", "Edited", "Removed"
5. Review the staged changes by clicking Details on the staged changes banner
6. Click "Deploy" once you are ready to apply the changes and re-deploy

---

Enable PR Environments

Railway can spin up a temporary environment whenever you open a Pull Request. To enable PR environments, go to your Project Settings -> Environments tab.

When enabled, a temporary environment is spun up to support the Pull Request deploy. These environments are deleted as soon as these PRs are merged or closed.

How Come my GitHub PR Won't Deploy?

Railway will not deploy a PR branch from a user who is not in your team or invited to your project without their associated GitHub account.

Domains in PR Environments

To enable automatic domain provisioning in PR environments, ensure that services in your base environment use Railway-provided domains. Services in PR environments will only receive domains automatically when their corresponding base environment services have Railway-provided domains.

Focused PR Environments

For monorepos and multi-service projects, Focused PR Environments only deploy services affected by files changed in the pull request. This speeds up PR environments and reduces resource usage.

How It Works

When a PR is opened, Railway determines which services to deploy:

1. Services connected to the PR repo that are affected by changed files (based on watch paths or root directory)
2. Dependencies of affected services (via variable references like ${{service.URL}})

All other services are skipped and indicated on the canvas. The GitHub PR comment shows which services were skipped.

Deploying Skipped Services

Skipped services can be deployed manually from the canvas. Click on the skipped service and select "Deploy" to add it to the PR environment.

Enabling Focused PR Environments

1. Go to Project Settings → Environments
2. Ensure PR Environments are enabled
3. Toggle Enable Focused PR Environments

Bot PR Environments

You can enable automatic PR environment creation for PRs opened by supported GitHub bots using the Enable Bot PR Environments toggle on the Environments tab in the Project Settings page.

Supported bots:

• Dependabot
• Renovate
• Devin AI
• GitHub Actions
• GitHub Copilot
• Jules (Google)
• Roo Code
• Claude Code (Anthropic)

---

Environment RBAC

Restrict access to sensitive environments like production. Non-admin members can see these environments exist but cannot access their resources (variables, logs, metrics, services, and configurations). They can still trigger deployments via git push.

Contact us to enable it for your enterprise workspace.

Once enabled, go to Project Settings → Environments and toggle the Restricted switch for any environment you want to restrict.

Role	Can access	Can toggle
Admin	✔️	✔️
Member	❌	❌
Deployer	❌	❌

---

Forked Environments

As of January 2024, forked environments have been deprecated in favor of Isolated Environments with the ability to Sync.

Any environments forked prior to this change will remain, however, you must adopt the Sync Environments flow, in order to merge changes into your base environment.