Know what has been measured.
Infrastructure, finance, engineering, and procurement teams
For data centers and other compute-heavy environments, this page separates measured Rubian and Kestowv results from ideas that still need new Project Valux benchmarks.
Measured results, open questions, and the tests still required.Every result names the system and test.
Current evidence includes Rubian and Kestowv shell, systems-layer, workload, responsiveness, and energy observations. Each result identifies what was tested and where the conclusion stops.
Project Valux needs new benchmarks.
Project Valux is the temporary name for the operating-system project. Its performance claims require a named build, matched control, equal work, correctness checks, telemetry, and repeated trials.
Commercial outcomes need commercial measurements.
Lower cost per token, lower energy per workload, more operations per joule, less thermal throttling, and universal responsiveness remain deferred until the required matched campaigns exist.
Working through a hardware or runtime decision? Explore compute evaluations