Softwr

Web Development · head to head

Drupal vs Nixpacks

D

Drupal

Web Development

Open-source CMS for complex, structured content sites

From
Free
Free plan
Yes
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

  • Each has a real cost: Drupal steep learning curve: concepts that are implicit in WordPress are explicit and must be configured; 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: Drupal covers Structured content modelling, Nixpacks covers Automatic language detection.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Drupal and Nixpacks actually diverge.

Attributes where Drupal and Nixpacks differ
AttributeDrupalNixpacks
PlatformsWeb, Linux, Self-hostedLinux, macOS, CLI, Docker
CategoryWeb DevelopmentDeveloper Tools

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 Drupal

  • Structured content modelling
  • Granular permissions
  • Multilingual
  • Views

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.

Drupal

  • Government and university sites with complex content models and strict permissionsnot Nixpacks
  • Multilingual sites where translation is structural rather than a pluginnot Nixpacks
  • Publishers needing custom content types and editorial workflownot Nixpacks

Nixpacks

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

Where each one falls short

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

Drupal

  • Steep learning curve: concepts that are implicit in WordPress are explicit and must be configured
  • Smaller developer pool than WordPress, and correspondingly higher build costs
  • Major version upgrades have historically been substantial projects, not routine updates
  • Considerably more machinery than a straightforward marketing site needs

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

Drupal

Free
  • DrupalFree
    • Full functionality
    • Commercial use permitted
    • Community support

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 Drupal if

  • You need structured content modelling.
  • You want to start without paying.
  • You work on Web, Linux, Self-hosted.
  • You also want granular permissions.
Drupal 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 Drupal or Nixpacks better?
Neither clearly leads. Drupal starts at Free and Nixpacks at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Drupal or Nixpacks?
Drupal starts at Free and Nixpacks at Free.
Does Drupal or Nixpacks run on more platforms?
Drupal runs on Web, Linux, Self-hosted. Nixpacks runs on Linux, macOS, CLI, Docker.
Can I use Drupal for free?
Both have a free tier, so you can try either at no cost before committing.
What is Drupal best used for?
Drupal is most often used for government and university sites with complex content models and strict permissions, multilingual sites where translation is structural rather than a plugin, publishers needing custom content types and editorial workflow. Of those, government and university sites with complex content models and strict permissions and multilingual sites where translation is structural rather than a plugin are not what Nixpacks is typically brought in for.
What can Drupal do that Nixpacks cannot?
Drupal covers Structured content modelling, Granular permissions, Multilingual, Views. Nixpacks covers Automatic language detection, No Dockerfile required, Nix toolchains, Configuration escape hatches.

Answered from the vendors’ own pages

Drupal: Is Drupal free?

Yes, open source under the GPL. Costs are hosting, development and any commercial modules.

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.

Drupal: Drupal or WordPress?

WordPress is faster to launch, cheaper to staff and has a much larger plugin ecosystem. Drupal is stronger when the content model is genuinely complex and permissions are strict, which is why institutions favour it.

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.

Drupal: Why is Drupal common in government and universities?

Structured content modelling, granular access control and multilingual support are core rather than bolted on, and those are exactly the requirements those sectors have.

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 Drupal

More on Nixpacks

Keep looking

Other head to heads