DeployHQ Reviews & Product Details - Page 5

What do you like best about DeployHQ?

Deploybot has become an integral part of our workflow due to its ease of use and seamless integration with the services we use. Commit, push to Bitbucket, pull open Deploybot, and the latest version of our app is ready to deploy. It handles the update on Elastic Beanstalk seamlessly and allows VERY easy rollback if there's bugs or errors. By far, the fastest site update/CI tool I've used.

Also has an automatic deployment feature based on keywords in the commit, but we don't use this. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

Honestly, there is nothing *not* to like here. This service works, works well, has very low friction. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

Deploybot makes deploying code a breeze. It's easy to set up multiple servers to deploy to, there's numerous ways to connect (FTP, SFTP, SSH), and you can integrate with Github, Bitbucket, Gitlab, and self-hosted git servers.

You can select the branch that you deploy from, they can be automatic or manually triggered, and rollbacks, when needed, are simple.

The interface is intuitive and the price is reasonable. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

Occasionally the service gets interrupted (DDOS attacks or other internal glitches). These can be really frustrating, when you need to push code out. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

1. Good guides - Deploybot has very good documentation for deployment guides, which is very helpful while setting things up. It is a growing repository which shows all the steps for building projects like Laravel and uploading automatically to VMs provided by AWS or DigitalOcean.

2. API endpoints - API endpoints let you programatically trigger a build or list/edit/delete those. While we create the builds by hand, the build triggers are used for connecting with other existing automated workflow, that we already use.

3. Building and compiling assets before deployment - Deploybot allows for building and compiling code using a script before deploying it to server. This removes the need for a separate such service or building every release before pushing to git.

4. Watch deployment progress in real time - Viewing the deployment steps occuring live along with full console output gives you the same flexibility as the older self-hosted deployment solutions. It is also easy to cancel the ongoing process at any time if anything seems wrong.

5. Rollback a release - Accidental or buggy releases can be easily rolled back with a single button, but it still takes some time to get the older release up and running.

6. Deploying without accessing servers is possible by users with low privilege access. Also, good thing is that the release notes gets shared with everyone team so that people can have a overview of all the development going on, even if they are not directly working on it. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

1. Deploying using docker container is a bit cumbersome - it takes a whole different section of configurations to be filled up which is not consistent with rest of the process. Many docker deployment integrations like Google Container Engine are currently missing, making the whole thing a half-hearted solution.

2. Docker hub integration is non-existent - so you cant directly pull updated docker images from docker hub or other hubs. They contain very well maintained packages, so it is a shame that you'll need to have a custom solution for using them or use static packages instead.

3. Windows-based hosts not supported - Windows have recently announced partnership with Canonical and released docker support on Windows. This is a really great development as it allows cross-platform development on the docker platform, which is essential for enterprises with large user base. But unfortunately Deploybot doesnt support Azure to make full use of this potential. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

1. The clean user interface.

2. The possibility to build assets using Grunt or Gulp.

3. Fast and Reliable, DeployBot instantly detects Git pushes and deploy changes to the server. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

1. I can't access to support and guides from the dashboard.

2. Lack of cloud platforms & hosting providers integrations (Microsoft Azure, Google Cloud, Rackspace, ..)

3. Hope they had "Quick reset" to previous commit.

4. Every time i click login, i have to input everything .. i wish the "remember me" option works properly for me. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

As a Enterprise user of Deploybot, I like a few solid things about it, which are a huge improvement from older softwares that we used to be trained in.

Accidental releases can be avoided and rectified quickly with real-time rollback available in Deploybot. While the deployment is in profess, it can be stopped accidentally as soon as something feels out of place or errors occur during this process. Rollback takes place within 30 seconds, which is a impressive timeframe for me as I have mostly dealt with other tools which can take upto 30 mins for this.

User Access Control is very important for us, as we believe in a strong hierarchy model for protecting access of sensitive/critical content for new recruits. Team leaders have full power of the project assigned to the team and higher administrative staffs have a overview of all projects, but not direct control over them. Deploybot has easy configuration options in their UI to make all this and even more possible. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

The biggest drawback about Deploybot, that our administrators feel is not having the option of hosting it on our own servers. As we have huge number of users and their privileges are already maintained via a different service, having it hosted offline with some way of mass editing user lists is very important to administrators. That also means we wouldn't have to pay per user, but instead by a fixed mass pricing. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

One of the recent docker-based deployment management platform with in-built testing is what best defines Deploybot.

It supports many programming languages like node.js, java, python, coffeescript, etc. out-of-the-box and the default configurations for these languages are very useful to get started with. It is quite easy to start with the defaults and then customize it for more complex scenarios.

It supports many sets of configurations for different branches of code like dev and master, which makes sure that untested or beta code dont get pushed to production. At any org level, this is a critical feature.

Builds are triggered automatically or manually, then build steps can be configured and to my surprise, it doesnt just tell you to write bash scripts but instead reads your project config files to setup/integrate automatically with tools like grunt, gulp and npm. Although it doesnt cover all the tool sets, I hope that'll only get better over time. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

Deploybot is quite nice, but some of its features seem to be limited to only the popular options.

Deployment integrations cover the most popular ones, but Rackspace and Openshift were missing in the list, to my disappointment. Language Support is also limited to a few and if you have a old-ish stack of C++ or even Haskell, you have to work much harder to get things running. Also, notification to mobile via sms or email should be another basic feature that it doesnt have.

Managing teams with different access levels in not possible, making it a insecure option for larger organisations. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

Deploybot is a visual solution for your deployment schedules and records, which can be triggered automatically from code repo and finally deployed auto/manually. It also makes rollback pretty easy when deployments go wrong, along with nice overview of what changed in that deployment.

Things I Like:

1. Huge set of integrations - From code hosting providers (Github, Bitbucket, Gitlab or any git repo) to deployment platforms (FTP, AWS, DO, Heroku, Shopify), they have pretty much all the ground covered for 1-click integration with popular services.

2. Performance monitoring - Each deployment can use monitoring services like New Relic and Bugsnag, which integrates right within the UI to give developers a one-stop place to keep in touch with everything.

3. Auto/Manual deployments - Every code push to master will test and build the code, then either automatically deploy it or queue it for review from user. This is a nifty feature as it allows deploying the push after some manual testing and monitoring to make sure that faulty things dont pass right through the automatic check.

4. Release Notes Management - Prepares automated release note for every push to production and it is shared with everybody in the team.

5. Docker-ised testing - All build code are run within containers, giving you faster startup time and nice separation from the OS. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

1. High Pricing - Basic Plan starts from $15/mo for single user, which is quite a high price for just trying it out.

2. If the deployment integrations dont cover your hosting provider, you are a bit out of luck. Writing shell scripts for that is possible, but quite a pain compared to the 1-click experience.

3. No email notification option alongside chat notification services. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

When it works, it works amazingly. Fast and secure. it takes a boring manually process and makes it easy and fun. Nice that it connects with GitHub and Bitbucket and can also use private keys to connect with multiple servers and environments. Supports Atomic deployments too! Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

Some networking issues have occurred like unable to connect to external services. Error messages could be better. Occasionally the service will be down and it can be hard to get hold of the support team over the weekend. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

Pretty much one-click integration with DigitalOcean was massive for me. I didn't have to set up any additional SSH keys and deploybot was able to set itself up in my environment. (Granted this was more on DO's side, but it's a cool feature nonetheless)

Multiple projects can be setup effortlessly to deploy under certain circumstances (and manually) Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

I dislike that this product became a paid service (even though it's thoroughly worth it for the quality)

For something like this, a free tier was perfect. Review collected by and hosted on G2.com.

What do you like best about DeployHQ?

For basic web sites, Deploybot is extremely easy to get up and running and easy to explain the process to non-developers (like marketing folks). The traceability of deployments is also really nice. Review collected by and hosted on G2.com.

What do you dislike about DeployHQ?

For more complex web applications which have a build pipeline, like compilation, compression, unit testing, etc., Deploybot really falls short since it serves solely as a pipe between source control and deployment environments. Review collected by and hosted on G2.com.