See where Rubian runs today.

Platform teams and deployment engineers

Current qualification covers defined x86, NVIDIA, and Apple Silicon research environments.

Current research environments.

Testing has covered defined x86 systems, Apple Silicon qualification, Ruby runtimes, and the current Kestowv research layer.

Some operations still rely on the host system.

Rubian and Kestowv don’t yet replace every service supplied by the current host environment.

Project Valux support must be versioned separately.

A supported build must identify its public release, hardware class, driver coverage, and test status.

Windows and broad hardware support remain open.

Current tests don’t establish native Windows support or universal production compatibility across arbitrary devices.

Same work. Same answer. Then compare.How Rubian and Kestowv got here.

The useful compatibility question is about your workload.

Which runtime does it need? Which services does it call? Where does it store state? What does the host have to provide? Those details matter more than a broad claim that software runs on a platform.

Rubian uses host-backed components today. Kestowv's current enterprise pilot has a declared Linux/JRuby host boundary. We'll scope an evaluation around the actual machine, dependencies, permissions and recovery needs instead of treating a successful launch as complete compatibility.

Discuss your target environment

Working through a hardware or runtime decision? Explore compute evaluations

Rubian/Kestowv Documentation

Startup and discovery, file and project organization, Forge libraries, Taskman, agent work and Kestowv pilot operations.