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 | Colour | Meaning |
|---|---|---|
running | Green | Service is live and healthy |
stopped | Amber | Postgres service is hibernated — compute paused, storage billed |
pending | Grey | Deployment is queued or starting up |
failed | Red | Deployment encountered an error |
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 the ⋮ menu on the active deployment and select Redeploy.
This is useful to pick up a new version of a latest Docker image tag.
Stopping, starting, and restarting a Postgres service
Postgres services have three additional lifecycle controls in the ⋮ dropdown on the active deployment:
| Action | When available | Effect |
|---|---|---|
| Stop | Service is running or failed | Hibernates the cluster. Pods scaled to zero, PVC retained. Compute billing paused. |
| Start | Service is stopped | Restores the cluster from the retained volume. Full billing resumes once running. |
| Restart | Service is running | Deletes and recreates the primary pod. Brief connection interruption (~30 s). Billing unaffected. |
See Stopping, starting, and restarting for the full walkthrough including billing details.
Undeploying a service
To remove the active deployment without deleting the service:
- Open the service panel → Deployments tab.
- Click the ⋮ menu on the active deployment and select Remove.
The service remains configured on the canvas but stops consuming all resources (compute and storage). You can redeploy it at any time.
For Postgres services, prefer Stop over Remove when you want to pause the service temporarily — Stop preserves the database volume so you can resume later, whereas Remove tears down the entire cluster.
Rolling back
To roll back to a previous deployment:
- Open the service panel → Deployments tab.
- In the Deployment history section, find an older deployment.
- Click the ⋮ menu and select Rollback.
The selected deployment is re-run with its original image and configuration. The previous active 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.
