Deployments

A deployment is the full process of taking your repository, building it, and getting it running. Every time your app is updated — whether triggered by a git push or manually — a new deployment runs.

Auto-deploy on push

By default, every push to your selected branch triggers a new deployment automatically. Jetpacked receives a webhook from GitHub when you push and starts a new deploy immediately.

You can disable auto-deploy from Settings → General if you want to control when deployments happen manually.

Manual redeploy

You can trigger a redeploy at any time from your project's overview page by clicking Redeploy. This runs a full deployment using the latest commit on your selected branch.

This is useful after changing environment variables, updating settings, or if a deploy failed and you've fixed the underlying issue.

What happens during a deployment

1. Your repository is cloned at the latest commit
2. Dependencies are installed
3. Required services are provisioned (if not already running)
4. Your app is built
5. Migrations are run (if detected)
6. The new container is started
7. The previous container is replaced once the new one is healthy

Deployment status

Each deployment has one of the following statuses:

Status	Meaning
queued	Waiting to start
running	Currently in progress
live	Succeeded — app is running this deployment
failed	Something went wrong — check the logs
cancelled	Superseded by a newer deployment

Deployment history

Your project keeps a history of recent deployments. You can view each one's logs from the Deployments tab. How many deployments are retained depends on your project plan:

Plan	Deployments retained
Free	3
Starter	10
Pro	50
Power	100

Failed deployments

When a deployment fails, Jetpacked produces a diagnostic report explaining what went wrong and suggesting a fix. Your previous deployment stays live — a failed deploy does not take down your running app.