Skip to content

LINUX EDGE AGENT

Zyvor Device Agent

Discover the box, expose physical interfaces, publish to Nodra, and expose Fleet-compatible inventory — a small Linux-native hardware foundation for an ARM64 edge gateway, with no Kubernetes required.

Get the highlights.

  • 241
    REST API endpoints
  • 8
    Guided tutorials, first build to production
  • 3
    Auth modes — none, bearer, mTLS
  • 92
    CLI subcommands in one binary
  • 2
    CPU architectures — arm64 and amd64

Linux hardware edge agent for Zyvor — discover the box, expose physical interfaces, publish to Nodra, expose Fleet-compatible inventory.

Why this exists

Zyvor already has higher layers for workload/runtime control and fleet/data-plane responsibilities. What was missing was a small Linux-native hardware foundation that can run directly on an ARM64 gateway without Kubernetes. Device Agent provides that boundary.

It intentionally does not interpret Modbus registers, CAN/J1939 PGNs or OPC-UA nodes. It reports physical capabilities and gives sensor drivers a stable local contract. Nodra owns industrial protocol semantics, routing and offline store-and-forward. Fleet owns remote lifecycle and desired state.

For the full picture — quick start, REST API reference, product boundary, repository map and license — see the README on GitHub.

Start here

  • Tutorials — guides index — a numbered series from first build to production/container deployment
  • FAQ — licensing, support, production-readiness, cloud/data questions for anyone still evaluating
  • Troubleshooting — real issues people hit, with the actual fix
  • Reference hardware — the capability profile a board needs, not a fixed SKU list
  • Architecture — the full security-model picture and what's still open before GA

v0.1 scope, at a glance

  • 🔌 GPIO / I2C / SPI / UART / CAN / USB / watchdog discovery
  • 🚌 Read-only SocketCAN health plus passive RS485 declaration
  • 📼 Disabled-by-default, RX-only CAN frame capture on an explicit allowlist
  • 🎥 Live camera snapshot + MJPEG streaming, off by default (--features camera)
  • 🔐 Bearer, mTLS, and optional TPM2-backed identity
  • 🧩 Out-of-process sensor plugins — Rust, Go, C, Python, or shell
  • 📊 REST API plus a Prometheus metrics endpoint
  • 📡 Nodra MQTT publishing and a Fleet inventory bridge

Is this for you?

Device Agent is a small, single-purpose, open-source (Apache-2.0) hardware layer for a Linux edge gateway. If you need a home-automation hub or a full container fleet/OTA platform instead, one of these is probably a closer fit; see the README's full comparison table for AWS IoT Greengrass and Azure IoT Edge as well.

  • Device Agent

Hardware inventory, health, and bounded sensor/bus access. No cloud dependency required — Nodra/Fleet integration is optional. Industrial protocol decoding and fleet/OTA orchestration are deliberately out of scope, handed to Nodra and Zyvor Fleet.

  • Home Assistant

Home automation hub, integrations, and local rules. Industrial fieldbus support, if any, comes through community integrations, not a built-in primitive.

  • balena

Fleet OS plus container deployment/OTA as its core feature, backed by balenaCloud (proprietary) for fleet management.

  1. Counted from the README's API table: health, ready, status, inventory (+ alias), refresh, interfaces, industrial (+ can, serial), CAN capture (+ recent, stream), thermal, integrations (+ fleet inventory), plugins (+ sample), sensors (+ by id), events (+ recent), doctor, and /metrics. See the API table. ↩
  2. serve, inventory, industrial, doctor, fleet-inventory, plugins, sample, enroll, identity. See Processes. ↩