Fleet
Operating a device fleet, from the SD card to continuous updates.
In brief
Fleet is the management of your devices: the ones you install at your customers' sites, inside a machine, a fridge, a kiosk.
It covers their whole life. You build the memory card from a form, you insert it, the device declares itself on first boot. From then on you point to a version, and the whole fleet updates itself.
The fleet is then managed without travelling: you see each machine's state, you intervene remotely, you update, you cut off a compromised device in one click.
Fleet can be bought on its own, and also serves as the foundation for the Octopoda business applications.
What it brings : A small team operates thousands of devices spread across the field, with no engineer call-outs.
In detail
Fleet builds, deploys and monitors an account's device fleet — Raspberry Pi and Linux ARM/AMD machines, development workstations, Android payment terminals — from a single console. You build the image, you write the card, the device enrols itself on first boot, then you point to a version and the whole fleet converges. From there the fleet is managed remotely: real-time monitoring, intervention without a permanent session, agent and operating system updates, firewall, device cut-off — with a tamper-proof record.
Fleet can be bought on its own. It is complete fleet management, for those who first want to operate their devices. It is also the foundation of the Octopoda suites: Data and Distrib are switched on for the same devices, with no migration.
Who it is for
| Audience | What they find |
|---|---|
| Operator, fleet manager | Fleets, deployments with a preview of changes, monitoring, remote actions, images ready to write. |
| Field technician | Time-limited certificate access, configuration over a USB cable, embedded console, standalone tool on five platforms. |
| Developer, integrator | Application framework provided, ten base modules, local bus, three execution modes, debugging in their usual environment, autonomous repository. |
| IT and security management | Isolation by account, firewall closed by default, secrets held by the platform, write-only record, enterprise sign-in, shared or dedicated hosting. |
The model: shape in Git, live settings in the database, secrets in the vault
A fleet follows a version published in the account's Git repository: that is the shape and the default values. Live settings — a trial version on one device, network, firewall, heartbeat rate, class — form the override, held device by device. Secrets (storage access, cloud keys) come from the vault and are issued for a limited time at each heartbeat.
The device pulls its configuration and converges on its own, including after an outage. Anything volatile — on, off, enabled — is a declared state that the system reconciles, never a one-off command.
What the product does
Ten functional domains, detailed in The ten domains:
- Building the device image: one form, one image ready to write, with an exact preview of what will be embedded.
- Enrolling and identifying: immutable identity born in the image, history of every write, replacement without loss.
- Deploying: point to a version, see the comparison before approving, full history.
- Configuring in cascade: zone, account, fleet, device — an empty field inherits, every override is visible and reversible.
- Monitoring in real time: state, metrics, modules, observed firewall, timeline.
- Intervening: embedded web console, time-limited technician access, configuration over a USB cable, scripts by phase.
- Updating the agent and the operating system without breaking the field, with automatic rollback.
- Developing on a provided framework: ten base modules, local bus, three execution modes, six languages.
- Governing: accounts, teams, roles, credentials, zones, write-only record.
- Three device types: embedded box, development workstation, Android payment terminal.
The Console
Fleet is one application of the Arkipelis Console, alongside Octopoda: dashboard, fleets (detail, modules, devices, images, resources, scripts, settings), devices (detail, scripts, override, monitoring), images, scripts, hardware, repositories, credentials, tasks, profile. Screen by screen: The Fleet application.
What it shares with Octopoda
Device identity, the account's Git repository, zones, teams and roles, sign-in, audit record, tasks: this is the platform foundation. A Fleet device sends its telemetry and logs into the account's Data portal, and sells through Distrib. The business identity of the point of sale stays distinct from the device that carries it, and the link between them is dated.