Anyone running distributed services faces the same challenges in six areas at once: identity, network, policy, secrets, access and provisioning. Every provider tackles this differently. Every change means new code, new lock-in and new dependencies.
Plexsphere sits exactly in the middle. A sovereign control plane that acts as middleware between your own ecosystem and any underlying infrastructure. Above it, the services you build. Below it, AWS, OpenStack, bare metal, or an edge node behind NAT. In between, a single, coherent interface.
Your services communicate solely with Plexsphere. Plexsphere communicates with the underlying infrastructure via portable interfaces: KRM via Crossplane for provisioning, OIDC for identity, and WireGuard for the data plane. The choice of underlying provider becomes a configuration decision, not an architectural one.
This talk introduces Plexsphere for the first time. It focuses on the three-layer model, the six core capabilities, and the core promise: one identity, one network, one policy, one provisioning across every provider. Through the encrypted WireGuard mesh, the ReBAC model and the signed event bus, you will see how digital sovereignty emerges not as a marketing term but as an inherent property of the codebase.
