RadiantOS is a new kind of operating system tuned for low-latency interactivity, offline workflows and knowledge creation.
|
Workshop Code |
Library Knowledge |
|
Studio Media |
Garden Experiments |
RadiantOS is a single address space operating sytem (SASOS) built around an exokernel. Hardware interfaces are designed to be directly accessible and simple to use, thanks to hardware/software co-design, and features of the Radiance language that make this safe. RadiantOS is inspired by Oberon, Plan 9 and Varvara, and unlike many modern operating systems, it is not UNIX-like or POSIX compatible.
RadiantOS treats your computer as an extension of your mind. It’s designed to capture your knowledge, habits, and workflows at the system layer. Data is interlinked, just like a personal wiki, not scattered around a file system.
Capabilities-based security. Apps run with only the permissions you give them. They can’t read your files or send data over the network without consent. Capabilities trickle down to the language’s type system.
Built for the Internet era, but not dependent on it. RadiantOS does not ship with a monolithic web browser. The network is part of the OS itself: files can live online, link to each other, and stay available offline. Browsing is no longer an app, it’s part of the environment.
RadiantOS replaces the “desktop” with a “home.” A calm and personal environment. No pop-ups. No notifications. No interruptions. The computer stays quiet until you need it. It’s time to move on from the desktop paradigm.
It’s an AI-native operating system. For those who use AI for productivity but wish for a deeper integration with their workflow, RadiantOS exposes all the APIs necessary for language models to be effective, while keeping their use safe using capabilities-based security.
Source as the distribution model. Radiant makes source code the default medium of software distribution. Software is delivered as readable, modifiable modules; not opaque binaries. The system itself is responsible for compiling and linking code as needed, keeping the complexities of toolchains, binary formats (eg. ELF), and shared libraries internal and invisible to the user.