You can trigger one-off deployments to any stage or service in Seed. This can be useful for example, when you want to test a hotfix branch in your staging environment.

### Manually Deploy a Stage

To manually deploy a stage, head over to the app pipeline. And hit **Deploy** on the stage you want to manually deploy.

Here you can enter a Git branch, tag, or commit that you want to deploy.

The next time you trigger a deployment, Seed will auto select the last ref that was deployed.

You can optionally force a deploy, more on this below.

### Manually Deploy a Service

To deploy a specific service, click the dropdown for the service in the stage you want to deploy. Hit **Deploy Service**.

Just as above, you’ll be asked to confirm the branch or to select one.

### Force Deploys

By default, Seed will only deploy the services and Lambda functions that have been updated. You can [read more about Incremental Deploys here](/content/docs/what-are-incremental-deploys/index.html). To skip this check and deploy all your services and Lambdas, select the **Force deploy** option.

This option tells Seed to deploy all your services even if there are no changes that’ve been detected.

A **Force deploy** also clears the [dependency cache](/content/docs/caching-dependencies/index.html) for the stage you are deploying to.