Browse documentation

Eryon technical portal

Roadmap

The near-term priority is a dependable terminal node and real multi-host network validation. Browser work remains postponed.

Source-groundedUpdated 2 November 2026Development status

Completed in the current source

  • Eryon Core configuration, persistent local registry, runtime abstractions, and CLI diagnostics.
  • Read-only Unix IPC integration from Eryon to the Control-managed MeshDaemon.
  • Control-managed FULL_MESH and SELECTIVE topology policy with an explicit neighbor set.
  • Network-scoped ACL API and live snapshot enforcement with default DENY.
  • DVeMesh route learning and bounded mesh transit forwarding implementation.
  • Standalone Mesh Node Installer and independent Ed25519 manifest bootstrap/release tooling; local automated validation is documented.

In Progress

  • Validate A ↔ B ↔ C across three independent Linux hosts with actual UDP, TUN, route advertisements, ACL, and return traffic.
  • Confirm node failure detection and recovery on real hosts.
  • Validate a clean Ubuntu/Debian installation lifecycle against a test Control environment.
  • Establish release compatibility, external HTTPS distribution, and independent trust-anchor delivery.

Planned

  • Operational hardening and reproducible supported release channels after external verification.
  • Document and test upgrade, recovery, and key revocation procedures on disposable hosts.
  • Improve terminal diagnostics and monitoring around the daemon-owned dataplane.

Research

  • IPv6 data plane and broader NAT behavior.
  • Independent monotonic release/rollback state for managed fleets.
  • Public relay operations and availability model.

Postponed

Browser functionality is postponed. The terminal daemon and CLI are the foundation for future interfaces; no browser networking feature is represented as available.