Software · head to head
Heroku vs Puppet
The short version
- Only Puppet has a free tier, so it costs nothing to try first.
- Each has a real cost: Heroku there is no free dyno tier; the cheapest Eco dyno is $5 per month; Puppet the pricing page publishes no rate and no minimum, and asks you to fill in a form to be sent pricing and plan information
- They diverge on capability: Heroku covers Git-based deployment, Puppet covers Manifests.
Where they differ
Only the attributes on which Heroku and Puppet actually diverge.
Identical on both: user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Heroku
- Git-based deployment
- Buildpacks
- Dynos (containers)
- Add-ons marketplace
- Postgres database
- Environment variables
- Logging
- API
Only in Puppet
- Manifests
- Modules
- Classes
- Variables
- Facts
- Puppet Master
- Hiera
- Facter
Both cover
- Cloud deployment
What people use each for
The jobs each tool is most often brought in to do.
Heroku
- Deploying and scaling web applications with git push and no server administrationnot Puppet
- Running managed Postgres, Redis and Kafka as attached data servicesnot Puppet
- Isolated production environments in a Private Space for regulated workloadsnot Puppet
Puppet
- Declarative configuration management of servers at scalenot Heroku
- Enforcing infrastructure compliance policy continuouslynot Heroku
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Heroku
- There is no free dyno tier; the cheapest Eco dyno is $5 per month
- Eco dynos sleep after 30 minutes of inactivity, are restricted to personal accounts and allow only 2 process types
- Free SSL and 10 process types start at the Basic dyno at $7 per month
- Private and Shield dyno types require a Private Space, which is billed on top of the dynos
- Private Space dynos start at $250 per month for Private-M and $500 per month for Private-L
- Dyno prices are per dyno per month, so an app with several process types multiplies the bill
Puppet
- The pricing page publishes no rate and no minimum, and asks you to fill in a form to be sent pricing and plan information
- Pricing is banded by number of managed nodes, with separate tiers for under 25 nodes and 25 or more nodes
- The product is split into Puppet Enterprise and a higher Puppet Enterprise Advanced edition, so compliance oriented features sit behind the upper tier
Pricing, plan by plan
Heroku
$7/month- Hobby$7/month
- 512MB RAM
- Shared CPU
- 1 web dyno
- Standard$50/month
- 512MB RAM
- Dedicated CPU
- Automatic scaling
Puppet
Free- Open SourceFree
- Puppet Agent
- Community support
- Full DSL
- Puppet Enterprise$100/month
- Puppet Server
- Console
- RBAC
Which should you pick?
Choose Heroku if
- You need git-based deployment.
- You work on Web, Api, Workers.
- You also want buildpacks.
Choose Puppet if
- You need manifests.
- You want to start without paying.
- You work on Linux, Windows, Mac, Api.
- You also want modules.
Questions people ask
- Is Heroku or Puppet better?
- Neither clearly leads. Heroku starts at $7/month and Puppet at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Heroku or Puppet?
- Puppet has a free tier; the other does not. Paid plans start at $7/month for Heroku and Free for Puppet.
- Does Heroku or Puppet run on more platforms?
- Heroku runs on Web, Api, Workers. Puppet runs on Linux, Windows, Mac, Api.
- Can I use Puppet for free?
- Yes. Puppet has a free tier, so you can try it without paying. Heroku starts at $7/month.
- What is Heroku best used for?
- Heroku is most often used for deploying and scaling web applications with git push and no server administration, running managed postgres, redis and kafka as attached data services, isolated production environments in a private space for regulated workloads. Of those, deploying and scaling web applications with git push and no server administration and running managed postgres, redis and kafka as attached data services are not what Puppet is typically brought in for.
- What can Heroku do that Puppet cannot?
- Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace. Puppet covers Manifests, Modules, Classes, Variables. Both handle Cloud deployment.
Related pages
Keep looking
Other head to heads
- Heroku vs Grafana Cloud
- Heroku vs Neon
- Heroku vs DigitalOcean
- Heroku vs AWS (Amazon Web Services)
- Heroku vs Lambda (AWS Serverless)
- Heroku vs Deno Deploy
- Heroku vs Hetzner Cloud
- Heroku vs Linode
- Heroku vs Packer
- Heroku vs Pulumi
- Heroku vs Render
- Heroku vs Upstash
- Heroku vs Vagrant
- Heroku vs Vultr
- Heroku vs Akamai
- Heroku vs Alibaba Cloud
- Heroku vs Chef
- Heroku vs Contabo
- Puppet vs Grafana Cloud
- Puppet vs Neon
- Puppet vs DigitalOcean
- Puppet vs AWS (Amazon Web Services)
- Puppet vs Lambda (AWS Serverless)
- Puppet vs Deno Deploy
- Puppet vs Hetzner Cloud
- Puppet vs Linode
- Puppet vs Packer
- Puppet vs Pulumi
- Puppet vs Render
- Puppet vs Upstash
- Puppet vs Vagrant
- Puppet vs Vultr
- Puppet vs Akamai
- Puppet vs Alibaba Cloud
- Puppet vs Chef
- Puppet vs Contabo


