Deployments
Deploy, redeploy, rollback, and stream logs for your services.
A deployment is a running or historical instance of a service. Every time you apply changes that affect a service, a new deployment is created.
Viewing deployments
Click a service node to open the service panel, then go to the Deployments tab. You'll see:
- Active deployment — the currently running instance with its status, started-at timestamp, and live metrics
- Deployment history — previous deployments with their status and timestamps
Deployment statuses
| Status | Meaning |
|---|---|
running | Service is live and healthy |
stopped | Service has been manually stopped |
failed | Deployment encountered an error |
pending | Deployment is queued |
deploying | Deployment is in progress |
Triggering a deployment
Deployments are triggered when you click Apply in the Apply Changes bar after making a change to a service (image update, variable change, resource resize, etc.).
You can also manually trigger a redeployment:
- Open the service panel → Deployments tab.
- Click Redeploy next to the active deployment.
This is useful to pick up a new version of a latest Docker image tag.
Undeploying a service
To stop a running service without deleting it:
- Open the service panel → Deployments tab.
- Click Undeploy next to the active deployment.
The service remains configured on the canvas but stops consuming resources. You can redeploy it at any time.
Rolling back
To roll back to a previous deployment:
- Open the service panel → Deployments tab.
- In the Deployment history section, expand an older deployment.
- Click Rollback to this deployment.
Railway immediately promotes that deployment to active. The previous deployment moves to history.
Viewing logs
To stream logs for the active deployment:
- Open the service panel → Deployments tab.
- Click View Logs on the active deployment.
Logs are streamed in real time. You can filter by text to narrow down output.
To view logs for a historical deployment, expand it in the history list and click View Logs.
Staged changes and deployments
Simplifyd Cloud collects changes before applying them. This means:
- Adding or updating variables does not redeploy immediately — you must click Apply.
- Changing service settings (image, resources) stages the change — you must click Apply.
- The Apply Changes bar summarises everything that will happen before you commit.
Click Discard in the Apply Changes bar to abandon all pending changes.