Independent operating system project

snarOS

An operating system
built from the ground up.

A long-term systems engineering project focused on security, isolation, reliability, performance and a foundation designed to evolve.

Current version 0.0.1
Target 1.0.0
Progress 0%
Status Planning
CURRENT STATE

The project starts here.

snarOS is currently at the foundation stage. This website will evolve together with the operating system and will reflect actual implementation progress.

RELEASE TARGET

snarOS 1.0.0

NOT STARTED
Overall development 0%
0 milestones completed Release gate pending
CURRENT MILESTONE

Project Foundation

Define the architecture, development environment, system boundaries and Version 1.0 requirements.

Planning
VERSION 01

What must exist
before 1.0.

Version 1.0 is not a visual milestone. It is a technical release gate. Every major subsystem must be implemented, tested and documented before the release is considered complete.

01

Boot & Kernel

Establish the boot path and the fundamental privileged execution environment of snarOS.

Boot Kernel CPU
02

Memory

Physical memory, virtual memory, address spaces, allocation and memory protection.

MMU Paging Isolation
03

Processes

Processes, threads, scheduling, context switching, synchronization and inter-process communication.

Scheduler Threads IPC
05

Storage

Device abstraction, filesystem interfaces, persistent storage and recovery mechanisms.

VFS Filesystem Storage
06

Networking

Network devices, protocol stack, sockets and controlled communication between systems.

IPv4/IPv6 TCP/UDP Sockets
07

Userspace

System services, shell, utilities, runtime interfaces and the initial application environment.

Shell Services Runtime
08

Graphics

Display, input, rendering and the foundation for the graphical user environment.

Display Input Rendering
09

Verification

Automated testing, fuzzing, fault testing, benchmarks and release validation.

Testing Fuzzing Benchmarks
DEVELOPMENT TREE

One system.
Many engineering domains.

The project is divided into technical domains so progress can be understood at a glance without hiding the complexity underneath.

s
snarOS 1.0 Complete system
01 Boot Firmware → Kernel
02 Kernel Core execution
03 Memory Address spaces
04 Processes Execution model
05 Security Trust boundaries
06 Storage Persistent data
07 Networking Communication
08 Userspace System environment
09 Graphics Visual environment
10 Verification Evidence & testing
ARCHITECTURE

Boundaries are
part of the design.

snarOS will be developed around explicit boundaries between hardware, privileged system code, system services and applications.

04
Applications

User applications · tools · ecosystem

↓
03
Userspace

Services · shell · runtime · system utilities

↓
02
System Interface

System calls · IPC · resource interfaces

↓
01
snarOS Core

Kernel · scheduling · memory · isolation · synchronization

↓
00
Hardware

CPU · memory · storage · network · display · input

VERSION ROADMAP

From first boot
to 1.0.

Versions represent technical milestones. A version becomes complete through implementation and verification — not simply because time has passed.

01
v0.0.1 CURRENT

Project Foundation

Establish the architecture, repository, toolchain, development workflow and complete 1.0 specification.

Architecture Toolchain Specification
02
v0.0.2 PLANNED

First Boot

Produce the first bootable snarOS image and establish the earliest kernel execution environment.

03
v0.1 PLANNED

Kernel Foundation

CPU initialization, interrupts, kernel runtime, diagnostics and foundational kernel services.

04
v0.2 PLANNED

Memory & Execution

Memory management, address spaces, tasks, context switching, scheduling and initial IPC.

05
v0.3 PLANNED

Storage & Persistence

Storage abstractions, filesystem interfaces, persistent data operations and recovery.

06
v0.4 PLANNED

Userspace

System services, shell, utilities and the initial userspace application model.

07
v0.5 PLANNED

Security Foundation

Process isolation, capabilities, authorization, identity boundaries and security testing.

08
v0.6 PLANNED

Networking

Network devices, protocol stack, sockets and system-level networking interfaces.

09
v0.7 PLANNED

Graphics

Display, input, rendering and the foundation for a graphical environment.

10
v0.8 PLANNED

System Integration

Integrate major subsystems and strengthen stability, diagnostics and recovery.

11
v0.9 PLANNED

Release Candidate

Full-system validation, security testing, fuzzing, benchmarks and release hardening.

12
v1.0.0 RELEASE GATE

First Stable Release

All defined Version 1.0 requirements implemented, verified and documented.

ENGINEERING PRINCIPLES

Build the foundation
correctly.

The goal is not to make claims that sound impressive. The goal is to build systems that can eventually prove them.

01

Security by construction

Security boundaries should be part of the architecture instead of being an afterthought.

02

Failure containment

A failure in one component should not automatically become a failure of the entire system.

03

Minimal trusted core

Keep privileged code deliberate, understandable and as small as practical.

04

Measured performance

Performance claims should eventually be supported by reproducible benchmarks.

05

Observable systems

Diagnostics should make failures understandable instead of mysterious.

06

Evolution without chaos

Stable interfaces and modular boundaries should allow future capabilities without constantly rebuilding the core.

TECHNOLOGY

The tools behind
the system.

Technology choices will evolve as architecture decisions are validated. These represent the current engineering areas.

01

Low-level languages

C Assembly Shell Rust — evaluation
02

Build & debugging

GCC / Clang Linker Make / CMake GDB QEMU
03

Engineering

Git GitHub Testing Fuzzing Benchmarking
04

Knowledge domains

Computer Architecture Operating Systems Concurrency Networking Security
RELEASE PHILOSOPHY

Code is not
evidence by itself.

A snarOS milestone becomes complete only when the implementation, tests and documentation support it.

01 Implement Working code
→
02 Test Automated validation
→
03 Verify Behaviour & performance
→
04 Document Reproducible evidence
DEVELOPMENT LOG

Build it.
Record it.

The development log will record meaningful technical progress throughout the life of the project.

#000
CURRENT 09 SEP 2026

Project foundation

snarOS is currently being defined from the ground up. The initial phase focuses on architecture, system boundaries, development tooling and the Version 1.0 specification.

Planning phase
THE BEGINNING

Every operating system
starts with a first boot.

snarOS starts here.

Follow the journey ↓