The XRUIOS is a Linux-based operating system designed to let different devices communicate seamlessly. It achieves this through an abstraction-layer API, ensuring data can be shared easily and securely between platforms.
While the long-term vision uses Stride3D atop Linux as the rendering engine, current development focuses on supporting Windows, Linux, and Android.
Technically, the XRUIOS is made up of three layers:
Base API – Handles data exchange and integration for software.
Application Layer – The interface and functionality presented to users on display-based devices.
Stride3D Renderer – Provides immersive XR rendering for headsets and related devices.
Developers can use any combination of these layers—from just the API to the full stack.
Alongside the core tech, I’ve created a few supporting tools:
Keeper of Tomes – Tracks changes in directories over time, helping identify added, removed, or renamed files
Secure Store – A cross-platform, per-session secure storage system with OS-level access control
The XRUIOS continues to evolve as a cross-platform XR operating system and development framework focused on secure, device-agnostic communication. This update covers recent demos, new tooling, and architectural changes.
To begin, let's look at where the XRUIOS is right now!
This demo was recently presented at Future University Hakodate as part of a research publication. The main goal was to show that XR needs a real purpose beyond just looking cool; something that actually makes people want to use it. The Evangelion-inspired theme isn’t fully complete yet, but it helped visualize the direction I’m going in.
On the development side, I’ll be moving away from Unity and switching to Stride. Unity was mainly used for the demo due to time constraints, but Stride gives me more control and fits better with the long-term vision.
CORE CONCEPTS
I’ve also been building out the foundation of XRUIOS with a few key components:
XRUIOS.Barebones
This is a growing library (400+ functions so far) that standardizes how devices communicate and share data. The idea is to have a consistent base across different operating systems, making cross-device interaction much easier. There’s also a simple CMD test in the project if you want to see it in action.
Dirac is a C# library that allows different programs to securely communicate with each other. It’s designed to simplify and replace a large portion of Plague’s Protocol, while making the system easier to scale by splitting functionality into separate workers.
This will be split into its own repository soon, but I want to finish proper documentation first. It builds on top of Dirac to handle higher-level communication between systems.
I also developed HangarBay, a modding system for Stride3D. It supports multiple mod types, includes encryption and signature verification, and handles both assets and code in a unified way. The goal is to make modding powerful without sacrificing security.
That’s where things are right now. There’s still a lot more coming, especially around documentation and refining the overall architecture, but the foundation is starting to come together!
🔒 Secure Store: A tiny, cross-platform, per-user key/value store designed for simplicity and security. Perfect for developers needing lightweight, reliable data persistence without the bloat.
🛡️ Plagues Protocol: A zero-trust, fully local RPC system that handles privileged operations. It splits every task into isolated, self-verifying workers—built to be PQC (Post-Quantum Cryptography) resistant for future-proof protection.
The XRUIOS is (In short) one of my longest endeavors, originally starting out as a small concept; that concept? Being able to use UIs in 3D but in a way that adds value to our everyday lives.
This is an idea I had years ago, but it only recently culminated in a prototype I was developing and close to releasing! That is, until the SSD it was on died.
This led to me asking how I could increase the quality of the project and what I could do differently. At this time, I built the UIs within Unity and had the backend API built atop Unity as well.
However, what if I didn't need Unity? What if I could instead work atop the base system itself? What if the XRUIOS could do more not just for headsets but ubiquitous computing in general? What if you weren't limited to an OS?
What if I didn't even need a display?
And thus the new XRUIOS was born!
First off is the base layer; this handles both abstraction and data handling; for example, in some cases the program focuses on ensuring data returned is the same between operating systems.
At other times, it handles custom data types
All of this will later be local APIs with IOT capability! In general, calling on these in one platform means you will get the same data structure elsewhere (AKA they're all Cross Platform)!
Next is the application layer; this is how you actually use the XRUIOS! For example, the main application usage of the XRUIOS on my end is through a Linux Distro (Called the XRUIOS (for now)) that runs a software suite I made!
*Area Manager
*Planner UI
This realistically can be as simple or advanced as you want; you can decide to use apps, terminal prompts, an LED matrix and anything else you can think of! You can also go the headless route if you prefer that as well.
Finally, there is the Renderer (AKA what I have touched the least so far)! This handles rendering the apps in 3D, while having apps exclusive to the renderer as well! I'm hoping to focus on this more with Stride3D in the upcoming weeks!
All in all, this is meant to be open source and free to use!