
rust-overlay
Pure and reproducible nix overlay of binary distributed rust toolchains
The Lens
By Erik Loyd, SaaS CEO and former COO/CFO of an AWS Premier Partner.
Updated Aug 2026
Rust toolchains inside Nix, pinned to an exact version and identical on every machine. Nixpkgs ships its own rustc, but it moves with the channel, so pinning 1.79.0 or a specific nightly means fighting the package set. rust-overlay pulls the official Rust release binaries with hashes already committed, so evaluation needs no network. MIT, free.
Three lines in a flake: add the input, add the overlay, ask for rust-bin.stable.latest.default. Point fromRustupToolchainFile at an existing rust-toolchain.toml and your Nix shell matches what rustup gives everyone else. Extensions and cross-compilation targets are overrides on the same attribute. CI refreshes hashes daily, so new releases land within a day.
Solo Rust developers on NixOS: install it and stop thinking about toolchains. Small and medium teams: this is how every laptop and every CI runner lands on the identical compiler with no argument. Teams not already on Nix: this is not the reason to adopt it, and rustup with a committed rust-toolchain.toml does the same job.
The catch is everything around it. This solves one problem cleanly and inherits every other Nix problem: flake syntax, eval errors that read like stack traces, and a first build that pulls a lot down. Old nightlies get pruned after roughly a year, so anything pinned to an ancient one eventually stops evaluating.
Free vs Self-Hosted vs Paid
fully freeFree
All of it, under MIT. Every stable, beta, and nightly toolchain, every component and cross-compilation target, both the classic overlay path and the flake path. Stable versions are retained indefinitely.
Paid
Nothing. No sponsorship gate, no pro tier, no hosted binary cache to subscribe to.
Self-Hosted Costs
Disk and download time. A full toolchain (rustc, std, cargo, clippy, rustfmt) lands in the Nix store at roughly 1 GB, so a team pinning three or four versions across laptops and CI should plan for a few gigabytes per machine and a periodic nix-collect-garbage. Binaries come prebuilt from upstream, so there is no compile cost. Nightly hashes update daily via GitHub Actions at no cost to you.
When to Pay
Never, there is nothing to buy. The money that would go here belongs in a build cache or CI minutes instead.
Free under MIT with nothing gated; the only cost is a few gigabytes of Nix store per machine.
What to do by team size
- Solo
- free; add the overlay to your flake and forget toolchain drift
- Small team
- free; pin one version in rust-toolchain.toml and every machine agrees
- Medium team
- free; the same pin covers laptops and CI runners with no extra setup
- Large team
- free, but only worth it if you already run Nix; otherwise rustup does this job
Get tools like this every Wednesday
One featured tool, three on the radar. No fluff.
A low score is not a verdict on quality. Young and niche tools start low by design. How we calculate scores
License: MIT License
Use freely, including commercial. Just keep the license.
Commercial use: ✓ Yes
About
- Owner
- oxalica (User)
- Stars
- 1,543
- Forks
- 88