Preview Release 3 is out and the first general release is expected in 2027. What the open edge standard changes in practice — and what you can do today.
Margo is close to its first general release. For machine and plant builders it comes down to this: choosing the edge hardware and choosing the management software become two separate decisions. Today they are usually one — which is why an application gets repackaged and retested for every device vendor.
Margo is an initiative under the Linux Foundation, founded in 2024 by ABB, Siemens, Microsoft, Schneider Electric, Rockwell Automation and Capgemini, among others. The name comes from the Latin word for “edge”.
Margo has three parts, and all three matter:
The third is the one that ends up making the difference. A standard without a test tool is a statement of intent.
| Point in time | Status |
|---|---|
| 2024 | Founded under the Linux Foundation |
| 13 January 2026 | Preview Release 1 — first public access to the specification, plus a sandbox |
| Plugfest 1 | Hands-on testing of the specification, hosted by SUSE at its Nürnberg office |
| 16 June 2026 | Preview Release 2 with initial device management; since then a quarterly release cadence with specification tagging |
| announced 23 June 2026 | Plugfest 2 based on PR2, on the way to the first general release |
| 15 September 2026 | Preview Release 3 |
| planned for 15 December 2026 | Preview Release 4 — which would complete the scope of the first general release |
| announced for 2026, likely 2027 | first general availability release |
Worth knowing for planning: the specification is still labelled pre-draft. Features that do not make a release move to the next one. If you put Margo on a roadmap today, put it there as a direction, not as a delivery date.
The pain point is everyday and rarely written down: different edge hardware relies on different deployment technologies — Docker, Podman, Snap. The same application has to be packaged differently, installed differently and managed differently for each target device. That costs engineering time with every new device in the portfolio, and it ties the choice of hardware to the software you already have.
Once the Margo standard takes hold, three things change:
For the installed base this is more than convenience. If you have to roll out security updates across a mixed device fleet — and since 11 September 2026, with the CRA reporting duties, that is no longer optional — you pay for every vendor quirk twice: once when building, once on every rollout.
Without waiting for the GA release:
logiccloud has built on Docker and Kubernetes from the start — precisely the container technologies Margo itself builds on. The Fleet Manager in logiccloud ORCHESTRATE follows the open Margo approach to managing edge workloads. Our take at the time is still in our post “Manage edge software uniformly”.
And the honest footnote to that: formal proof of conformity only becomes possible once the compliance testing toolkit ships with the general release. Until then the same applies to everyone involved — you align with a specification that is still moving. We will tell you as soon as we have passed the test.
If you run edge devices from more than one vendor today, the stocktake is worth doing now rather than after the release: how many package formats do your applications exist in, and what does that cost you per rollout?
Show us your device fleet — we will look at what can already be unified today.
Sources, checked on 12 September 2026; timeline updated on 2 November 2026
Choose hardware freely, deploy applications more easily, run machines reliably: what matters when moving to cloud-native automation, and how IDE, CONTROL, ORCHESTRATE and DELEGATE work together.
Article 14 of the Cyber Resilience Act has applied since 11 September 2026 — including to machines already in the field. Which deadlines run, and what you need to answer them.
BSI registration was due on 6 March, the extension on 31 July. Both are gone — the obligation is not. What to do now, in the order that actually works.
