Softwr

Developer Tools · head to head

Nixpacks vs Preact

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
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Nixpacks covers Automatic language detection, Preact covers 3kB runtime.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nixpacks and Preact actually diverge.

Attributes where Nixpacks and Preact differ
AttributeNixpacksPreact
PlatformsLinux, macOS, CLI, DockerWeb
CategoryDeveloper ToolsWeb Development

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), 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 Nixpacks

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

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What people use each for

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

Nixpacks

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

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Nixpacks
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Nixpacks
  • Applications targeting low-bandwidth or low-powered devicesnot Nixpacks

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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.

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

Pricing, plan by plan

Nixpacks

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

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

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

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.
Preact review

Questions people ask

Is Nixpacks or Preact better?
Neither clearly leads. Nixpacks starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nixpacks or Preact?
Nixpacks starts at Free and Preact at Free.
Does Nixpacks or Preact run on more platforms?
Nixpacks runs on Linux, macOS, CLI, Docker. Preact runs on Web.
Can I use Nixpacks for free?
Both have a free tier, so you can try either at no cost before committing.
What is Nixpacks best used for?
Nixpacks is most often used for understanding the build behaviour of a platform that adopted nixpacks before it was frozen, producing container images from a polyglot monorepo where nobody wants to own several dockerfiles, reproducing an existing railway build locally while planning a migration to railpack, comparing what a nix based builder does differently from a buildpack before choosing a successor. Of those, understanding the build behaviour of a platform that adopted nixpacks before it was frozen and producing container images from a polyglot monorepo where nobody wants to own several dockerfiles are not what Preact is typically brought in for.
What can Nixpacks do that Preact cannot?
Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

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.

Preact: Is Preact free?

Yes, open source under the MIT licence.

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.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

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.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

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 Nixpacks

More on Preact

Keep looking

Other head to heads