Your build,always at its best

Wezel keeps watch over your build performance as your code changes. See regressions and improvements, traced to the commits that introduced them.

Get started

Any signal your repo needs.

Build time, bundle size, or a metric specific to your project. Use the built-in measurement tools, or write your own.

email discord bluesky

Every regression is attributed.

Clean build regressed.

Measure selected commits. If a build slows down, Wezel checks the commits in between to find where it started.

[step.cargo.clean-build]
args = ["build", "--workspace"]
summary.time.outcome = "time_ms"

measured buildworkspace build time

introducing commit8f4c2d1

+12.4scompared with last measured run

Express your workflow any way you want.

Rebuild regressed.

Run the base build, apply the patch, then sample the rebuild five times.

[step.cargo.base-build]
args = ["build", "--workspace"]

[step.cargo.edit-build]
args = ["build", "--workspace"]
apply_diff = true
summary.time.outcome = "time_ms"
summary.time.aggregation = "mean"
summary.time.samples = 5

measured buildsampled rebuild

introducing commit3b91a0f

+2.8smean of 5 samples

Good changes surface too.

WASM size improved.

Build your app, then measure the size of the file your users download.

[step.exec.build-wasm]
cmd = "trunk build --release"

[step.filesize.measure-wasm]
glob = "dist/app.wasm"
summary.size.outcome = "dist/app.wasm"

measured artifactdist/app.wasm

introducing commitc91a7d4

-184 KiBcompared with last measured run

Examples

Blog9 May 2026

Introducing Wezel

Give your builds love they long for.