When comparing Cloud 66 vs Shippable, the Slant community recommends Shippable for most people. In the question“What are the best continuous deployment services?” Shippable is ranked 9th while Cloud 66 is ranked 11th. The most important reason people chose Shippable is:
The fact that Shippable runs inside of Docker means that it keeps a persistent state and every build will not have to revert to initial state where it needs to install every dependency from the ground up. Classic CI tools that run on virtual machines need to reset their environment every time and every time install the gems, packages and services needed.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Integrations
Integrated with major Data services: MySQL, PostgreSQL, MongoDB, Redis, Memcached, ElasticSearch.
Pro Cloud 66 Prepress
Cloud 66 Prepress builds and deploys static (Jamstack) websites to your own cloud account. Prepress supports AWS, Google Cloud, DigitalOcean, Azure and Linode. With detailed logging, automated SSL certificates and custom domains, Prepress is everything you need to deploy your static site to your account on all major cloud providers. Cloud 66 supports the following static site generators: Hugo, Gatsby, Jekyll, Next.js, Vue.js, Nuxt.js, Svelte, Middleman, and Docusaurus, with more generators on the way.
Pro Features
Failover Groups, Command line and API, LiveLogs, ActiveProtect, Infrastructure Inventory, Team Access Control, Deployment Engine, BuildGrid, ContainerNet, Backups and Replications, Database Management and more.
Pro Frameworks
Ruby on Rails, Node.js, Jamstack (Jekyll, Hugo, Gatsby, Next.js, Vue.js, Nuxt.js, Svelte, Middleman, and Docusaurus), Laravel, GoLang, and more.
Pro Teams
Unlimited team members at no extra cost, with fine-grained control over permissions and roles. Multi-organization support.
Pro Run anywhere
Deploy Cloud 66 to any cloud provider or your own server.
Pro Cloud 66 Maestro
Cloud 66 Maestro offers a full stack container management service backed up by Kubernetes. You can deploy any application (any language, any framework) to any cloud, as long as you have a Dockerfile. With support for containers and complete with support for non-container parts of your infrastructure including firewalls and network, databases (provisioning, monitoring, backups, and replication), security and ACL access control, OS and server-level security monitoring, deployment workflow management, and native DB and storage components and more.
Pro Deployment
Supports rolling, parallel, blue/green, and canary deployment strategies and full deployment history with easy rollbacks.
Pro Cloud 66 for Rails
Cloud 66 for Rails builds, manages and maintains your Rails applications that can be deployed to any cloud provider or to your own server. It helps you scale your database with master-slave replication, without having to make any configuration changes. You can add back-ups, load balancers and de-commission servers with a single click.
Pro Rails, Node and Container
Cloud 66 for Rails Cloud 66 for Rails allows you to focus on your app while we take care of everything you need to build, deploy and maintain your Ruby applications (including deployments of Rails and Rack frameworks). Cloud 66 for Rails helps you scale your database with master-slave replication, without having to make any configuration changes. You can add back-ups, load balancers and de-commission servers with a single click. Cloud 66 for Node Cloud 66 for Node allows developers a pain free deployments in three easy steps. First connect Cloud 66 to your Git repository, then to the cloud provider of your choice and lastly deploy. Spend more time on developing your Node app and less time configuration the boxes. Secure. Robust. Production ready. Scale as you need. Cloud 66 for Containers: Cloud 66 for Containers offers a full stack container management. A complete solution for building, running and maintaining containerized applications in production Build your image or bring your own image, deploy and manage. Depending on your needs.
Pro Security
Provides simple firewall management, stress-free DDoS protection, and powerful account security tools.
Pro Scales easily
Scaling your web, database, and process servers with the click of a button. Easy to scale vertically or horizontally, manage the workers' lifecycle and pin or move the workers to specific servers.
Pro Docker integration
A complete toolkit for deploying containers in production. Build your image or bring your own image, deploy, manage and maintain.
Pro Builds are faster
The fact that Shippable runs inside of Docker means that it keeps a persistent state and every build will not have to revert to initial state where it needs to install every dependency from the ground up. Classic CI tools that run on virtual machines need to reset their environment every time and every time install the gems, packages and services needed.
Pro GitHub and Bitbucket integration
Shippable supports both BitBucket and GitHub. Repositories uploaded on either of those services can be built using Shippable.
Pro Free plan available
Unlimited builds for unlimited public repos and up to 5 private repositories.
Pro Docker integration
Shippable is built using Docker, a popular open source Linux container. It was originally built using it's own container but when that started to become too complex, they switched to using Docker. Since the beginning Shippable was different from other CI tools because while Shippable uses a container (Docker), traditionally CI tools have used virtual machines to manage their workloads.
Pro Quick setup
All Shippable needs for it's setup is a shippable.yml
file in the root of the repository that needs to be built. The bare minimum Shippable needs is the language and the version number specified in that file.
Pro Integrated code coverage and test results visualization
No need to use coveralls or any other tool for code coverage visualization. Code coverage and test results are integrated into the product.
Pro Build as Code
Builds are described in the shippable.yml file located in the root of your project. This empowers engineers to take responsibility for code delivery. If you are coming from Travis CI, Shippable reads your .travis.yml file directly so you can try it out painlessly.
Pro Build on your own host
Teams can set up Docker containers on their own servers and run Shippable in there.
Pro Supports monitoring and tracking utilization and system performance for your devops automation infrastructure
Pro Cheaper than competitors
Plans are significantly cheaper than competitors.
Pro Testing against multiple runtimes, versions and environments
Supports builds against multiple runtimes, environment variables, and platforms.
Pro 2X faster than any other platform
The accuracy & speed is 2x more compared to all the other available CI & CD platforms.
Cons
Con Requires way to much permissions when logging in using Bitbucket
It even requests the permission to "Delete your repositories".
Con No Direct Deploy to S3
Currently, Shippable does not allow for build artifacts to be natively deployed to S3. This can be gotten around, however it is a rather large hole when compared to Travis.
In order to deploy to S3 you have to add a couple of lines to the yml file. For example:
env:
global:
#secure variable contains values for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
- secure: HKwYujx/qmsyQQdHvR2myu8HLUDtcLeDyYV149YJuxIV4J7Hk3SxeY8X3D6aTlR8mvMnd/ZFY+tGNUh4G0xtLLjjZcPsBgvFlB
build:
on_success:
- aws s3 sync $SHIPPABLE_BUILD_DIR "s3://bucket_name" --region "us-east-1"
Con Docker security measures may be a hindrance
Shippable runs inside Docker containers. Docker has some specific security measures which may or may not become a hindrance in using Shippable. It may be harder for users who are not very comfortable with a Linux container environment and that can create some security problems. Even for more advanced users, it's still something more that they have to address while using Shippable.
