Skip to main content
Back to trending

blaze

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

  • cargo
  • compiler
  • cranelift
  • developer-tools
  • hot-reload
  • incremental-compilation
  • jit
  • live-coding
  • rust
  • rust-analyzer
View on GitHub
Stars
636
Forks
21
+ today
+5
Created
7d

Ranking data as of October 26, 2026 (UTC).

Star History

Today, hour by hour

636 stars
05

Overview

Incremental rust builds up to 92x faster than cargo/rustc It ranks #35 on GitTiger, gaining +5 stars on October 26, 2026 (UTC).

The project is written in Rust and has 21 forks. It was created 7d ago.

AI-generated summary of the repository README — may contain errors.

What it is

Blaze is an incremental build and run tool for Rust projects, written in Rust and released under Apache-2.0. The pitch is that an edit should reach a running program in milliseconds instead of waiting on a full cargo rebuild, which puts it alongside hot-reload and live-coding setups rather than in competition with the compiler itself. Its topics include cranelift, incremental compilation and rust-analyzer.

Performance as described

The repository description advertises builds up to 92 times quicker than the cargo and rustc path. The README extract gives more modest platform averages for edit-driven rebuilds: roughly ten times on Apple silicon macOS, twenty-four times on Linux aarch64 and eleven times on x86-64 Linux, averaged over real projects. It also cites about twenty milliseconds between saving a file and seeing the new code execute. Those are different kinds of number, so the headline multiplier should be read as a best case.

Platforms and trade-offs

Apple silicon macOS and Linux are the named targets. On Windows the README says builds fall back to cargo, so the speed-up does not apply there. Blaze compiles with a pinned, dated Rust nightly, so a recent nightly toolchain is the expectation. It also spends memory to buy time, needing a few gigabytes even on a small project.

Getting started

Setup commands are not part of the supplied evidence. The README is where to find them, along with the nightly currently pinned.

Installation
git clone https://github.com/indexable-inc/blaze.git
cd blaze
# see README for setup

Frequently Asked Questions

How much faster is blaze than cargo?

The description advertises up to 92 times faster builds, while the README's platform averages for edit rebuilds are about ten times on Apple silicon macOS, twenty-four times on Linux aarch64 and eleven times on x86-64 Linux.

Does blaze work on Windows?

Not in the accelerated sense described. The README states that every build on Windows is handled by cargo, so the incremental speed-up is confined to macOS and Linux.

Which Rust toolchain does it need?

Blaze builds projects with a pinned, dated Rust nightly. The README is the place to check which nightly is currently pinned for the release you are using.

Why does it use so much memory?

The project states that it deliberately trades memory for speed, requiring a few gigabytes of RAM even when the project being built is small.