Self-hosted service
railwayapp/nixpacks avatar
railwayapp/nixpacks

Nixpacks calls itself early stage while its version is 1.41.0

App source + Nix packages + Docker = Image

3,558 stars321 forksRustMIT

At a glance

What is it?
Nixpacks turns a source directory into an OCI image using packages from the Nix ecosystem. Its README declares maintenance mode and recommends a replacement, then describes the project as very early stage with no stable release in sight.
Who is it for?
Nixpacks fits a Railway user who already depends on its generated builds and has no reason to migrate today.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 46 days ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 16, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • railwayapp/nixpacks3,558 ★ · +3
Star history
Repository2026-09-242026-11-16
railwayapp/nixpacks3.6k3.6k

3 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A banner recommending something else

The first line of substance in the file is a maintenance notice. The project is in maintenance mode, the README states that development of it has stopped, and a different tool by the same organisation is recommended as its replacement. Everything after that notice reads as a description of what the thing does rather than an invitation to build on it. The commit record adds a wrinkle worth knowing before you plan around either signal: the last commit to the default branch is dated two days before this repository snapshot, while the newest release tag is from the autumn of the previous year. So the branch is still receiving work while the release history has been quiet for about eleven months, which is what maintenance mode with an active triage looks like rather than a frozen repository.

Early stage, at version 1.41.0

The contributing section carries its own caveat, and it does not agree with the version number. Contributions are welcome, it says, with the big caveat that this is a very early stage project and that implementation details and the API will most likely change between now and a stable release. That paragraph reads as though it were written for version zero. The manifest, meanwhile, declares version 1.41.0, matching the newest tag. So a contributor reading the contributing guide is warned that the interface is unstable before a stable release exists, while the package they install is on its forty-first minor line. That contradiction is not harmful on its own, but it is a fair signal that the project's own communication has not been revisited since the two eras.

Source in one side, an image out the other

The mechanism is one sentence: a source directory goes in and an OCI compliant image comes out, deployable anywhere. The origin story explains the design choices. The project was started by the hosting platform's team as an alternative to the buildpack approach, and it exists to address the problems that appeared when deploying thousands of user applications on that platform. The change it makes is about where dependencies come from: system and language dependencies are pulled from the Nix ecosystem rather than being installed by a language-specific script the platform has to trust. Everything else in the repository, the plan generation, the example fixtures and the snapshot tests, is machinery for deciding what that one image should contain.

Debugging works by rewriting the generated script

The build file has a set of single-target commands for working on one example, and the last of them is the most revealing. The first two check that the target directory exists and stop with an error if it does not, then run the tool to build that one example. The third does the same, but then takes the build script the tool just generated, rewrites one line of it with a text substitution that swaps a plain container build for an experimental build command with a debug subcommand, and evaluates the result in the shell. So the debugging path is not a flag in the program. It is a generated shell script, edited after the fact, because the generation step is where the interesting content is. Anyone writing a new debugging affordance should start by asking whether editing the script would be simpler.

The examples directory is the test matrix

The repository carries an examples directory with dozens of directories, one per stack, and that directory is what the test commands target. The names are the coverage list: several Clojure variants distinguished by build tool and language version, three COBOL layouts, Deno with and without a JSON configuration file, Crystal, C# as an API and as a command line tool, Dart, Elixir with a framework, a Gleam hello-world, and an Apt case carrying ffmpeg. There are also configuration-shaped fixtures: custom packages, a custom plan path, a custom user. The plan generator has its own snapshot tests, and the build file installs the snapshot testing tool on demand before running them in review mode, with a comment saying this is needed whenever the examples are added or changed. So the fixtures are assertions, and a new language becomes supported by adding a directory.

A web framework and a port picker in a command line tool

The dependency list explains several features that the README does not mention. There is an async runtime with all of its features enabled, a web framework, and a library whose only job is to find an unused port, which together mean the tool can serve something rather than only print a plan. There are parsers for Cargo manifests and for the version-range syntax used by node projects, so plan generation reads the files a project already has. A set of small terminal libraries handle wrapping and alignment, including one crate for drawing boxes. And the declared minimum language version is a number from well before the edition the package uses, which is a deliberate choice about how old a compiler the tool will accept. None of this is documented in the readme; all of it is there in the manifest.

The Nix revision is a constant somebody updates by hand

One build target exists only to print information. It queries the Nix package collection's repository for the latest commit and prints the identifier, with a comment explaining that it is for updating constants named after package archives in the source. So the tool does not resolve the package collection at build time; it ships pinned archives and a human updates those pins. Two more details sit alongside it. The installation story covers three platforms: a shell script, a PowerShell script, an uninstall script, and a directory holding a Windows installer definition, which is a fuller installer story than most command line tools attempt. And the development environment is itself Nix-based, with a lock file at the root and a development container configuration beside it.

Editorial conclusion

Nixpacks fits a Railway user who already depends on its generated builds and has no reason to migrate today. Check four things before starting anything new on it: that the README's own banner declares maintenance mode and points at a replacement, which means language detection and plan generation will not gain providers, what your pinned Nix packages revision is, because the revision is a constant in the source that someone updates by hand, whether your platform is covered by the install scripts it ships, and that the test matrix is the examples directory rather than a documented support list. If you are choosing a builder today, the banner's own recommendation is the more useful sentence in the file.

Frequently asked questions

nixpacks alternative?

The README declares the project to be in maintenance mode and recommends a replacement tool from the same organisation. The last commit to the default branch is dated 2026-10-02 while the newest release tag is from 2025-10-24.

nixpacks vs buildpacks?

The project describes itself as started by the hosting platform's team as an alternative to buildpacks, aimed at the problems of deploying thousands of user applications there. Its stated big change is that system and language dependencies are pulled from the Nix ecosystem.

What does nixpacks produce?

An OCI compliant image built from a source directory, deployable anywhere. It is written in Rust and ships both a command and a library, and its intermediate output is a shell script that invokes a container build.

How is nixpacks installed?

The repository carries an install script for a POSIX shell and one for PowerShell, an uninstall script, and a directory holding a Windows installer definition, and the project is published as a crate. The README itself points to the documentation site instead of repeating commands.

Which languages does nixpacks support?

The examples directory reads as the coverage list rather than a documented matrix: Clojure in several build tool variants, COBOL in three source layouts, Deno with and without a JSON configuration file, Crystal, C# as an API and as a command line tool, Dart, Elixir with a framework, Gleam, and Apt with ffmpeg.

How does nixpacks pin its Nix packages?

With constants held in the source. A make target queries the Nix package collection repository for the latest commit and prints the identifier, with a comment saying it exists to update those archive constants, so the revision is bumped by hand rather than resolved at build time.

Official sources

  1. License: MIT
  2. Project website
  3. railwayapp/nixpacks on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/railwayapp-nixpacks.svg)](https://hysenlabs.com/projects/railwayapp-nixpacks)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/railwayapp-nixpacks.svg)](https://hysenlabs.com/projects/railwayapp-nixpacks)

Was this useful?