StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Platform As A Service
  5. AWS CloudFormation vs Heroku

AWS CloudFormation vs Heroku

OverviewDecisionsComparisonAlternatives

Overview

Heroku
Heroku
Stacks25.8K
Followers20.5K
Votes3.2K
AWS CloudFormation
AWS CloudFormation
Stacks1.6K
Followers1.3K
Votes88

AWS CloudFormation vs Heroku: What are the differences?

Developers describe AWS CloudFormation as "Create and manage a collection of related AWS resources". You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work. 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.

AWS CloudFormation belongs to "Infrastructure Build Tools" category of the tech stack, while Heroku can be primarily classified under "Platform as a Service".

Some of the features offered by AWS CloudFormation are:

  • AWS CloudFormation comes with the following ready-to-run sample templates: WordPress (blog),Tracks (project tracking), Gollum (wiki used by GitHub), Drupal (content management), Joomla (content management), Insoshi (social apps), Redmine (project mgmt)
  • No Need to Reinvent the Wheel – A template can be used repeatedly to create identical copies of the same stack (or to use as a foundation to start a new stack)
  • Transparent and Open – Templates are simple JSON formatted text files that can be placed under your normal source control mechanisms, stored in private or public locations such as Amazon S3 and exchanged via email.

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.

"Automates infrastructure deployments" is the primary reason why developers consider AWS CloudFormation over the competitors, whereas "Easy deployment" was stated as the key factor in picking Heroku.

Product Hunt, Soylent, and Code School are some of the popular companies that use Heroku, whereas AWS CloudFormation is used by Expedia.com, TimeHop, and NASA Jet Propulsion Laboratory. Heroku has a broader approval, being mentioned in 1496 company stacks & 938 developers stacks; compared to AWS CloudFormation, which is listed in 195 company stacks and 75 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Heroku, AWS CloudFormation

Alex
Alex

Oct 20, 2020

Decided

I'm transitioning to Render from heroku. The pricing scale matches my usage scale, yet it's just as easy to deploy. It's removed a lot of the devops that I don't like to deal with on setting up my own raw *nix box and makes deployment simple and easy!

Clustering I don't use clustering features at the moment but when i need to set up clustering of nodes and discoverability, render will enable that where Heroku would require that I use an external service like redis.

Restarts The restarts are annoying. I understand the reasoning, but I'd rather watch my service if its got a memory leak and work to fix it than to just assume that it has memory leaks and needs to restart.

101k views101k
Comments
Timothy
Timothy

SRE

Mar 20, 2020

Decided

I personally am not a huge fan of vendor lock in for multiple reasons:

  • I've seen cost saving moves to the cloud end up costing a fortune and trapping companies due to over utilization of cloud specific features.
  • I've seen S3 failures nearly take down half the internet.
  • I've seen companies get stuck in the cloud because they aren't built cloud agnostic.

I choose to use terraform for my cloud provisioning for these reasons:

  • It's cloud agnostic so I can use it no matter where I am.
  • It isn't difficult to use and uses a relatively easy to read language.
  • It tests infrastructure before running it, and enables me to see and keep changes up to date.
  • It runs from the same CLI I do most of my CM work from.
385k views385k
Comments
Daniel
Daniel

May 4, 2020

Decided

Because Pulumi uses real programming languages, you can actually write abstractions for your infrastructure code, which is incredibly empowering. You still 'describe' your desired state, but by having a programming language at your fingers, you can factor out patterns, and package it up for easier consumption.

426k views426k
Comments

Detailed Comparison

Heroku
Heroku
AWS CloudFormation
AWS CloudFormation

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.

You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.

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.;Erosion-resistant architecture. Rich control surfaces.
AWS CloudFormation comes with the following ready-to-run sample templates: WordPress (blog),Tracks (project tracking), Gollum (wiki used by GitHub), Drupal (content management), Joomla (content management), Insoshi (social apps), Redmine (project mgmt);No Need to Reinvent the Wheel – A template can be used repeatedly to create identical copies of the same stack (or to use as a foundation to start a new stack);Transparent and Open – Templates are simple JSON formatted text files that can be placed under your normal source control mechanisms, stored in private or public locations such as Amazon S3 and exchanged via email.;Declarative and Flexible – To create the infrastructure you want, you enumerate what AWS resources, configuration values and interconnections you need in a template and then let AWS CloudFormation do the rest with a few simple clicks in the AWS Management Console, via the command line tools or by calling the APIs.
Statistics
Stacks
25.8K
Stacks
1.6K
Followers
20.5K
Followers
1.3K
Votes
3.2K
Votes
88
Pros & Cons
Pros
  • 703
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
Cons
  • 27
    Super expensive
  • 9
    Not a whole lot of flexibility
  • 7
    No usable MySQL option
  • 7
    Storage
  • 5
    Low performance on free tier
Pros
  • 43
    Automates infrastructure deployments
  • 21
    Declarative infrastructure and deployment
  • 13
    No more clicking around
  • 3
    Infrastructure as code
  • 3
    Any Operative System you want
Cons
  • 4
    Brittle
  • 2
    No RBAC and policies in templates
Integrations
Mailgun
Mailgun
Postmark
Postmark
Loggly
Loggly
Papertrail
Papertrail
Redis Cloud
Redis Cloud
Red Hat Codeready Workspaces
Red Hat Codeready Workspaces
Nitrous.IO
Nitrous.IO
Logentries
Logentries
MongoLab
MongoLab
Gemfury
Gemfury
No integrations available

What are some alternatives to Heroku, AWS CloudFormation?

Clever Cloud

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Google App Engine

Google App Engine

Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.

Red Hat OpenShift

Red Hat OpenShift

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

AWS Elastic Beanstalk

AWS Elastic Beanstalk

Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

Render

Render

Render is a unified platform to build and run all your apps and websites with free SSL, a global CDN, private networks and auto deploys from Git.

Hasura

Hasura

An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.

Cloud 66

Cloud 66

Cloud 66 gives you everything you need to build, deploy and maintain your applications on any cloud, without the headache of dealing with "server stuff". Frameworks: Ruby on Rails, Node.js, Jamstack, Laravel, GoLang, and more.

Jelastic

Jelastic

Jelastic is a Multi-Cloud DevOps PaaS for ISVs, telcos, service providers and enterprises needing to speed up development, reduce cost of IT infrastructure, improve uptime and security.

Dokku

Dokku

It is an extensible, open source Platform as a Service that runs on a single server of your choice. It helps you build and manage the lifecycle of applications from building to scaling.

PythonAnywhere

PythonAnywhere

It's somewhat unique. A small PaaS that supports web apps (Python only) as well as scheduled jobs with shell access. It is an expensive way to tinker and run several small apps.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot