Nixpacksvs
Depot
Depot: Managed remote builds with persistent caching if build speed is the actual problem
Nixpacks
Build system that turns a source directory into an OCI image, now in maintenance mode
As of 31 August 2026, Nixpacks is free to use. Nixpacks inspects a repository, works out the language and toolchain, and produces a container image without a Dockerfile, using Nix for packages and Docker for layers. Softwr lists it under Developer Tools. Nixpacks is made by Railway, available on Linux, macOS, API, Self-hosted.
Overview
What Nixpacks does
Nixpacks is a Rust command line tool from Railway that takes a source directory and emits an OCI image. Language providers detect the project type, pull the toolchain from a pinned nixpkgs archive, and assemble the image in Docker layers. It supports the usual set of runtimes and became widely used beyond Railway itself because it removed the need to write and maintain a Dockerfile per service. It is MIT licensed and has passed 3,500 stars. The fact that should decide the matter is that the project is over. Both the documentation site and the repository README carry a banner saying the project is in maintenance mode and not under active development, and recommending Railpack as a replacement. The last release was version 1.41.0 in October 2025, and the default branch has had no commits since May 2026. Railway rewrote the successor as a BuildKit custom frontend specifically to get fine-grained caching and parallel build steps, which is the architectural gap Nixpacks could not close, and Railway build documentation now covers only Railpack and Dockerfiles. The practical consequence is narrow but real. Existing builds keep working, because a pinned nixpkgs archive keeps resolving. What stops working is the future: a new major version of Node, Python or Bun needs a provider change, and there is nobody merging provider changes. Anyone still running it should read this as a migration item rather than an evaluation, and anyone evaluating build systems should compare Railpack, Cloud Native Buildpacks and a plain Dockerfile instead. The only reason to keep Nixpacks in mind is that a large number of platforms adopted it and their build behaviour is now frozen too.
What people use it 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
Related searches
The honest half
Where it falls short
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about 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.
Cross-shopped
What people choose instead of Nixpacks
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.
- NixpacksvsEarthly
Earthly: Repeatable build definitions when you want explicit build files rather than automatic detection
- NixpacksvsDocker
Docker: A plain Dockerfile remains the option with the largest ecosystem and no deprecation risk
Pricing
What Nixpacks costs
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Nixpacks
Free
- MIT licensed, no usage limits
- No commercial edition and no support contract
- In maintenance mode, superseded by Railpack
Capabilities
Features
Automatic language detection
Providers identify Node, Python, Go, Ruby, PHP, Java, Rust and others from the source tree
No Dockerfile required
Produces an OCI image from a plain source directory
Nix toolchains
Pulls compilers and runtimes from a pinned nixpkgs archive rather than distribution packages
Configuration escape hatches
A nixpacks.toml file overrides install, build and start phases when detection is wrong
Docker layer caching
Reuses unchanged layers between builds
Answered, with sources
Questions people ask
Each answer names the page it came from, so you can check it rather than take our word for it.
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.
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.
What replaces it?
Railpack, also from Railway and also MIT licensed, rebuilt as a BuildKit custom frontend for finer grained caching and parallel steps.
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.
Keep looking
Where to go from Nixpacks
- Nixpacks alternativesEvery product people weigh against it
- Nixpacks pricingPlans, floors and what the tiers exclude
- Nixpacks badgesWhich rules it meets, and the figure behind each
- All Developer Tools softwareThe full category
- Best Developer Tools softwareThe shortlist, and how it was cut
Best Developer Tools software for
Compare Nixpacks with
- Depot
- Earthly
- Cloud Native Buildpacks
- Dagger
- Nx Cloud
- Tilt
- Blacksmith
- WarpBuild
- Namespace
- Rust
- Ona (formerly Gitpod)
- Bazel
- Fig
- Frappe
- Git
- GoLand
- Hookdeck
- JFrog Artifactory
Other Developer Tools software
Specification and tooling that turns source code into OCI images without Dockerfiles
Open source12 researched notesProgrammable CI/CD engine that runs your pipeline as containers on any runner
Free, then $50/mo12 researched notesLocal Kubernetes development loop that rebuilds and live-updates containers on save
Open source12 researched notesA language empowering everyone to build reliable and efficient software
Free plan9 researched notesCloud development environments repositioned as a control plane for software engineering agents
Free, then $20/mo12 researched notesThe Python web framework behind ERPNext, sold as managed hosting through Frappe Cloud
Free, then $5/mo12 researched notesEvent gateway that receives, queues, retries and replays inbound webhooks
Free, then $39/mo12 researched notes
Softwr does not host reviews and shows no star rating for Nixpacks, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
More on Nixpacks
Nixpacks alternatives
What people switch to, and what they give up
Nixpacks pricing
Every tier, and where the cost actually lands
Compare Nixpacks
Put it head to head with anything we hold
Nixpacks badge
Its rating, and an embed for your own site
Best Developer Tools software alternatives
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
quote
Feature flag service priced per flag and environment with unlimited seats and unlimited monthly active users
Per month by feature flag and environment countProgrammable CI/CD engine that runs your pipeline as containers on any runner
Per month per team for Dagger CloudEvent gateway that receives, queues, retries and replays inbound webhooks
Per month by delivered event count
Analytics governance: define a tracking plan, generate typed code from it, and catch drift before release
Per editor seat per month
Kubernetes development and testing automation with shared caching, now owned by Incredibuild
Open source, no licence feeThe Python web framework behind ERPNext, sold as managed hosting through Frappe Cloud
Per month by site or server
Open source internal developer portal framework created and open sourced by Spotify
Open source, no licence fee