Sovereignty

“Sovereign” isn’t a slogan here; it’s an architecture.

Two planes

• Control plane (the vendor) brokers identity and policy: who you are, what’s allowed.
• Data plane is your actual traffic between your devices.

These are separated structurally. The control plane hands out identity and policy decisions; it is not a relay. Your bytes go directly, device to device, encrypted end to end.

Why the vendor can’t decrypt you

The peer-to-peer links are encrypted between your devices with keys the vendor doesn’t hold. Even the control plane operator can’t read your traffic — not “promises not to”, can’t. That’s the difference between a policy and a property.

Why it’s not just a setting

Because the data plane doesn’t route through vendor infrastructure at all, there’s no switch an operator could flip to start reading it. The guarantee is enforced by where the bytes physically go — which is why you can Prove It yourself instead of trusting a claim.

The honest edge

When two devices genuinely can’t reach each other directly, a fallback relay can carry the (still end-to-end encrypted) traffic. Ankayma shows you when that happens — the path chain never hides it. Today, direct peer-to-peer is the norm.