Incremental rust builds up to 92x faster than cargo/rustc

The identical commands as cargo, alongside blaze in front.
Blazingly accelerated 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, alongside or without Rust installed: blaze downloads the Rust it builds alongside formerly (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 # akin cargo run blaze test # akin cargo test blaze build # akin cargo build 

The archetypal build runs cargo, afterward waits a few seconds for blaze to burden your project. Then change a function and build again: it's rear in milliseconds, and the Finished row says [ra-jit] (blaze's engine). Every another cargo command passes direct through to cargo. Where cargo is installed, cargo blaze run is the identical as blaze run.

• Edits rebuild 10× faster on macOS arm64, 24× faster on Linux aarch64 and 11× faster on Linux x86-64 than alongside cargo build, on average complete genuine projects.
• About 20 ms from preservation a document to a operating program using the new code, with live edits.

Every project, platform, chart, and the recollection 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, alternatively of linking it again from scratch. A program that opts in can obtain the new code during it keeps running. More.

• macOS on Apple silicon and Linux. On Windows all build is cargo's.
• blaze is its own toolchain. It builds all project alongside its own Rust, blaze-2026-10-25 (today the nightly of that date), any the project pins; stable code and #![feature(...)] code build. Your toolchain and CI remain the final word (why).
• It trades recollection for speed: a few GB for a small project.
• It's young. Keep cargo inspect or your CI as the final word, and tell us whenever item differs from cargo.

All the details: what plant and what doesn't yet.

• Install: requirements, crates.io, Nix
• Using blaze: day to day, rebuild on save, making plain cargo build use blaze
• Benchmarks: all number, how it's measured, and on what machines
• How it works: a map of the code
• Cargo compatibility: all command, emblem and setting
• Hot reload: changing a operating program
• CI runner and roadmap: anywhere blaze is going
• Contributing

nix run github:indexable-inc/blaze

This opens a Game of Life window. On macOS on Apple silicon you can alter its rules, colours and speed during it runs; elsewhere the opening runs without live edits. It needs Nix, and builds blaze from origin the archetypal time.

For publish news: Watch → Custom → Releases on GitHub.

We're operating alongside a few teams on accelerated Rust CI and distant builds, built on blaze. If your team waits on Rust builds, inform us what slows you down: [email protected]. Teams we activity alongside get first admission and a straightforward say in what we build next.

How to build blaze from a checkout, run its tests and dispatch a change: docs/contributing.md. To study a safety problem: SECURITY.md.

blaze stands on the shoulders of giants. Thank you to the group who built:

• rust-analyzer, whose inspection and MIR blaze compiles from
• Cranelift (Bytecode Alliance), the accelerated code generator
• LLVM and inkwell, for the optimised tiers
• salsa, the incremental motor underneath
• object, for study and penning executables
• Rust and its compiler crates
• rustd (DioxusLabs), whose code blaze includes

None of these projects endorses blaze.

blaze was called ra-jit until 2026-10-24; cargo ra-jit motionless works. Made at ix for den's native app. MIT or Apache-2.0.