The project
Eryon is a private-network project built around three separately developed components: Eryon Core, DVeMesh, and DVeProto. The current terminal path connects Eryon Core to the Control-managed MeshDaemon through read-only local IPC. MeshDaemon owns the overlay dataplane and Control remains the topology and policy authority.
Development status. Core, daemon IPC, topology and ACL management, Installer, and local release verification are present in the source tree with automated test coverage. Independent multi-host connectivity and public release distribution have not been verified.
Read this first
Use the Getting Started guide for the development and pilot path. The Architecture and Network Model pages explain the control and data planes. For cryptography, identity, or trust decisions, read Security, Identity, and Trust Model.
Status language
- Implemented means relevant code exists in this checkout.
- Tested locally means automated or local integration tests cover the stated path.
- Not verified means the scenario has not been confirmed on independent hosts or a public service.
- Planned means no current implementation should be assumed.
Source boundaries
Eryon Core does not replace the cryptographic protocol, peer-session manager, or packet engine. DVeMesh implements membership, topology, ACL distribution, and the Linux mesh dataplane. DVeProto supplies protocol identity and session primitives. A capability in one component is not automatically a supported product guarantee for the entire stack.
Documentation sections
Getting Started
Development requirements and the honest pilot path.
Architecture
Component roles and the Control/Data Plane split.
Security
Cryptographic mechanisms, identity limits, and operational boundaries.
CLI Reference
Commands checked against the current CLI help and source.
Downloads
Release publication and artifact verification status.
Service Status
Monitoring availability and status-report limits.