Deployments Overview
Every time you send an update to Guara Cloud, a deployment is created. The deployment represents the complete process of turning your code into a running application in the cloud.
How it works
The deployment process follows simple, automated steps:
- Code submitted — you push to GitHub or click “Deploy” in the dashboard
- Image build — Guara Cloud creates a container image from your code
- Application deploy — the new version goes live
- Health check — Guara Cloud confirms the application is responding correctly
The full pipeline typically completes in 2 to 5 minutes, depending on build complexity.
Status lifecycle
Each deployment goes through a sequence of statuses that indicate its progress:
| Status | Description |
|---|---|
| Pending | The deployment has been created and is waiting for the build to start |
| Building | The container image build is in progress |
| Deploying | The new version is being put into production |
| Healthy | The application is running and responding correctly |
| Failed | An error occurred during the build or deploy |
Deployment history
Guara Cloud keeps a complete history of all deployments for your service. In the dashboard, go to the Deployments tab of your service to view:
- Status of each deployment (Healthy, Failed, etc.)
- Date and time the deployment was created
- Commit that triggered the deployment (SHA and message)
- Trigger type (automatic push, manual, or rollback)
- Duration of the full deployment
Deployment details
Clicking on a specific deployment opens a detailed view with:
- Image tag — unique identifier of the generated container image
- Commit SHA — the exact code commit used
- Duration — total build and deploy time
- Current status — detailed status with timestamps for each stage
- Build logs — full output of the build process
Deployment types
Guara Cloud supports different ways to initiate a deployment:
| Type | Description |
|---|---|
| Automatic push | Triggered automatically when you push to the configured branch |
| Manual | Started by the user directly from the dashboard |
| Rollback | Restores a previous working version |
| Config change | Triggered when you change environment variables or service resources |