Configurations
A Configuration in Admiral defines the desired state of containerized workloads running on your physical edge nodes, autonomous mobile robots (AMRs), industrial IoT appliances, and interactive kiosks.
Fleets
A Fleet is the fundamental logical grouping mechanism in Admiral. Fleets group hardware assets that share the same operational mission: active configuration version, network failover credentials, OS component version baselines, and spatial sensing policies.
Device Documents & Desired State
Every device, fleet, and configuration in Admiral has a single document: one place that says what the device should be running (spec) and what it is running (status). You can read it in the dashboard, edit it from the CLI, keep it in Git, and apply it back. A robot that was offline for a week converges on the latest document when it reconnects; nothing is lost in a queue of one-off commands.
Networking & Failover
Admiral is engineered for high-availability operation across unpredictable physical network environments: noisy warehouse Wi-Fi, moving autonomous mobile robots (AMRs), remote cellular gateways (4G/5G), and firewalled enterprise corporate intranets.
Platform Boundary & Customisation
Teams moving an existing robot or appliance stack onto Admiral usually ask the same question: what stays in my workload, and what moves into the platform?