Browse documentation

Eryon technical portal

Getting Started

The public project is in active development. No production release is currently published.

Source-groundedUpdated 2 November 2026Development status

Requirements

The Python components require Python 3.11 or newer. The automated Mesh Node Installer targets systemd-based Ubuntu and Debian hosts, but a public signed installer release is not available. A real node pilot requires a disposable Linux host, a reachable test Control endpoint, enrollment credentials, TUN access, and permitted UDP traffic.

Inspect the local Core

python3 -m eryon --help
python3 -m eryon --version
python3 -m eryon doctor

The Eryon Core help currently lists version, doctor, status, daemon status, network status, peers, routes, and sessions. The diagnostics commands do not install a node or enroll it.

Inspect a managed daemon

For a system-managed DVeMesh daemon, the local IPC socket is root-only by default. These commands are read-only and require a daemon already configured by an administrator:

sudo eryon daemon status
sudo eryon network status
sudo eryon peers
sudo eryon routes
sudo eryon sessions

Safe pilot sequence

  1. Use a clean, disposable Ubuntu or Debian Linux host; do not use a production node.
  2. Review the Installer host requirements and the planned configuration.
  3. Create a dedicated test network in an existing test Control deployment and create a short-lived enrollment token.
  4. Use the supported Installer only after obtaining a separately verified release artifact and trust anchor.
  5. Enroll a second test device and verify peer session, route, ACL, and packet delivery separately.

Three independent Linux hosts and actual UDP have not yet established a complete A → B → C production-like path.

No public install artifact

Do not copy an install command from an old component README and assume it publishes the current Eryon build. The current status is listed on the Downloads page. Use Development for source-level checks.