The project's README from github.com/indexable-inc/blaze. As one markdown file: README.md.
The same commands as cargo, with blaze in front.
Blazingly fast Rust, literally.
Install · Try it · How fast · How it works · Docs
curl -fsSL https://raw.githubusercontent.com/indexable-inc/blaze/main/install.sh | sh
For macOS on Apple silicon and Linux, with or without Rust installed: blaze downloads the Rust it builds with once (about 100 to 135 MB), or uses rustup's. Rather use crates.io or Nix? Other ways to install.
In any Rust project:
blaze run # like cargo run
blaze test # like cargo test
blaze build # like cargo build
The first build runs cargo, then waits a few seconds for blaze to load your project. Then change
a function and build again: it's back in milliseconds, and the Finished line says [ra-jit]
(blaze's engine). Every other cargo command passes straight through to cargo. Where cargo is
installed, cargo blaze run is the same as blaze run.
cargo build, on average over real projects.| Edit one function, then build (Linux x86-64) | cargo build |
cargo blaze build |
|---|---|---|
| ripgrep | 508 ms | 56 ms (9.1× faster) |
| nushell | 1.25 s | 236 ms (5.3× faster) |
| helix | 2.15 s | 116 ms (19× faster) |
| bun (1.25M lines of Rust) | 9.11 s | 451 ms (20× faster) |
Every project, platform, chart, and the memory and disk it takes: benchmarks.
blaze runs beside cargo and keeps your project compiled in memory. After an edit it compiles only the functions you changed and writes them into the program cargo already built, instead of linking it again from scratch. A program that opts in can take the new code while it keeps running. More.
nightly-2026-10-25 today) whatever toolchain the project pins. A project on a stable
release builds as it is, and #![feature(...)] code builds too.cargo check or your CI as the final word, and
tell us when something differs from cargo.All the details: what works and what doesn't yet.
cargo build use blazenix run github:indexable-inc/blaze
This opens a Game of Life window. On macOS on Apple silicon you can change its rules, colours and speed while it runs; elsewhere the window runs without live edits. It needs Nix, and builds blaze from source the first time.
For release news: Watch → Custom → Releases on GitHub.
How to build blaze from a checkout, run its tests and send a change: docs/contributing.md. To report a security problem: SECURITY.md.
blaze stands on the shoulders of giants. Thank you to the people who built:
None of these projects endorses blaze.
blaze was called ra-jit until 2026-10-24; cargo ra-jit still works. Made at ix
for den's native app. MIT or Apache-2.0.
The first build runs cargo, then waits a few seconds for blaze to load your project. Then change a function and build again: it's back in milliseconds, and the Finished line says [ra-jit] (blaze's engine). Every other cargo command passes straight through to cargo.