Deployment Targets for your projects
Save time and streamline your workflows with DeployHQ's deployment targets. Effortlessly deploy your code to multiple servers at once—whether it's a single FTP server or a cluster on DigitalOcean—managing all your destinations in one place.
What are deployment targets?
In DeployHQ, deployment targets are destinations for your code. For you, this could be a single FTP server, or a group of servers on DigitalOcean that all run the same application.
You can consider a target representing a specific environment that your code lives on, such as a production or staging server. Within a DeployHQ project, you can only connect to a single repository, however you can add as many targets as you like.
-
FTP or FTPS
![]()
-
SFTP
![]()
-
AWS S3
![]()
-
DigitalOcean
![]()
-
Shopify
![]()
-
Cloudflare R2 and CDN
![]()
Why are deployment targets useful?
In many cases, a typical DeployHQ project will consist of three targets, one for development, one for staging and another for production.
The development target will be set up to deploy from a dev branch, then the staging and production targets from master. You can individually specify which targets will be deployed to manually or automatically to as well - you might not want your code automatically deployed to production when you’ve pushed a change to your master branch!
