DOCSEARCHbyAlgolia
Submit Docs

Admiral Documentation

website·Indexed 30 days ago

https://docs.admrl.co

A platform for managing autonomous machines and distributed hardware. Admiral provides a base OS for edge devices, featuring OCI workload execution, fleet organization, AirDetect™ spatial intelligence, and secure device provisioning via BLE and auto-provisioning. The platform includes a REST API, IAM policies for resource hierarchy, and support for AI accelerators including NVIDIA x86 GPUs and Jetson AGX Orin.

Tokens
28.6K
Snippets
76
Records
208
Agent score
50%

What's inside Admiral

  1. Overview of Admiral Rollouts Engine

    The Rollouts Engine provides controlled, phased deployments for edge fleets, autonomous robots, and kiosks. It mitigates operational risks—such as robotics mission disruption, network congestion, and widespread outages—through staged batching, pre-execution impact simulation, per-device failure reporting, and on-device rollback.

  2. Overview of AirDetect spatial presence sensing

    AirDetect is an embedded spatial presence and foot-traffic intelligence service that transforms connected displays, kiosks, or edge devices into anonymous physical traffic sensors. It uses a passive sensing model via existing onboard Bluetooth radios to listen to surrounding packets from smartphones, wearables, and portable devices without broadcasting signals or using cameras/optical sensors. All data is anonymized at the edge to ensure zero PII (Personally Identifiable Information) is stored.

  3. Overview of Admiral GPU driver supply for Jetson Orin

    Admiral provides the NVIDIA driver for Jetson AGX Orin, Orin NX, and Orin Nano by running the container image as the device's system userspace. The platform supplies the kernel, GPU firmware, and matching NVIDIA driver libraries (including libcuda.so.1), which are mounted read-only into the userspace at startup. This covers both CUDA compute and GPU display output (EGL, OpenGL, Vulkan). Users do not need to install a desktop NVIDIA driver, Docker daemon, or NVIDIA Container Toolkit on the device.

  4. Overview of the Admiral Device Detail View

    The Device Detail View (accessible via /devices/<device-id>) provides deep visibility and command control over edge hardware nodes, robots, and kiosks. It is organized into nine functional tabs: Activity, Details, Configuration, Network, Services, Volumes, Real-Time Logs, Images, and AirDetect™ Presence.

  5. Overview of the Admiral Edge Orchestration Platform

    Admiral (app.admrl.co) is an edge orchestration platform and immutable operating system designed for Autonomous Mobile Robots (AMRs), Automated Guided Vehicles (AGVs), Edge AI Nodes, Smart Kiosks, and Distributed Hardware Fleets. It replaces heavyweight desktop Linux distributions with a lightweight, memory-resident supervisor that boots directly into an OCI container runtime, minimizing RAM usage (approx. 100MB) and enabling sub-10-second cold boots to maximize resources for SLAM, navigation, and perception models.

  6. Overview of Fleet Management capabilities

    The Fleet Management system provides a centralized dashboard for managing and monitoring an entire device fleet. Key capabilities include:

    • Fleet Management: Centralized control and monitoring of all devices from a single dashboard.
    • Real-time Monitoring: Live tracking of device status, performance metrics, and compliance levels.
    • Compliance & Security: Tools to ensure all devices adhere to established security standards and regulatory compliance requirements.

  7. Understand Admiral's Organization Hierarchy and Tenancy

    Admiral utilizes an organization-based multi-tenant security architecture. Access is scoped to an Organization, which can be structured as follows:

    • Tenants: Independent organizations that contain their own fleets, devices, configurations, users, and service accounts.
    • Nested Sub-Organisations: Available for enterprise accounts, allowing the creation of child organizations where governance and billing roll up to the parent entity.

  8. Admiral OS BLE Provisioning Overview

    Admiral OS uses BLE exclusively for initial device setup. Once a device reaches the FULLY_PROVISIONED state, the BLE radio advertisement is permanently disabled to eliminate the BLE attack surface. Re-enabling BLE requires a physical factory reset. The protocol supports multi-device batching (configuring 10+ devices simultaneously) and uses application-layer X25519 ECDH key exchange with AES-GCM encryption for sensitive data like Wi-Fi passwords and pairing keys.

  9. Understand Admiral OS Auto-Provisioning capabilities

    Auto-provisioning allows the creation of customized Admiral Base OS installer images (ISO for x86_64, raw IMG for ARM) that automate the initial boot process. Key capabilities include:

    • Automatic Registration: Skips manual Crockford Base32 token entry to claim the device under an organization.
    • Fleet Association: Automatically assigns the machine to a specific fleet (e.g., Warehouse-AMR-Zone-1).
    • Network Pre-configuration: Includes facility Wi-Fi credentials (SSID and passphrases) for immediate connectivity.
    • Automated Workload Deployment: Automatically pulls and launches the assigned OCI workload container upon first boot.

  10. Understand Admiral's immutable storage and networking architecture

    Admiral utilizes a specific architecture for reliability in industrial environments:

    • Admiral Mesh: A TCP/UDP control fabric designed for high-latency, low-reliability, and intermittent links (e.g., cellular or noisy Wi-Fi) with automated transport fallbacks.
    • CoW Storage Engine: A Copy-on-Write (CoW) filesystem for persistent data partitions featuring transparent compression, persistent subvolumes, and atomic checkpoints to prevent corruption from sudden power loss.

  11. Understand Admiral workload hardware and system access

    Admiral workloads run as root by default and are not sandboxed cloud containers. They have direct access to host hardware and system resources, including:

    • Device Nodes: Full access to the host /dev tree with hotplug support.
    • sysfs: Read-write access to /sys/class, /sys/devices, /sys/bus, /sys/block, /sys/module, /sys/firmware, and /sys/power.
    • Capabilities: Includes CAP_SYS_ADMIN, CAP_NET_ADMIN, CAP_NET_RAW, CAP_SYS_NICE, CAP_SYS_RESOURCE, and CAP_MKNOD.
    • Scheduling: Support for real-time priorities (SCHED_FIFO / SCHED_RR) and unlimited locked memory for DMA and pinned CUDA buffers.
    • Networking: Private network namespace by default; physical interfaces are accessed directly when Host Network is enabled.

  12. Understand and organize Admiral Fleets

    A Fleet is the fundamental logical grouping mechanism in Admiral. It groups hardware assets that share the same operational mission, including active configuration versions, network failover credentials, OS component version baselines, and spatial sensing policies.

    Recommended organization strategies based on operational topology include:

    • AMRs & AGVs: Group by zone or function (e.g., Warehouse-AMR-Zone-1, Logistics-Sorting-AGVs).
    • Robotics Cells: Group by line or stage (e.g., Assembly-Line-Cell-A).
    • Kiosks & Displays: Group by location (e.g., Sydney-Flagship-Displays).
    • Deployment Tiers: Group by environment (e.g., Production-Fleets, Staging-Canary, Hardware-Lab-Test).