Monado Is the Open Source Runtime Quietly Powering Half the XR Industry

If you have used a VR headset in the last couple of years, there is a decent chance an open source project you have never heard of was running quietly underneath the whole experience. Its name is Monado, and in 2026 it has gone from a niche Linux curiosity to one of the most important pieces of plumbing in the entire XR industry.

First, what a runtime actually does

When you build a VR app, you do not talk to the headset directly. You talk to a runtime. The runtime is the layer that takes your rendered frames, hands them to the compositor, reads the tracking data off the sensors, manages the display timing, and keeps everything synced so you do not get sick. On Quest, that runtime is Meta's. On a Windows PC with SteamVR, it is Valve's. The runtime is invisible when it works and miserable when it does not.

OpenXR, the Khronos standard, gave developers one API to write against so they would stop maintaining a separate code path for every headset. But a standard is just a document. Somebody still has to implement it. Monado is the open source implementation, originally built by Collabora as the first OpenXR runtime for Linux, and now running on Linux, Windows, and Android.

The quiet part is who is using it

Here is the thing that made me sit up. Monado is no longer a hobby runtime for Linux enthusiasts poking at a Valve Index. Collabora confirmed this year that Monado has become the foundation under a long list of commercial XR products. Google's Android XR builds on it. So do NVIDIA CloudXR, Hololight Stream, Qualcomm's Snapdragon Spaces, PortalVR, and Pico's runtime on the Neo3 and Pico 4.

That is a remarkable position for an open source project to be in. Instead of every vendor writing a brand new OpenXR runtime from scratch, burning months of engineering on the boring and bug prone parts, they fork or build on Monado and spend their time on the things that actually differentiate their hardware. It is the same pattern that made Mesa the graphics backbone of the Linux desktop, and Monado was deliberately architected to follow that philosophy, with the OpenXR API cleanly separated from the implementation underneath.

Khronos is paying to make it better

The momentum is not accidental. The OpenXR Working Group at Khronos funded a dedicated effort this year, the Monado Upgrade Project, and picked Collabora to drive it. The work is squarely aimed at the parts developers feel. There is a refactor of the compositor graphics pipeline and layer squashing to cut overhead and push more frames, plus support for a batch of extensions that make life easier on both sides of the API.

Those extensions are not glamorous, but they matter. XR_KHR_visibility_mask lets the runtime skip rendering the pixels you cannot see at the edges of the lens, which is free performance. XR_KHR_vulkan_swapchain_format_list gives Vulkan apps more control over their image formats. XR_EXT_conformance_automation makes automated testing possible, and XR_EXT_debug_utils is the kind of quality of life tooling that turns a frustrating afternoon of guesswork into a quick fix.

The releases keep landing

This is not a project coasting on a press release either. The Monado 25.1.0 release brought real improvements to hand tracking and a pile of new device drivers, including support for the Blubur S1, the old Rift DK2, and SolarXR IPC, along with fixes for the Razer Hydra, the Vive Pro 2, and the Xreal Air 2 Ultra. The runtime has also been keeping pace with OpenXR 1.1, which folded a number of previously separate extensions into the core spec and made cross platform development noticeably simpler.

Why this should matter to you

If you only ever use one headset and never write a line of code, you might wonder why any of this is your problem. The answer is longevity. Headset makers come and go, and when a company folds or simply decides your device is too old to support, the proprietary runtime stops getting updates and your hardware slowly turns into a paperweight. An open source runtime does not have to die when a vendor loses interest. The community can keep it alive, add support for new operating systems, and squeeze more life out of devices the manufacturer abandoned.

That is the unglamorous but genuinely important reason I keep coming back to projects like this. The flashy headset reveals get the headlines, but the open source plumbing is what determines whether the XR ecosystem is something we collectively own or something we rent until the lease runs out. Monado quietly becoming the shared foundation for half the industry is, to me, one of the most encouraging things happening in XR right now.