Softwr

Cloud · head to head

Heroku vs Nixpacks

Heroku logo

Heroku

Cloud

Cloud Application Platform

From
$5/month
Free plan
No
Full reviewWebsite
Nixpacks logo

Nixpacks

Developer Tools

Build system that turns a source directory into an OCI image, now in maintenance mode

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Only Nixpacks 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; Nixpacks the project is in maintenance mode with no commits on the default branch since May 2026 and no release since October 2025, so support for new language versions arrives only if someone forks it.
  • They diverge on capability: Heroku covers Git-based deployment, Nixpacks covers Automatic language detection.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Heroku and Nixpacks actually diverge.

Attributes where Heroku and Nixpacks differ
AttributeHerokuNixpacks
Starting price$5/monthFree
Pricing modelsubscriptionOpen source, no licence fee
Free tierNoYes
PlatformsWeb, Api, WorkersLinux, macOS, CLI, Docker
CategoryCloudDeveloper Tools
Founded2007Unknown

Identical on both: user rating (Not yet rated).

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 Nixpacks

  • Automatic language detection
  • No Dockerfile required
  • Nix toolchains
  • Configuration escape hatches
  • Docker layer caching

What people use each for

The jobs each tool is most often brought in to do.

Heroku

  • Application hostingnot Nixpacks
  • Database as a servicenot Nixpacks
  • CI/CD pipelinesnot Nixpacks
  • API deploymentnot Nixpacks

Nixpacks

  • Understanding the build behaviour of a platform that adopted Nixpacks before it was frozennot Heroku
  • Producing container images from a polyglot monorepo where nobody wants to own several Dockerfilesnot Heroku
  • Reproducing an existing Railway build locally while planning a migration to Railpacknot Heroku
  • Comparing what a Nix based builder does differently from a buildpack before choosing a successornot 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

Nixpacks

  • The project is in maintenance mode with no commits on the default branch since May 2026 and no release since October 2025, so support for new language versions arrives only if someone forks it.
  • Build determinism is softer than it appears, because providers pin a nixpkgs archive commit and bumping that archive silently moves compiler and runtime versions underneath a build that looks unchanged.
  • Caching is limited to Docker layers rather than a content addressed graph, so a small change early in the build invalidates everything after it, which is exactly the limitation Railpack was rewritten to fix.
  • Images carry Nix store layers and come out larger than an equivalent tuned Dockerfile or buildpack output, which costs registry storage and slows cold pulls on scale-out.
  • There is no specification, no vendor neutral governance and no third party provider ecosystem, so a single company was able to redirect strategy and leave every downstream user with a frozen build tool.

Pricing, plan by plan

Heroku

$5/month
  • Eco Dyno$5/month
    • 0.5 GB RAM
    • Git/Docker deploy
    • Custom domains
  • Basic Dyno$7/month
    • 0.5 GB RAM
    • Always-on
    • Free SSL
  • Standard-1X Dyno$25/month
    • 0.5 GB RAM
    • Horizontal scaling
    • App metrics
  • Standard-2X Dyno$50/month
    • 1 GB RAM
    • Horizontal scaling
    • App metrics

Nixpacks

Free
  • NixpacksFree
    • MIT licensed, no usage limits
    • No commercial edition and no support contract
    • In maintenance mode, superseded by Railpack

Which should you pick?

Choose Heroku if

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

Choose Nixpacks if

  • You need automatic language detection.
  • You want to start without paying.
  • You work on Linux, macOS, CLI, Docker.
  • You also want no dockerfile required.
Nixpacks review

Questions people ask

Is Heroku or Nixpacks better?
Neither clearly leads. Heroku starts at $5/month and Nixpacks at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Heroku or Nixpacks?
Nixpacks has a free tier; the other does not. Paid plans start at $5/month for Heroku and Free for Nixpacks.
Does Heroku or Nixpacks run on more platforms?
Heroku runs on Web, Api, Workers. Nixpacks runs on Linux, macOS, CLI, Docker.
Can I use Nixpacks for free?
Yes. Nixpacks has a free tier, so you can try it without paying. Heroku starts at $5/month.
What is Heroku best used for?
Heroku is most often used for application hosting, database as a service, ci/cd pipelines, api deployment. Of those, application hosting and database as a service are not what Nixpacks is typically brought in for.
What can Heroku do that Nixpacks cannot?
Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace. Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches.

Answered from the vendors’ own pages

Heroku: How much does Heroku cost?

Heroku dyno pricing starts at $5 per month USD for the Eco tier (with 30-minute inactivity sleep), $7 per month for Basic (always-on), and scales up to $1,500 per month for Performance-2XL with 126 GB RAM.

Source
Nixpacks: Should I start a new project on Nixpacks?

No. The documentation and README both say it is in maintenance mode and recommend Railpack. Choose Railpack, Cloud Native Buildpacks or a Dockerfile instead.

Heroku: What is the cheapest always-on Heroku plan?

The Basic Dyno at $7 per month USD is Heroku's cheapest always-on container option. It provides 0.5 GB RAM, free SSL, and support for 10 process types.

Source
Nixpacks: Will my existing Nixpacks builds stop working?

Not immediately. Pinned nixpkgs archives keep resolving, so builds continue. What you lose is support for new runtime major versions and any fix for a provider bug.

Heroku: How is Heroku Postgres priced?

Heroku Postgres Essential tier (shared resources) starts at $5-$20 per month for 1-32 GB disk. Standard tier (dedicated) ranges $50-$12,000 per month. Premium, Private, Shield, and Advanced tiers offer higher performance at corresponding prices.

Source
Nixpacks: What replaces it?

Railpack, also from Railway and also MIT licensed, rebuilt as a BuildKit custom frontend for finer grained caching and parallel steps.

Nixpacks: Is it still open source?

Yes, MIT, and the repository is not archived. Being open source does not help much when nobody is merging provider updates.

Share

Related pages

More on Heroku

More on Nixpacks

Keep looking

Other head to heads