Hyperion OS

Hyperion OS is an AI-native operating system: AI is a kernel-level primitive rather than an application running on top of a conventional desktop. It is Layer 3 (L3) of EntroStack, EntroVerse's sovereign compute vertical, sitting on EntroKernel (L4) and, further down, sovereign silicon and energy infrastructure. Above it sit the inference runtime, compiler, tensor framework, and application layers that ship independently.

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 ship 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 kernel-level assistant rather than through a separate app.
• Hyperion Compat: a compatibility layer for running existing Windows applications natively, without dual-boot or a separate virtual machine.
• EntroEdge: the daemon that contributes idle CPU/GPU cycles to the wider EntroEdge compute network in exchange for credits. Off by default when the machine is active; see §4.
• Hyperion App Store: the distribution channel for third-party applications. Every listed application is cryptographically signed and scanned before it is made available.

The OS runs on any hardware capable of running Linux; x86_64 and ARM64 are supported at launch. A certified-hardware list is planned for 2027 but is not required to run the OS today.

Hyperion OS is designed to be post-quantum secure at the kernel level 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. The design rule is that classical-only schemes (RSA, plain ECDH/ECDSA) are never the sole mechanism anywhere in the stack.

Conformance, stated plainly: naming a standard is a claim a reader can check, so we state where we actually are. No ML-KEM implementation here has been run against NIST ACVP or Wycheproof vectors. Our earlier hand-written ML-DSA signer was measured against Project Wycheproof and accepted 0 of 79 valid signatures. It carries ML-DSA-65 parameters but is not FIPS 204 conformant, and we say so wherever it appears. A conformance-tested signing path now exists and passes the official corpus; migrating each system onto it rotates keys, so it is being done deliberately rather than all at once.

The Hyperion App Store's signing and scanning requirement exists specifically to rule out sideloading risk, adware, and bloatware as a distribution-channel problem rather than a per-application one.

Hyperion OS, HERCULES, quantum-safe transport, and EntroCredits are provided at no cost. In exchange, EntroEdge may contribute a small share of idle compute (on the order of single-digit percent) 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:

• HERCULES model weights
• HERCULES 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 available now; macOS is coming soon. A Developer Alpha is targeted for Q3 2026, a Beta 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 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.