stow

Public compilation cache

cargo build with the dependencies already compiled.

stow is a public, signed compilation cache for Rust crates. Trusted CI compiles every crate version once; your machine verifies the signature and skips the compile.

install
curl -fsSL https://stow.waterui.dev/install.sh | sh

already installed? stow build needs no setup — stow setup is what makes a plain cargo build fast.

Measured

2.88×

median faster cold build across 13 popular Rust projects

4.76×

best case (sd): 10.7 s of cargo becomes 2.2 s

234 s

the whole suite with stow — 433 s with plain cargo, 61 s floor

Cold cargo build against stow build with a preheated cache, 13 popular Rust projects, one machine, dev profile. Method and every row: the acceleration audit.

How it works

1/3trusted build

GitHub-hosted CI compiles every crate version once and signs the artifact with cosign. Each one is keyed by crate, version, features, target and rustc, so it is only ever served to a build that would have produced the same bytes.

2/3verified fetch

The CLI verifies the signature before anything touches your target directory. A record that fails to verify is a miss, never a hit — a polluted cache can slow a build down, not change it.

3/3miss → build

A cache miss queues a build for the exact identity that missed. A crate requested on this page goes to the front of that queue, for every CI target, on the current stable rustc.

Each hit lands in your target directory as a copy-on-write clone of stow's local cache — on clone-capable filesystems (APFS, Btrfs, XFS with reflink, ReFS Dev Drive) ten projects that share a crate store its bytes once; elsewhere it is a plain copy. sccache keeps compressed entries and writes a full new copy into each target dir on every hit.

Is it cached?

Type a crate name and this page answers from the published index slice for the current stable rustc — the whole lookup happens in your browser, no per-crate query leaves the machine.

cache lookupslice loads on first query

This is what the site reports is cached. The page does not verify signatures — the CLI does that itself before any artifact touches your build.

Request a crate

Ask for a crate and trusted CI builds it ahead of the miss queue, for every CI target on the current stable rustc. One request, 9 signed artifacts.

request

features

pick a crate to list its features