What Is Mesh of Things?

Mesh of Things is a control plane for fleets of internet-connected devices. It connects devices to a private encrypted overlay network and gives operators one dashboard for provisioning, Docker Compose deployments, runtime visibility, logs, and remote terminals—without exposing a device-management port to the public internet.

Get started: Create an account

Connect Remote Devices

Run the Mesh of Things agent as a Docker container on each device. Provisioning assigns private IPv4 and IPv6 addresses and issues a device certificate that defines its identity and security posture.

Devices on the same network can communicate directly when their certificates and inbound firewall rules allow it. If a direct route is unavailable and the organization is eligible, a hosted relay can forward the encrypted packets without decrypting them.

Typical uses include:

Industrial and edge computing

Remote servers and cloud workloads

Digital signage

Home and office infrastructure

Deploy Applications Over the Air

An app in Mesh of Things is a versioned Docker Compose definition. Assign devices to an app, save a version, and promote it to queue the rollout across the fleet. Offline devices keep their desired state and deploy after they reconnect; a newer promotion supersedes stale queued work.

Environment values, write-only secrets, and private-registry credentials are managed separately from the Compose definition and resolved at deployment time.

Operate Devices Remotely

For devices with dashboard access enabled, the device detail page provides current container state, logs, and terminal sessions. This helps operators diagnose and repair workloads without traveling to the hardware or publishing Docker and SSH management ports on the internet.

Organization event history adds a searchable view of Docker runtime activity across devices. Check Settings → Billing for current feature availability.

Separate Fleets and Limit Access

Networks create isolated trust and address spaces inside an organization. Firewall groups define reusable allow-only inbound rules, while peer isolation prevents a device from trusting other device certificates at all.

These controls operate at different layers:

• networks decide which devices can establish trust with one another;
• peer isolation removes device-to-device trust for a specific certificate; and
• firewall rules restrict accepted traffic after trust exists.

Automate Safely

The scoped HTTP API supports scripts and CI workflows. The MCP endpoint exposes the same bounded fleet-management capabilities to compatible AI clients. Interactive terminals, logs, and live container access are deliberately excluded from both token-based interfaces.

Learn more in API and MCP automation.