Blaze rebuilds Rust projects in milliseconds by patching the running binary
Blaze is an open-source build tool from Indexable Inc. It compiles only the functions you changed and patches them into the running Rust binary. The project reports a 19x speedup on helix and a 20x speedup on bun.
Why it mattersRust's long compile times eat the loop a developer actually works in. A rebuild that lands in 100 to 500 ms is a different kind of day.
A Rust developer edits one line, hits save, and waits several seconds for the compiler to catch up. Blaze is a build tool that keeps the project loaded in memory and patches changed functions into the running binary.
The project was open-sourced on 19 October 2026 by Indexable Inc, a native-app shop at ix.dev. The repository has 360 stars after six days. It is dual-licensed MIT or Apache-2.0.
The benchmark the project publishes
The README headline claim is "up to 92x faster than cargo/rustc". The detailed table attached to it is more modest. The project tested one-function edits on four well-known Rust crates on Linux x86-64.
Blaze reports 508 ms down to 56 ms on ripgrep, a 9.1x speedup. On nushell: 1.25 s to 236 ms, 5.3x. On helix: 2.15 s to 116 ms, 19x. On bun, with 1.25 million lines of Rust: 9.11 s to 451 ms, 20x. The specific hardware is not stated.
The 92x headline figure is not matched to a named crate in the detailed table. The project does not explain the gap between its headline and its own benchmarks. Read the 92x as the ceiling the authors have seen. Read the table as the measurement they published a method for.
How it works
Blaze keeps a running compiler process for the project. When you edit, it recompiles only the functions that changed. It writes those functions into the binary already in memory, so the linker step is skipped.
The project says live editing takes about 20 milliseconds from save to the new code running. That is cheap enough to feel instant.
What it costs
Blaze trades memory for speed. Indexable says a small project needs several gigabytes of RAM. A large one needs more. It runs on macOS on Apple silicon and on Linux. Windows builds still use plain cargo.
The project asks for Rust 1.99.0, the stable channel. Nightly-only features are not supported. The team writes that Blaze is "young" and recommends keeping cargo check or your continuous integration as the final word.
Who it fits
The command surface mirrors cargo, so a developer who already uses cargo can swap most calls for Blaze. The team at Indexable built it for one of their own projects before releasing it. The repository has 14 forks on GitHub.
Rust compile times have been a common complaint from Rust developers for years. A tool that trades a few gigabytes of RAM for 100 ms rebuilds is worth trying. The audience is anyone who edits Rust several times a minute, which is most working Rust developers.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
