nixpacks.com

What It Is

Nixpacks is an open-source developer tool initiated by Railway. It analyzes, plans, and builds an application source directory into an OCI-compatible image. Its goal is similar to an “automatic Dockerfile/Buildpacks” experience: in most cases, it can detect the project language without configuration, install dependencies, run the build, set the start command, and ultimately produce an image that can be run with Docker.

Core Capabilities and Ecosystem

Nixpacks’ core workflow consists of Plan and Build. In the Plan phase, it matches language providers and generates a reproducible build plan containing Nix packages, install commands, build commands, start commands, and more. The plan can be saved as JSON/TOML. In the Build phase, it generates a Dockerfile based on the plan and builds the image using Docker BuildKit. Configuration can be overridden via nixpacks.toml, nixpacks.json, environment variables, and CLI arguments, with a clear priority order and support for extending array-based configuration.

Language support is broad. The documentation lists Node, Python, Go, Rust, Java, PHP, Ruby, C#/.NET, Deno, Elixir, Swift, Scala, Zig, Clojure, COBOL, and more. Its deployment ecosystem includes Railway, Coolify, Dokku, GitHub Actions, and others, making it suitable for CI/CD integration or self-hosted PaaS setups.

Pricing and Open-Source Status

No commercial pricing is mentioned in the main documentation. The project is explicitly open source on GitHub and can be installed via Homebrew, MacPorts, curl, PowerShell, Debian packages, Scoop, MSI, or Rust cargo. However, the documentation repeatedly notes that Nixpacks is currently in maintenance mode, is no longer being actively developed, and recommends Railpack as an alternative.

Pros and Cons

The advantages are its good default experience, strong automatic detection, fine-grained configuration, and output as standard OCI images, which makes migration relatively easy. Both Nix packages and Apt packages can be configured, and features such as caching, Procfile support, and phase dependencies are also fairly complete.

The main drawback is the project’s maintenance status, which is the biggest risk. Expectations for new languages, new frameworks, and bug fixes are relatively limited. In addition, it does not support building multi-architecture images in a single build; users need to combine them manually with docker manifest. Most advanced use cases still require an understanding of Docker, Nix, and build phases.

Who It’s For and Access from China

Nixpacks is suitable for developers, DevOps teams, PaaS platform users, and teams that want to quickly containerize projects across multiple languages or generate images in GitHub Actions or self-hosted environments. The main documentation does not provide information about access from mainland China. In actual use, GitHub Releases, Nix package sources, and Docker image pulls may be affected by local network conditions. For new projects, it is worth evaluating the officially recommended Railpack, traditional Dockerfiles, or Paketo Buildpacks as well.