The substrate underneath an operator's fleet should never be a vendor lock-in. UMF is open. Our SDKs are open. Reference implementations are open. What's commercial is hardened distributions, signed registries, and the BOREAL control plane — the substrate stays in your hands.
The UMF spec is a public document. Implement a parser or builder against it without permission, licensing, or sign-up.
Eight languages — Go, Rust, Python, TypeScript, Java, C#, Ruby, Elixir — open and tracking the spec version directly.
Reference implementations under MIT/Apache. Fork them, run them air-gapped, build downstream tooling without negotiating a license.
UMF runs on any hypervisor, any cloud, any registry. The format isn't tied to a single runtime, builder, or distribution.
Working code for every directive in the spec. Read, modify, replace — the canonical implementation is never a black box.
Sovereign deployments work end-to-end without outbound connectivity. Registries and caches accelerate but are never required.