RigRoute LabsDAENRigRoute ↗
Technical Preview

Benchmark your computer for Local AI

Download RigRoute AI Benchmark, run a real local AI workload, and see what your machine can actually run. Benchmarking happens locally. Uploading results is optional and requires your explicit consent.

Windows

Windows x64

Unsigned Preview

Code signing is pending; your operating system may show a security warning.

Download for Windows

0.1.0 · 13.9 MB

Release details
Version
0.1.0
File
RigRouteBenchmark-windows-x64.zip
SHA-256
3d171a5208fe0df0335417cade2c7b032f526cb766946cacc5a0a62c10abb03d
Build
5ceddbabc74c
Signing
Unsigned (code signing is pending)
Validation
A full Quick benchmark completed on real hardware: AMD RX 9070. Other graphics cards are not validated yet.
Requirements
Windows 10/11 x64 (tested: Windows 11 10.0.26200)
How to start
Extract the zip and start RigRouteBenchmark.exe. Windows may show a warning because the preview is not code-signed yet.

macOS

Apple Silicon

Unsigned Preview

Code signing is pending; your operating system may show a security warning.

Download for macOS

0.1.0 · 12.2 MB

Release details
Version
0.1.0
File
RigRouteBenchmark-macos-arm64.tar.gz
SHA-256
3a27a40d5555ec06f630912144d27ffbac1489cf46eb30eeec1eebb36839329a
Build
5ceddbabc74c
Signing
Unsigned (code signing is pending)
Validation
A full Quick benchmark completed on real hardware: Apple M1 Pro. Other graphics cards are not validated yet.
Requirements
macOS 14.8.9 or later on Apple Silicon (build host version; not yet tested lower)
How to start
Extract the archive (double-click), move RigRouteBenchmark to Applications and open it. macOS may block or warn because the app has no Developer ID signature or notarization yet. Use Control-click > Open, or System Settings > Privacy & Security > Open Anyway; do not turn Gatekeeper off.

Linux

Linux x64

Technical Preview

 

Download for Linux

0.1.0 · 12.8 MB

Release details
Version
0.1.0
File
RigRouteBenchmark-linux-x64.tar.gz
SHA-256
f93909cdda046e5db32f528d603ba717313dc26f54bad4b525e39ed241918729
Build
5ceddbabc74c
Signing
No code signature; verify with the SHA-256 above
Validation
The frozen build is tested in clean Ubuntu 22.04/24.04 and Debian 12 environments (CI). Validation on a real Linux GPU is in progress; we are looking for testers.
Requirements
Linux x86_64 with glibc >= 2.35 (built on it); the GPU runtime additionally needs glibc >= 2.34, libstdc++ GLIBCXX_3.4.30, libvulkan.so.1 and a Vulkan driver, OpenSSL 3, libgomp
How to start
Extract with tar -xzf RigRouteBenchmark-linux-x64.tar.gz and run ./rigroute-bench quick in the extracted folder. You do not need Python, Git or Docker.
Troubleshooting: the Linux GPU benchmark uses Vulkan. You need a Vulkan driver for your graphics card (Mesa RADV on AMD) and libvulkan.so.1. Run ./rigroute-bench probe to see what was detected.

How it works

  1. 1DownloadChoose your operating system.
  2. 2BenchmarkRigRoute runs a real Local AI workload on your computer.
  3. 3See your resultGet measured performance and a RigRoute capability result.

Your benchmark runs locally

Uploading results is optional. Local paths, usernames and private diagnostic data stay on your computer. If you choose to upload, RigRoute sends only the privacy-filtered benchmark evidence needed to generate your result.

Result sharing is opening in stages; until then the app keeps your result on your computer.

Questions or feedback? kontakt@rigroute.dk

What gets uploaded?

Stays on your computer

  • Your name, username, computer name and network addresses
  • File and folder paths and the exact commands that ran
  • The full llama.cpp output and the raw result files (only their SHA-256 fingerprints are uploaded)
  • The downloaded test model and runtime

Uploaded only if you choose to

  • Operating system, version and kernel, and processor architecture
  • Processor, core counts and memory
  • Graphics hardware and the device memory llama.cpp reported
  • Test model, runtime and benchmark profile with versions and hashes
  • Measured speed per repetition, and whether the run succeeded
  • The two answers, the rule behind them, and when the run happened