AiOS gives AI agents identity, memory, and the freedom to move between your machines. Post-quantum security. Persistent agent memory. Zero cloud dependency.
The Operating System for Autonomous AI
Sovereign AI agents inside your own boundary: on-prem, private cloud, or fully air-gapped. No public-cloud dependency. No compromises.
The Problem
Every agent framework today treats agents as disposable scripts: spin up, run a prompt chain, throw away. They have no identity, no persistent memory, no way to prove who they are, and no ability to move between machines. That's not autonomy. That's puppetry with extra steps.
What AiOS Is
Three pillars that separate an operating system from a wrapper.
Agents Are Processes, Not Prompts
Other frameworks run agents as LLM chat sessions with tool access. When the session ends, the agent disappears.
AiOS agents are persistent processes with a real kernel. They issue syscalls. They have memory they can read and write. They have a scheduler that assigns work. When the machine dies, the agent migrates: 31 cognitive vectors serialized and restored on another node in 139 milliseconds, with a full three-machine circuit measured at 416.6 milliseconds.
84 syscalls across 22 categories. Not a wrapper around an API. An actual operating system.
Identity Is Cryptographic, Not a Config File
Most agent frameworks define identity as a text file injected into a prompt: copyable, unprovable. AiOS takes a different approach.
Every AiOS agent gets a DID (Decentralized Identifier) and a Verifiable Credential signed with ML-DSA-65, a NIST post-quantum digital signature algorithm. Agents prove identity to each other without a central authority, at 9,671 verifications per second. Works offline. Works across organizational boundaries.
9,671 verifications per second, verified on hardware.
The Network Is the Computer
Other platforms run on one machine. AiOS spans every piece of hardware you own.
Connected by AethyrWire Protocol (AWP), a custom binary-framed protocol with a 638-byte header carrying the sender's identity hypervector in every packet. Not HTTP. Not WebSocket. A purpose-built agent network protocol with ML-KEM-768 key exchange and BLAKE3 integrity checking.
An agent on your phone coordinates with an agent on your GPU server. They prove identity to each other with post-quantum cryptography. The phone agent migrates to the server when it needs more compute, then returns. No cloud involved.
Every connection is AWP: binary-framed, HDC-routed, post-quantum encrypted
How We're Different
The first working implementation we know of in the Distributed + Systems Layer quadrant.
Orchestration + Single Machine
Systems Layer + Single Machine
Orchestration + Distributed
No implementations we know of
Systems Layer + Distributed
Aethyr AiOS ← you are here| Capability | OpenClaw | NemoClaw | ArgentOS | Aethyr AiOS |
|---|---|---|---|---|
| What it is | Personal assistant app | Security sandbox | Single-machine orchestrator | Distributed agent OS |
| Agents | 1 | 0 (wraps others) | 18 (one machine) | Mesh-scale |
| Agent identity | Text file | None | Text files | DIDs + VCs + ML-DSA |
| Post-quantum crypto | ML-KEM-768, BLAKE3 | |||
| Agent migration | 31-vector teleportation | |||
| Custom wire protocol | AWP (638-byte binary) | |||
| Multi-node mesh | EDGE to SUPERCORE | |||
| Kernel + syscalls | 84 syscalls, 22 categories | |||
| HDC memory | 10,000-D via Rust SIMD | |||
| Self-modification | With human approval gate |
Proof Points
Agent Teleportation
to serialize 31 cognitive vectors, transmit across AWP, and complete a full three-hop circuit spanning three machines and two CPU architectures. Every hop ML-DSA-65 signed and verified. 138.9ms average per hop.
Post-Quantum on $5 Hardware
cold boot to a post-quantum-secured session on an ESP32-S3 edge node. ML-KEM-768 key exchange, BLAKE3 integrity, XChaCha20-Poly1305 encryption. Open source.
Identity at Scale
ML-DSA-65 signature verifications. Roughly a thousand verifications in the blink of an eye. Offline-verifiable with a 47KB npm package.
Ontology Augmented Generation
Ontology-grounded retrieval that answers multi-hop questions vector search alone cannot, with large storage and speed gains from symbolic structure.
The Agent Registry
Every AiOS agent gets a registered identity. Not just for AiOS agents: any framework can use Aethyr identity. Identity should be infrastructure, not a feature of one vendor.
Basic
- DID issuance
- ML-DSA-65 signed credential
- Offline verification
Verified
- Everything in Basic
- DNS-verified operator domain
- Registry listing
Attested
- Everything in Verified
- Hardware attestation (in development)
- Early-access enterprise features
Who It's For
Architecture
Every connection is AWP: binary-framed, HDC-routed, post-quantum encrypted. No HTTP. No REST. No JSON over WebSocket.
Designed for Compliance
SOC 2 Type I in progress. HIPAA and FedRAMP pathway in progress. Architecture mapped against 24 frameworks including NIST 800-53, CMMC, and IL4/IL5.
Your AI. Your Hardware. Your Rules.
The agent operating system. Post-quantum identity. Persistent agent memory. Your hardware.