The way Nixpacks uses Nix to pull in dependencies often results in massive image sizes with a single /nix/store layer ... all Nix and related packages and libraries needed for both the build and runtime are here. Not a problem with Nix per se but certainly a problem with how we were using it. Trying to abstract all the parts of Nix that make Nix… Nix, just fundamentally doesn't work. Since we transitioned away from Nix, we also transitioned away from the name Nixpacks in favor of Railpack. Generates : Construct a BuildKit build graph based on the inputs and outputs from the plan.