Everyone loves DeployHQ!

We have used a few deployment products over the years. We even tried products like Jenkins & Bitbucket pipelines, we spent days on these and made little progress. They were painful, poorly documented and poorly supported, perhaps they would be easier to use if you have an in-house DevOps team.

I can say without a doubt DeployHQ is the most intuitive, easy to configure & troubleshoot deployment tool.

We currently use it to deploy to a multi-server and AWS S3 environment. There was an incredible lightbulb moment recently when we were able to add our AWS S3 as a server for all our Javascript (built on DeployHQ at each deployment) without having to intervene in the build process.

We ship multiple times per day, every day and no longer have to worry about deployments.

For around $1 per month per project, an absolute no brainer. DeployHQ has released us to focus on our product.

Let me try to explain how we feel about your product.

This is the greatest, easiest to use, most robust, best quality, most attractive, and most intuitive deployment tool we have ever seen. We struggled for nearly a week trying to configure Gulp tasks and scripts, Bitbucket pipelines, and who knows what else, to attempt to deploy a recent client project via SFTP. What a nightmare, and we are not a novice team!

Finally we stumbled on an article from our managed WordPress hosting provider, Flywheel. In it, they described how they use DeployHQ for their own deployments. We visited the site, gave it a go, and the site was deployed in T minus 45 seconds (Is that even legal?!). We had so much fun we must have deleted the servers 5 times just to try things out. Everything worked. From the repo autodiscovery to the slack notifications. Bravo squad, bravo.

Please don’t change whatever you are putting in the coffee over there!