What is Fleet Manager?
Fleet Manager (the Workload Fleet Manager) is an enterprise platform for managing fleets of edge devices and orchestrating workload deployments to them in industrial-automation environments. It gives operations teams a single place to onboard devices, organize them, publish applications, roll those applications out safely, and monitor everything in real time — across many isolated organizations.
It is built on the open Margo specification for device onboarding, capability reporting, and workload orchestration, so any Margo-compliant device can participate without bespoke integration.
The problem it solves
Section titled “The problem it solves”Industrial fleets are large, distributed, and long-lived. Devices sit in factories and remote sites; the software they run must be deployed, updated, and rolled back carefully, because a bad rollout can take production offline. Fleet Manager addresses this by providing:
- a secure, standards-based way for devices to join and be trusted,
- a catalog of versioned, validated applications sourced from your own registries,
- controlled rollouts (canary, rolling, immediate) with automatic rollback,
- real-time visibility into device health and deployment progress, and
- multi-tenant isolation with role-based access, so many teams or customers can share one platform safely.
Who it’s for
Section titled “Who it’s for”- Operators and viewers — the people who run the fleet day to day: onboard devices, deploy applications, and watch rollouts.
- Tenant administrators — who manage users, registries, certificates, and tenant settings.
- Superadmins — who administer organizations across the whole platform.
- OT engineers — who connect edge devices and need to understand the device-side Margo workflows.
See Roles & Access for exactly what each role can do.
What you can do with it
Section titled “What you can do with it”Fleet Manager is organized into modules, each covering one part of the workflow:
- Devices — onboard edge devices with a one-time signed enrollment, track their status and reported capabilities, and manage their lifecycle.
- Groups — organize devices by labels and use those groups as deployment targets, without maintaining static lists.
- Applications — browse a catalog of versioned workloads that is populated automatically by syncing your registries.
- Deployments — roll applications out to devices or groups using immediate, canary, or rolling strategies, with auto-rollback, and watch progress live.
- Repositories — connect the Git and OCI registries that supply the application catalog.
- Certificates — run the PKI: a certificate authority and the device certificates issued from it that secure communication.
- Users — invite people to a tenant and assign their roles.
- Tenants — switch between organizations and, as a superadmin, administer them.
- Audit Logs — review and export an immutable record of every change.
- Dashboard — see fleet health, deployment status, and a live activity feed at a glance.
How the pieces fit together
Section titled “How the pieces fit together”A typical end-to-end flow looks like this:
- A device onboards — it registers with a signed request and is issued an identity and certificate.
- The device reports its capabilities (CPU, memory, storage, interfaces), so the platform knows what it can run.
- You connect a registry, which syncs to populate the application catalog.
- You create a deployment, targeting devices directly or by group, and choose a rollout strategy.
- The platform distributes the desired state to each device, and the
devices report status back through the Margo lifecycle
(
pending → installing → installed, with rollback if needed). - You watch it all on the Dashboard and in the deployment detail view, with a full audit trail behind every action.
Everything is scoped to a tenant (organization). Your role within that tenant determines which of the modules above you can see and use, and the data of one tenant is isolated from another.
Built on Margo
Section titled “Built on Margo”Fleet Manager implements the Margo Workload Management API to the letter, so the device side is standards-based and interoperable. The Margo section explains onboarding, capability reporting, desired state, and the deployment-status lifecycle for OT engineers and integrators.
Where to go next
Section titled “Where to go next”| If you are a… | Start with |
|---|---|
| New user | Getting Started |
| Operator / Viewer | Devices → Applications → Deployments |
| Tenant Admin | Roles & Access → Users → Repositories → Certificates → Settings |
| Superadmin | Tenants → Audit Logs |
| OT Engineer | Margo Overview → Onboarding → Desired State |
New to the platform? Begin with Getting Started.