Software updates in the field
If you look after hundreds of machines at many customers, every update needs a process — not a service technician with a USB stick.
With logiccloud ORCHESTRATE you see which software runs on which machine, roll out new versions in stages and document every change. Across vendors — including software that was not built with logiccloud.
3 machines not on the released version
Auto-rollback once the failure rate passes the threshold
Today and tomorrow
Know what runs out there. Without travelling.
Roll out in stages
Which strategy fits depends on how critical the machines are and how sure you are of the new version.
All targets at once — for non-critical changes.
A few systems first, then the rest once all is well.
Batch by batch; optionally with an admin approving each batch.
The markers show the principle, not customer figures.
What it takes
Devices onboard with a one-time token and receive a certificate from the tenant’s own CA.
Labels by customer, site, machine type and version — new machines sort themselves in.
Immediate, canary or rolling; applications as Helm charts or Compose files from Git and OCI registries.
Audit log with CSV export: who rolled out or approved what, and when.
Telemetry via OpenTelemetry, device logs, alerts by email or webhook.
Tenants strictly separated, each with its own branding.
CRA conformity of the overall product remains the manufacturer’s responsibility.
Cyber Resilience Act
The Cyber Resilience Act requires manufacturers to handle vulnerabilities and provide security updates for the whole support period. Reporting duties have applied since 11 Sep 2026, the full requirements from 11 Dec 2027.
ORCHESTRATE provides the technical capabilities for this: inventory, controlled updates, evidence. CRA conformity of the overall product remains the manufacturer’s responsibility.
No. ORCHESTRATE distributes any container application as a Helm chart or Compose file — including software that was not built with logiccloud.
On edge devices from many vendors with Linux and a container runtime. The hardware page lists the devices.
In canary and rolling rollouts ORCHESTRATE stops automatically once the failure rate passes the threshold you set. Rollouts can also be paused, resumed or cancelled at any time.
ORCHESTRATE implements the Margo Workload Management API, an open specification under the Linux Foundation. The specification is not final yet; we keep ORCHESTRATE current with every release.