Multi-device Networking
GroundControl is designed to scale from a single instrument on one machine to dozens of instruments spread across multiple lab locations. Here is how the topology works in each scenario.
One edge machine, multiple instruments
The simplest multi-device setup: one GroundControl installation managing several instruments connected to the same machine.
Connector A ──┐
Connector B ──┤── GroundControl ── UniteLabs Platform
Connector C ──┘
Each instrument gets its own connector. All connectors run as separate processes under one GroundControl instance. Add each device through Devices → Add Device and assign it a connector as usual.
There is no hard limit on the number of connectors per GroundControl. In practice, the limit is the resources available on the edge machine.
The above architecture is still a work in progress. In the current state, while managed by GroundControl, each connector establishes an independent, direct connection to the cloud as sole communication channel. A second channel via the GroundControl relay will be rolled out soon.
┌── GroundControl Connector A ──┤ Connector B ──┤─────────────────── UniteLabs Platform Connector C ──┘
Multiple edge machines
If instruments are spread across multiple benches or rooms — each with a dedicated computer — run one GroundControl per edge machine. All GroundControl instances in the same tenant share the same connector registry and appear in the same platform workspace.
Lab bench A Lab bench B
┌──────────────┐ ┌──────────────┐
│ Connector 1 │ │ Connector 3 │
│ Connector 2 │ │ Connector 4 │
│ GroundControl│ │ GroundControl│
└──────┬───────┘ └──────┬───────┘
└──────────┬───────────────┘
UniteLabs Platform
Each machine needs its own GroundControl installation. Sign in with the same tenant credentials on each.
Instruments on separate network segments
If the edge machine cannot directly reach an instrument (e.g., the instrument is on a restricted VLAN), you have two options:
Option 1 — Relocate GroundControl. Run GroundControl on a machine that is already on the same network segment as the instrument. This is the simplest solution and avoids network routing complexity.
Option 2 — Remote connector. Run the connector on a machine co-located with the instrument and add it to GroundControl as a remote. The connector runs independently and GroundControl connects to it over the network:
- Discovered (mDNS): if the connector broadcasts on the local network, GroundControl finds it automatically
- Manual remote: enter the connector's hostname and port directly in the Add Device wizard
See Add a Connector — Manual Remote for the setup steps.
Multiple lab locations
For connectors in physically separate locations (different buildings or sites), the recommended setup is:
- Install GroundControl at each location
- Enable cloud connectivity at each location (Connect to UniteLabs Platform)
- All connectors appear in the central platform workspace, accessible from anywhere
Without cloud connectivity, connectors are only reachable from within their local network.