Kits - Hoplynk

A kit is the physical hardware you deploy in the field. Think of it as a self-contained communications and sensing node: it has its own internet uplink (or multiple), its own local network, and a small computer (the Pi) that manages everything and reports back to the cloud.

What’s in a kit

Component	Role
Raspberry Pi (Hydra)	Runs connectors, manages local services, reports to cloud
UniFi router	WAN failover/load balancing, local LAN gateway
Cameras (Reolink or similar)	Video and detection feeds
Starlink dish	Primary WAN link
Cellular modem	Secondary WAN link
Silvus radio (optional)	Tactical WAN link — mesh networking over RF
WiFi AP	Local wireless for on-site devices

How a kit is identified

Every kit has a unique Kit ID — a UUID assigned when the kit is provisioned in the dashboard. You’ll use this ID in every API call to scope data to a specific kit.

HOPLYNK_KIT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

What a kit reports

Once online, a kit continuously reports:

GPS location — from Starlink or a connected GPS source, at 1Hz
Link health — throughput, latency, and packet loss per WAN link
Asset status — all connected devices and their feeds
Gateway telemetry — CPU, memory, connected clients

Kit lifecycle

Provision → Deploy → Online → Reporting

Provision — create the kit in the Argus dashboard, get a Kit ID and credentials
Deploy — bring the kit to its location, power on
Online — Pi connects to cloud, registers all assets
Reporting — live data flows; kit appears on the map in Argus

Next

Deploy a kit

Hardware setup and provisioning walkthrough.

Assets

The devices connected to a kit.