Skip to content

Quickstart

This quickstart provides the essential steps to bring up your first DaaS-IoT node and understand the minimal workflow required to operate within the overlay network.

1. Select your Environment

Choose the combination of Platform SDK and Language Binding you need:

  • OS: GNU/Linux, Windows, macOS, Android
  • Languages: native C++, Python, Qt/C++, Java

Refer to the Environment Matrix for supported configurations.

2. Install the SDK

Each SDK provides its own installation instructions:

Platform SDKs

Language Bindings

Each installation page contains platform-specific instructions and links to package managers, bindings, and source builds.

3. Run your First Node

To initialize a DaaS-IoT node, a minimal configuration must be defined.
A node can either be created from scratch or restored from a previously saved configuration.

Option A — Create a new node (cold start)

When bringing up a fresh node, you must explicitly define:

  1. SID — the network domain the node belongs to.
    Nodes discover each other, synchronize, and exchange DDOs only if they share the same SID.

  2. DIN — the unique identifier of the node within the SID.
    It is used for addressing, routing, topology mapping and DDO delivery.

  3. Communication Drivers — at least one driver must be enabled
    (e.g., INET4, Bluetooth, or any platform-supported link layer).
    Drivers determine how the node physically exchanges packets.

Once these parameters are set:

  • initialize the runtime
  • join the overlay
  • validate connectivity (discovery)
  • allow the node to enter time synchronization (dATS)

Option B — Restore an existing node (warm start)

If a configuration file from a previous session is available, the node can be restored directly:

  • the stored SID, DIN, driver configuration, and timing parameters are automatically loaded
  • only the initialization and join steps are required

This is the preferred method for persistent devices and stable deployments.

4. Explore the Official Examples

Each SDK includes dedicated examples that demonstrate:

  • Overlay initialization
  • Driver configuration
  • Discovery & autonomous networking
  • Time synchronization (dATS)
  • Sending & receiving DDOs
  • Working with typesets
  • Handling Frisbees

You can find them directly inside each SDK section:

Platform SDK Examples

Language Examples

And the full example directory is always available on GitHub:

👉 https://github.com/sebyone/daasiot-sdk/tree/main/examples

5. Next Steps

To deepen your understanding, continue with:

DaaS-IoT is designed to be predictable, modular, and cross-platform—start small, then integrate features progressively.