Hyperion OS

Hyperion OS is an AI-native operating system: AI is a system service, running in user space with its own privilege boundary, rather than an application on top of a conventional desktop. It is Layer 3 (L3) of EntroStack, EntroVerse's sovereign compute vertical, designed to sit on sovereign silicon (L2) and energy infrastructure (L1) and built to run on ordinary hardware today. Above it sit the compute kernels (L4), the compiler, tensor framework, inference runtime and application layers.

The design brief is simple: an operating system built after large language models existed, rather than one that had AI bolted on afterward.

Four components are planned as part of the OS itself:

• Hyperion Shell: the desktop environment. AI is the primary interaction model: speech, text, and gesture route through the same system assistant rather than through a separate app.
• Hyperion Compat: a compatibility layer, on the roadmap, for running existing Windows applications through Wine and Proton; dual-boot is planned so the current system stays one restart away.
• EntroEdge: the daemon that contributes idle CPU/GPU cycles to the wider EntroEdge compute network in exchange for credits. Off until you opt in, and never active while the machine is in use; see §4.
• Hyperion App Store: the distribution channel for third-party applications. Every listed application is to be cryptographically signed and scanned before it is made available.

The preview targets Linux-capable x86_64 and ARM64 devices with at least 8 GB RAM. This is a target specification, not universal hardware certification or a claim that a production OS release is available today.

Hyperion OS is designed for post-quantum cryptography from the start rather than retrofitted later. The target primitives are ML-KEM (FIPS 203) for key exchange and ML-DSA (FIPS 204) for signatures, the NIST-standardized successors to the CRYSTALS-Kyber and CRYSTALS-Dilithium submissions, sitting behind a cryptographic-agility layer so the algorithm can be replaced without redesigning the protocol.

Conformance: No ML-KEM implementation of ours has been run against NIST ACVP or Wycheproof vectors; key exchange uses OpenSSL 3.5. Our ML-DSA-65 (FIPS 204) signing uses Cryspen's libcrux, whose verifier passes 210 of 210 cases of the Wycheproof ML-DSA-65 verify corpus in our own tests; package signing is moving to libcrux. UEFI Secure Boot signatures stay classical and are named as such. FIPS 140-2 validations moved to the CMVP Historical List on 22 September 2026; only FIPS 140-3 validations remain active.

The App Store's signing and scanning requirement is meant to handle sideloading risk, adware and bloatware at the distribution channel rather than one application at a time.

Hyperion OS, Ganglion (local inference), scoped post-quantum transport, and EntroCredits are provided at no cost. If you opt in, EntroEdge may contribute a small share of idle compute (5% of the machine, not 5% of one core) when the device is inactive. This is disclosed, revocable at any time with one click, and never active while the machine is in use. This exchange is the Covenant applied to computing: nothing is taken that isn't disclosed, and nothing disclosed is taken without consent.

Open source at launch:

• Kernel modifications
• The EntroEdge daemon
• Hyperion Shell
• The Hyperion Compat compatibility layer
• The post-quantum cryptography libraries

Kept proprietary:

• Research-kernel model weights (when an export exists)
• Research-kernel architecture
• The EntroEdge network protocol

The line is drawn at the point where opening the code would let someone reproduce the model or the compute-exchange network, not at the point of maximum disclosure.

EntroEdge Desktop for Windows is in private testing and not yet distributed; macOS is coming soon. A Developer Alpha is coming soon, with a Beta targeted for Q4 2026 and a 1.0 consumer release for Q1 2027, with a certified-hardware program following in 2028. These are engineering targets, not shipped commitments; where a date moves, the roadmap on the Hyperion OS page reflects the change rather than the original date.

For anything not covered here, including integration questions, enterprise deployment, or security review requests, use the contact page.