Roadmap

Where EuroOS is going.

EuroOS is an early, from-scratch experiment. This is the honest direction, not a set of promises. It shows what is built and boot-verified today, what we intend to tackle next, and the longer goal: a foundation Europe can build, read and govern, owned by no single company or state.

How to read this: built & boot-verified intent, not a promise No fixed dates. Priorities shift as contributors join.

Now

Alpha, built today

Everything here boots and runs. It is not a daily-driver OS yet, but it is real, and you can try it in a VM at euro-os.eu/try.

  • From-scratch kernel in Rust (no_std, UEFI): preemptive multitasking, SMP, ring-3 userspace with enforced privilege separation.
  • EuroFS + real storage interop: copy-on-write filesystem with checksums, crash-consistent A/B superblocks and snapshots. Reads and writes FAT and exFAT, reads ext4, opens SMB and NFS shares, auto-mounts USB, TRIM through the block stack.
  • Own network stack: IPv4/IPv6, TCP, DNS, DHCP, a stateful firewall, a forward-secret VPN, and fail-closed TLS 1.3.
  • EuroDesktop and office: a windowed compositor, an interactive shell, GNU-compatible coreutils, the EuroSuite office apps, and all 24 official EU languages.
  • Sovereign identity and trust: EuroID (memory-hard Argon2id, tamper-evident audit log), a GUI lockscreen, TPM 2.0 with measured boot, full-disk encryption and PCR-sealed secrets.
  • Capability-isolated AI agents (EuroAgent) that run offline, plus a Linux/musl compatibility bridge that runs unmodified programs. Every binary is Ed25519-verified before it runs.
  • Reproducible, signed builds, open under the EUPL-1.2. The security-critical logic lives in host-tested libraries.

Next

Making it real

Turning an experiment into something people can join and use.

  • A real contributor onramp: good first issues, a clear contributing guide, and a European-hosted mirror (Codeberg) alongside GitHub.
  • Hardware breadth beyond VMs: broaden driver support toward real laptops, starting with common, standards-based devices (the wifi-chipset problem is a real one).
  • The app and package story: the eupkg package manager and an app catalog, so an average user has what they expect.
  • One-command build verification: let anyone prove a shipped binary matches the public source, so a backdoor cannot hide.
  • Broader Linux compatibility, dynamic linker and WASM runtime polish, so more existing software runs unchanged.

Later

Ecosystem & sovereignty depth

The layers that take a community, partners and time.

  • A RISC-V port. The Rust core is portable, so it can move onto open, European-backed silicon (the EU Chips Act and projects like SiPearl) as that matures.
  • Pilots on real hardware with partners and public bodies. Adoption comes from being a reference and creating demand, not from out-adopting Windows tomorrow.
  • Independent governance: a foundation so EuroOS is owned by no single company, with keys and roadmap held by a community.
  • Accessibility everywhere, robust signed updates, and identity/enterprise depth.

The vision

Why

A base layer Europe can build, read and govern, owned by no single company or state. Not a product that beats Windows tomorrow, but a foundation others can fork, build on, and make real. If enough people put in the effort, maybe it becomes something. If it only ever proves the thing is buildable and moves the conversation, that already beats talking about it.

How to help

This only becomes more than an experiment if others join. Pick an issue, port a driver, package an app, write docs, or just open an issue telling us why we are wrong. That is the point.

Contribute on GitHub Get in touch Support the work