Softwr

Software · head to head

Heroku vs Palo Alto Networks

Heroku logo

Heroku

Software

Cloud Application Platform

From
$7/month
Rated
-
Palo Alto Networks logo

Palo Alto Networks

Software

Enterprise cybersecurity platform

From
On request
Rated
-

The short version

  • Each has a real cost: Heroku there is no free dyno tier; the cheapest Eco dyno is $5 per month; Palo Alto Networks enterprise-focused pricing model
  • They diverge on capability: Heroku covers Git-based deployment, Palo Alto Networks covers Advanced threat prevention.

Where they differ

Only the attributes on which Heroku and Palo Alto Networks actually diverge.

Attributes where Heroku and Palo Alto Networks differ
AttributeHerokuPalo Alto Networks
Starting price$7/monthOn request
PlatformsWeb, Api, WorkersCloud, On-premises, Hybrid
Founded20072005

Identical on both: pricing model (subscription), free tier (No), 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 Palo Alto Networks

  • Advanced threat prevention
  • Threat detection and response
  • Cloud security
  • Endpoint protection
  • Network security
  • API protection
  • Incident response
  • Threat intelligence

Both cover

  • Cloud deployment
  • Web support

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 Palo Alto Networks
  • Running managed Postgres, Redis and Kafka as attached data servicesnot Palo Alto Networks
  • Isolated production environments in a Private Space for regulated workloadsnot Palo Alto Networks

Palo Alto Networks

  • Enterprise network security and threat protectionnot Heroku
  • Cloud-native application protectionnot Heroku
  • Identity and access securitynot Heroku
  • Security operations and incident responsenot 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

Palo Alto Networks

  • Enterprise-focused pricing model
  • Complex implementation required

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

Palo Alto Networks

On request
  • Enterprise$undefined/year
    • Threat prevention
    • Detection and response
    • Cloud security

Which should you pick?

Choose Heroku if

  • You need git-based deployment.
  • You work on Web, Api, Workers.
  • You also want buildpacks.

Choose Palo Alto Networks if

  • You need advanced threat prevention.
  • You work on Cloud, On-premises, Hybrid.
  • You also want threat detection and response.

Questions people ask

Is Heroku or Palo Alto Networks better?
Neither clearly leads. Heroku starts at $7/month and Palo Alto Networks at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Heroku or Palo Alto Networks?
Heroku starts at $7/month and Palo Alto Networks at On request.
Does Heroku or Palo Alto Networks run on more platforms?
Heroku runs on Web, Api, Workers. Palo Alto Networks runs on Cloud, On-premises, Hybrid.
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 Palo Alto Networks is typically brought in for.
What can Heroku do that Palo Alto Networks cannot?
Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace. Palo Alto Networks covers Advanced threat prevention, Threat detection and response, Cloud security, Endpoint protection. Both handle Cloud deployment, Web support.

Related pages

Other head to heads