The paradigm

Reachability of the device, delivered as a service.

Communication is no longer something you implement per device. A local service absorbs the complexity of managing transmission channels and offers one unified model to reach remote devices with whatever technology is most effective in the real operating context.

The vocabulary

Six primitives, one mental model

A node hosts the DaaS stack and uses locally available communication resources to reach other nodes. Everything else builds on these.

Node

Connected when a channel reaches another node; active when its timer is aligned with the already-active nodes.

DIN

DaaS IdeNtifier — identifies a single node instance within the network.

SID

System IDentifier — identifies the distributed system (segment) a node belongs to.

DDO

DaaS Data Object — the unit of information exchanged. A recognizable object in the network, not a raw packet.

Typeset

Semantic classification of a DDO — state, telemetry, command, result, notification, event — so nodes read meaning uniformly.

DME

DaaS-MEssage — encapsulates DDOs for transfer. Three variants: transfer, control, service.

The API

Event-driven push / pull

Total decoupling between application logic and transport. The sender locates a node and pushes a DDO; the receiver reacts to a callback and pulls it. The stack handles channel choice, bridging and synchronization.

locate(din) — find the destination node
push(din, typeset, ts, payload) — send a DDO
onDDOReceived() → pull() — receive it

communication model

# sender
locate(din)
push(din, typeset, ts, payload)

# receiver
onDDOReceived()  →  pull()

Time without a server

The dATS synchronization algorithm

Nodes exchange data to compute drift and offset compensation, aligning local time to the network time set by the oldest active node — the time-master — within a user-defined network period. A node exists only if it is temporally synchronized.

server-less resilient robust scalable precise

Experimental results — Case 4 · 3 heterogeneous nodes

380 ms

avg sync time

±6.3 ms

network-period error

12 pkt

avg ATS per sync

A remote node desynced by up to a full day converges to network time in hundreds of ms, with error narrowing to ±1 ms — unaffected by transfer times and network latency.

Protocol efficiency

A header that stays under 32 bytes

Variable-size, variable-meaning encapsulation keeps the DME + DDO header compact — efficient even over frame-limited underlay protocols.

Parameter	Underlay · IPv4 / TCP	Overlay · DaaS INET4
Packet header	40 bytes (max 60)	32 bytes (max 32)
Traffic footprint	baseline	up to ~80% less
Measurement tool	standard (TCP-level only)	`dsperf` (layers 5–6)

Overlay overhead is measurable but negligible against the gains in self-configuration, security and scalability — validated with the University Metrology Department using dsperf.

In motion

Representative scenarios

Multi-driver failover

Ethernet or Wi-Fi drops while DaaS-IoT keeps delivering DDOs over the best available driver: ETH → WiFi → BLE.

Temporal consensus

After the first DDO-ATS exchange, nodes converge to a shared time — no central clock, no round-trip.

Autonomous discovery

A new node boots, discovers neighbors, joins the topology and synchronizes — with virtually zero configuration.

Intelligent routing

Prefers A → C → B over A → B when the longer path is faster and more reliable — best path, not shortest.

Integrations

It plugs into your world

ROS2

DaaS-ROS Bridge

An open-source package letting ROS2 nodes talk over a DaaS overlay mesh — opening up distributed robotics and industrial automation.

In-browser

JavaScript node

A browser tab can act as a full DaaS node, exchanging DDOs in real time with a Node.js peer — the site's live "try it in-browser" lab.

Ready to build on the mesh?

Pick an SDK, run the examples, and let your devices find each other.

Go to the SDK Hub Back to overview