It's in the same vein, but our goal is to create a standard for fully reproducible builds

Nixpacks can also spit out a plan (https://nixpacks.com/docs/how-it-works#plan) which, when run again, will assure that the build artifacts the exact same every time it's run against that plan.

The result is that any code that's built with nixpacks has all it's dependencies snapshotted so it won't break over time.

For us, that means anytime someone comes to our platform (http://railway.app/) and deploys an Template, it won't be broken