Need advice about which tool to choose?Ask the StackShare community!

DeployBot

93
91
+ 1
74
Deployer

52
73
+ 1
21
Add tool

DeployBot vs Deployer: What are the differences?

DeployBot: Instantly deploy from Github, Bitbucket, or Gitlab without complex scripts, commands or configs. DeployBot makes it simple to deploy your work anywhere. You can compile or process your code in a Docker container on our infrastructure, and we'll copy it to your servers once everything has been successfully built; Deployer: Deployment Tool for PHP. A deployment tool written in PHP with support for popular frameworks out of the box.

DeployBot and Deployer can be categorized as "Continuous Deployment" tools.

Some of the features offered by DeployBot are:

  • Manually deploy with a click in the app, automatically deploy on each push, or use deploy tags in a commit [deploy:production].
  • DeployBot gathers new and changed files from your repositories since the last deployment. You can even preview the changes first.
  • Files are uploaded, SSH commands are executed and deployment hooks are triggered. Everything is logged for you.

On the other hand, Deployer provides the following key features:

  • Simple setup process and a minimal learning curve
  • Ready to use recipes for most frameworks
  • Parallel execution without extensions

"Easy setup" is the primary reason why developers consider DeployBot over the competitors, whereas "Simply to use" was stated as the key factor in picking Deployer.

Deployer is an open source tool with 6.93K GitHub stars and 986 GitHub forks. Here's a link to Deployer's open source repository on GitHub.

According to the StackShare community, DeployBot has a broader approval, being mentioned in 37 company stacks & 6 developers stacks; compared to Deployer, which is listed in 8 company stacks and 5 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of DeployBot
Pros of Deployer
  • 26
    Easy setup
  • 20
    Seamless integrations
  • 17
    Free
  • 10
    Rocks
  • 1
    Docker
  • 8
    Simply to use
  • 7
    Easy to customize
  • 6
    Easy setup

Sign up to add or upvote prosMake informed product decisions

Cons of DeployBot
Cons of Deployer
  • 1
    Not reliable
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is DeployBot?

    DeployBot makes it simple to deploy your work anywhere. You can compile or process your code in a Docker container on our infrastructure, and we'll copy it to your servers once everything has been successfully built.

    What is Deployer?

    A deployment tool written in PHP with support for popular frameworks out of the box

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention DeployBot and Deployer as a desired skillset
    What companies use DeployBot?
    What companies use Deployer?
    See which teams inside your own company are using DeployBot or Deployer.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with DeployBot?
    What tools integrate with Deployer?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to DeployBot and Deployer?
    Beanstalk
    A single process to commit code, review with the team, and deploy the final result to your customers.
    DeployHQ
    A service packed with features to help you automate and manage the continuous deployment of your websites.
    Jenkins
    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
    Buddy
    Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.
    AWS CodePipeline
    CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
    See all alternatives