Get Advice Icon

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

Cloud 66
Cloud 66

26
21
+ 1
76
Heroku
Heroku

7.5K
5.2K
+ 1
3.1K
Add tool

Cloud 66 vs Heroku: What are the differences?

Developers describe Cloud 66 as "Full Stack Container Management as a Service". Cloud 66 makes Ops easy for developers. It is a single tool built for developers to build, configure and maintain servers and Docker containers on your own servers. On the other hand, Heroku is detailed as "Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience". Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

Cloud 66 and Heroku are primarily classified as "Continuous Deployment" and "Platform as a Service" tools respectively.

Some of the features offered by Cloud 66 are:

  • Provision — build your infrastructure from your code.
  • Backup — peace of mind with regular database backups for all your databases.
  • Security — Simple firewall management & DDoS protection without the stress.

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

  • Agile deployment for Ruby, Node.js, Clojure, Java, Python, Go and Scala.
  • Run and scale any type of app.
  • Total visibility across your entire app.

"Easy provisioning" is the top reason why over 12 developers like Cloud 66, while over 694 developers mention "Easy deployment" as the leading cause for choosing Heroku.

- No public GitHub repository available -
- No public GitHub repository available -

What is Cloud 66?

Cloud 66 makes Ops easy for developers. It is a single tool built for developers to build, configure and maintain servers and Docker containers on your own servers.

What is Heroku?

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
Get Advice Icon

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

Why do developers choose Cloud 66?
Why do developers choose Heroku?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Cloud 66?
What are the cons of using Heroku?
    Be the first to leave a con
    What companies use Cloud 66?
    What companies use Heroku?

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

    What tools integrate with Cloud 66?
    What tools integrate with Heroku?

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

    What are some alternatives to Cloud 66 and Heroku?
    Codeship
    Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.
    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.
    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.
    Spinnaker
    Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
    See all alternatives
    Decisions about Cloud 66 and Heroku
    No stack decisions found
    Interest over time
    Reviews of Cloud 66 and Heroku
    Review ofHerokuHeroku

    I use Heroku, for almost any project of mine. Their free plan is awesome for testing, solo developers or your startup and its almost impossible to not cover you somehow. Adding an add on is a simple command away and I find it easy to use it both on my Windows PC or my Linux laptop. Their documentation, covers almost everything. In particular I have used Heroku for Spring, Django and AngularJS. I even find it easier to run my project on my local dev with foreman start, than ./manage.py runserver (for my django projects). There is no place like Heroku for the developer!

    Review ofHerokuHeroku

    Can't beat the simplicity of deploying and managing apps, the pricing is a bit high, but you are paying for those streamlined tools. However, after several experiences of tracing issues back to Heroku's stack, not having visibility into what they are doing has prompted moving two applications off of it and on to other more transparent cloud solutions. Heroku is amazing for what it is, hosting for early stage products.

    Review ofHerokuHeroku

    I've been using Heroku for 3 years now, they have grown super fast and each time they're improving their services. What I really like the most is how easily you can show to your client the advances on you project, it would take you maximum 15 minutes to configure two environments (Staging/Production). It is simply essential and fantastic!

    Review ofHerokuHeroku

    I liked how easy this was to use and that I could create some proof of concepts without have to pay. The downside for NodeJS is remote debugging. Pretty much have to depend on logging where Azure allows remote debugging with Node Inspector.

    Review ofHerokuHeroku

    Using Heroku takes away all the pains associated with managing compute and backing services. It may require a little extra optimisation and tweaks, but these constraints often make your app better anyway.

    How developers use Cloud 66 and Heroku
    Avatar of StackShare
    StackShare uses HerokuHeroku

    Not having to deal with servers is a huge win for us. There are certainly trade-offs (having to wait if the platform is down as opposed to being able to fix the issue), but we’re happy being on Heroku right now. Being able to focus 100% of our technical efforts on application code is immensely helpful.

    Two dynos seems to be the sweet spot for our application. We can handle traffic spikes and get pretty consistent performance otherwise.

    We have a total of four apps on Heroku: Legacy Leanstack, StackShare Prod, StackShare Staging, StackShare Dev. Protip: if you’re setting up multiple environments based on your prod environment, just run heroku fork app name. Super useful, it copies over your db, add-ons, and settings.

    We have a develop branch on GitHub that we push to dev to test out, then if everything is cool we push it to staging and eventually prod. Hotfixes of course go straight to staging and then prod usually.

    Avatar of StackShare
    StackShare uses HerokuHeroku

    We keep the Metrics tab open while we load test, and hit refresh to see what’s going on: heroku metric

    I would expect the graphs to expand with some sort of detail, but that’s not the case. So these metrics aren’t very useful. The logs are far more useful, so we just keep the tail open while we test.

    Avatar of Tim Lucas
    Tim Lucas uses HerokuHeroku

    Heroku runs the web and background worker processes. Auto-deployments are triggered via GitHub commits and wait for the Buildkite test build to pass. Heroku pipelines with beta release phase execution (for automatically running database migrations) allowed for easy manual testing of big new releases. Web and worker logs are sent to Papertrail.

    Avatar of Jeff Flynn
    Jeff Flynn uses HerokuHeroku

    As much as I love AWS EC, I prefer Heroku for apps like this. Heroku has grown up around Rails and Ruby, massive set of add-ons that are usually one-click setup, and I once had to perform an emergency app scale-up a that I completed in seconds from my mobile phone whilst riding the Bangkok subway. Doesn't get much easier than that.

    Avatar of danlangford
    danlangford uses HerokuHeroku

    With its complimentary SSL (on *.herokuapp.com) we can test everything. Our dev branch is built and deployed out to Heroku. Testing happens out here. not production cause $20/mo is TOO much to pay for the ability to use my own SSL purchased elsewhere.

    How much does Cloud 66 cost?
    How much does Heroku cost?