Download

Install Kraftverk

Official binaries ship for x86_64 Windows and x86_64 Linux only, and require an AMD CPU under policy amd-only-v1.

Latest GitHub Release All releases

Preflight

Hardware check before you install

Kraftverk will refuse to run optimize/benchmark paths on unsupported hardware. Exit codes 20–25 mean the gate blocked execution — that is intentional.

You need

x86_64 Windows or Linux
AMD CPU (AuthenticAMD)
No GPU, or AMD GPU only (PCI 0x1002)

Will not run

Intel CPU hosts
NVIDIA or Intel GPU present
ARM / non-x86 machines

Inspect without the gate after install: kraftverk compatibility, kraftverk hardware.

Hardware support details →

Platforms

Install instructions

Windows (x86_64)

Open the latest release and download the Windows asset (zip or installer published for that tag).
Verify checksums when the release notes publish digests (see note below).
Extract or install to a writable directory. Prefer a path without unexpected ACL restrictions.
Open a terminal in that directory (or add it to PATH) and run:

kraftverk compatibility
kraftverk hardware
kraftverk inspect
kraftverk baseline

Desktop instrument (when packaged in the release): launch kraftverk-desktop — it shares the local experiment DB with the CLI.

Linux (x86_64)

Download the Linux x86_64 asset from the latest release.
Verify checksums when published with the release.
Make the binary executable and place it on your PATH:

chmod +x kraftverk
./kraftverk compatibility
./kraftverk hardware
./kraftverk inspect
./kraftverk baseline

Safe optimize uses best-effort nice / affinity APIs. Some process priority changes may require elevated privileges depending on your distro policy.

Build from source

Requires a recent Rust toolchain. From a clone of the repository:

cargo build --release -p kraftverk-cli
cargo run -p kraftverk-cli -- compatibility
cargo run -p kraftverk-cli -- baseline
cargo run -p kraftverk-cli -- optimize --mode safe --goal balanced
cargo run -p kraftverk-desktop

See DEVELOPMENT.md for workspace details.

Integrity

Checksums

Treat release artifacts as untrusted until you verify them. When a release publishes SHA-256 (or similar) digests in the release notes or accompanying *.sha256 files, verify before running:

# Windows (PowerShell example)
Get-FileHash .\kraftverk-windows-x86_64.zip -Algorithm SHA256

# Linux
sha256sum kraftverk-linux-x86_64.tar.gz

Exact asset names vary by tag. Always match the digest published for that release. If digests are missing for a given tag, open an issue or wait for the checksums to be attached — do not invent trust.

First run

Recommended first session

kraftverk doctor
kraftverk capabilities
kraftverk baseline
kraftverk optimize --mode safe --goal balanced
kraftverk report --format html
kraftverk status

If something looks wrong, restore:

kraftverk restore --baseline

Continue in the docs →