Skip to content

What is logiccloud orchestrate?

logiccloud orchestrate 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.

logiccloud orchestrate was formerly called Fleet Manager. Some technical names, such as the namespace, the realm and the image paths, still use fleet-manager.

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. logiccloud orchestrate 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.
  • 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.

logiccloud orchestrate is organized into modules, each covering one part of the workflow:

  • Devices — see every edge device that registered, its status, health, workloads and logs, and manage it.
  • Device Groups — put devices into named groups and deploy to a whole group in one step.
  • 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.
  • Alerts — get an e-mail or webhook when a device goes offline, a metric crosses a threshold or a rollout halts.
  • Repositories — connect the Git and OCI registries and the FLECS Store that supply the application catalog.
  • Certificates — manage the certificate authority and see the certificates of your devices.
  • 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.

A typical end-to-end flow looks like this:

  1. A device onboards — it registers with a request signed by its own certificate and receives its client ID.
  2. The device reports its capabilities (CPU, memory, storage, interfaces), so the platform knows what it can run.
  3. You connect a registry, which syncs to populate the application catalog.
  4. You create a deployment, targeting devices directly or by group, and choose a rollout strategy.
  5. 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).
  6. 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.

logiccloud orchestrate 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.

Everything the web interface does is available over the REST API. The API Reference section documents every endpoint, and the full OpenAPI specification is downloadable at openapi.json — see API Spec for what you can do with it.

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.