Deploy multi-network device meshes using Device Connect server and NATS
Introduction
Learn when to use Device Connect server for multi-network deployments
Run devices and an orchestrating agent on a Device Connect server
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  30 min
Last updated:  13 Aug 2026
Skill level:
  Introductory
Reading time:
  30 min
Last updated:
  13 Aug 2026
Authors:Kavya Sri Chennoju, Arm
Annie Tallund, Arm
Arm IP:Cortex-A Neoverse
Tags: Libraries Linux macOS Python Docker
Authors:
  • Kavya Sri Chennoju, Arm
  • Annie Tallund, Arm
Arm IP:
Cortex-A Neoverse
Tags:
Libraries Linux macOS Python Docker

Who is this for?

This Learning Path is for developers who have completed the Device-to-device Learning Path and want to build a globally connected fleet of devices and AI agents on top of their Device Connect mesh. You'll add a server layer that gives you persistent registry, distributed state, and security features (commissioning, ACLs) so devices and agents on different networks can find and call each other through a single namespace. If you're new to Device Connect, start with the device-to-device Learning Path first.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Understand what the Device Connect server adds on top of the edge SDK and when you'd reach for it
  • Provision a hosted tenant on the Device Connect portal and download per-device NATS credentials
  • Commission an example primary device and a secondary device against your tenant using the credentials the portal issues
  • Discover and invoke commissioned devices from a Python client using `device-connect-agent-tools`
  • Connect a Strands AI agent to the same tenant

Prerequisites

Before starting, you will need the following:

  • Complete the Device-to-device Learning Path to understand Device Connect edge SDK basics
  • An account on the Device Connect portal
  • A Raspberry Pi 5, another Linux device, or your development machine to use as the example primary device
  • A development machine for the secondary device and Python client
  • Basic familiarity with Python and the command line

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll extend a Device Connect mesh across networks with a server and NATS authentication. First, you’ll provision a private tenant, download device credentials, and commission primary and secondary devices. Then, you’ll discover devices and invoke RPCs from Python to verify reachability. You’ll connect a Strands AI agent so devices and agents share one authenticated registry.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I know my tenant is ready before I commission devices?
After you sign in to the Device Connect portal, a private tenant is created. You should be able to download per-device NATS credentials and use them to commission a device. If the Python client can discover that device, your tenant is ready.
Which credentials should I use on the primary and secondary devices?
Use the per-device NATS credentials you download from the portal for each specific device. Don’t reuse a single credential across multiple devices.
What result should I expect when discovery works from the Python client?
The client lists commissioned devices in your tenant and can invoke their RPCs. Successful calls confirm that routing over the Device Connect server and NATS is working across networks.
What should I check if the client cannot discover a commissioned device?
Verify the device was commissioned to the same tenant and is running with the correct NATS credentials. Also confirm the client is targeting that tenant and repeat discovery after the device is online.
How do I connect a Strands AI agent to the same tenant?
Configure the agent with the tenant details and portal-issued credentials, then start it. The agent should appear under the tenant’s namespace and discover and invoke commissioned devices such as the Python client.
Next