VaydeNet Contribute

Hardware-independent by design

One interface.
Any communication technology.

Keep embedded applications independent from the radios beneath them. VaydeNet provides a shared communication layer across ESP-NOW, LoRa, Wi-Fi, Bluetooth, Ethernet, and future transports.

Explore the architecture View on GitHub
01
Shared API
05+
Transport goals
Open
Source first
Close-up of an embedded circuit board
network_overview prototype
Transport abstraction Photo: Unsplash Application logic stays portable

Built for a mixed-radio world

  • ESP-NOW
  • LoRa
  • Wi-Fi
  • Bluetooth
  • Ethernet
  • + future transports

The problem

Radio-specific code creates brittle systems.

Embedded projects become difficult to evolve when application behavior, packet handling, and hardware APIs are mixed together. Changing one radio should not require rebuilding the whole application.

01

One communication contract

Applications describe what they need to communicate through a stable, transport-independent boundary.

02

Replaceable adapters

Transport-specific details live behind focused adapters, making new radio support easier to add and test.

03

Embedded-first core

Small, explicit components keep ownership clear and remain suitable for constrained devices.

Clean separation

A layered architecture developers can reason about.

Each layer has one job. Hardware details stay at the edge while the core coordinates communication through portable contracts.

  • Clear ownershipComponents own only the state they create.
  • Stable boundariesPlatform APIs do not leak into the portable core.
  • Incremental growthAdd transports without changing application logic.
01
Intent

Application

Defines what should be communicated.

portable
02
Coordination

VaydeNet Core

Applies shared message and engine contracts.

shared
03
Translation

Transport Adapter

Maps common intent to transport behavior.

replaceable
04
Delivery

Radio Hardware

Moves transport-native frames between devices.

platform

Developer experience

Less coupling. More room to build.

A focused set of architectural principles keeps the framework understandable as it grows.

Program to an interface

Application code targets shared contracts instead of ESP32, LoRa, or Ethernet APIs.

Portable logic

Compose focused modules

Small components make setup, transport selection, packet handling, and runtime behavior easier to trace.

Clear ownership

Validate at boundaries

Transport callbacks stay short while message validation and processing occur in controlled runtime code.

Predictable flow

Active development

Build the foundation before the features.

VaydeNet is evolving in deliberate layers. The current work establishes dependable boundaries before expanding into complete routing and delivery behavior.

Follow development on GitHub
  1. Current foundation

    Bootstrap and adapter boundaries

    Establish hardware identity, settings, transport initialization, and portable engine dependencies.

  2. Next layer

    Packet processing

    Consume queued frames, validate packet fields and integrity, then deliver logical messages.

  3. Future expansion

    Discovery, routing, and more adapters

    Grow capability behind the stable interface without coupling applications to new hardware.

Built in the open

Different disciplines. One shared network.

VaydeNet needs practical input across hardware, firmware, networking, testing, and documentation.

HW

Hardware

Validate boards, radios, pin mappings, and real-world operating constraints.

NW

Networking

Shape message contracts, discovery, routing, reliability, and security boundaries.

FW

Firmware

Build efficient portable components and focused platform adapters.

DX

Developer experience

Create examples, tests, documentation, and workflows developers can follow.

Contribute to VaydeNet

Help create a better communication layer for embedded systems.

Review the architecture, test a board, improve an adapter, or document what you learn.

Open GitHub Browse issues