CloudBees vs Engine Yard Cloud

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

CloudBees

95
164
+ 1
6
Engine Yard Cloud

27
36
+ 1
7
Add tool

CloudBees vs Engine Yard Cloud: What are the differences?

Developers describe CloudBees as "Enterprise Jenkins and DevOps". Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud. On the other hand, Engine Yard Cloud is detailed as "Deploy and scale Rails applications in the cloud". The Engine Yard Platform as a Service (PaaS) is a product family that leverages open source technologies to orchestrate and automate the configuration, deployment and management of applications on multiple infrastructures.

CloudBees and Engine Yard Cloud can be categorized as "Platform as a Service" tools.

Some of the features offered by CloudBees are:

  • Hosted CI/CD as a Service
  • Flexible and governed software delivery automation
  • Starter Kit

On the other hand, Engine Yard Cloud provides the following key features:

  • Dedicated, secure, commercial-grade platform that increases agility
  • Focus on your code - not on operations or platform maintenance
  • Scale cloud applications and infrastructure rapidly

ChallengePost, Firecracker, and CoolWorks are some of the popular companies that use Engine Yard Cloud, whereas CloudBees is used by Netflix, Randstad, and Watchguard Technologies, Inc.. Engine Yard Cloud has a broader approval, being mentioned in 8 company stacks & 4 developers stacks; compared to CloudBees, which is listed in 3 company stacks and 4 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of CloudBees
Pros of Engine Yard Cloud
  • 6
    Jenkins
  • 6
    Great customer support
  • 1
    Simple deployment

Sign up to add or upvote prosMake informed product decisions

What is CloudBees?

Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.

What is Engine Yard Cloud?

The Engine Yard Platform as a Service (PaaS) is a product family that leverages open source technologies to orchestrate and automate the configuration, deployment and management of applications on multiple infrastructures.

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

What companies use CloudBees?
What companies use Engine Yard Cloud?
See which teams inside your own company are using CloudBees or Engine Yard Cloud.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with CloudBees?
What tools integrate with Engine Yard Cloud?

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

Blog Posts

GitCloudBees+2
3
4435
Git.NETCloudBees+3
6
1066
What are some alternatives to CloudBees and Engine Yard Cloud?
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.
CircleCI
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
GitLab
GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
See all alternatives