This site runs without analytics or fingerprinting. One choice determines whether web fonts are pulled from Google Fonts — an external request that carries your IP to a third party.
ConsentExternal web-font request only. Declining swaps in system typefaces; everything else is identical.
RetentionOne strictly-necessary cookie records this choice for 12 months — required to remember it. No analytics, no fingerprinting, nothing else.
Your rightsAccess · rectification · erasure · portability. We hold no data, so there is nothing to retrieve.
NO TRACKING · NO ANALYTICS · ONE CONSENT-RECORD COOKIE (12 MONTHS) · NOTHING ELSE
Operating control stays in the customer's jurisdiction because a local operator holds keys, support and update authority. That's not just a channel strategy — it's an implementation of the sovereignty architecture. We're recruiting the first operators and MSP partners.
§ 01 — WHY PARTNERTWO ROUTES, ONE PROVENANCE CHAIN
DIRECT / VELOCITY
“Move commodity boxes fast.”
Entry and departmental units sell near-transactionally to prosumer and SMB buyers — thin hardware margin plus the first test of the SovereigntyOS subscription. A homelab-grade reputation reaches the enterprise's technical evaluator.
CHANNEL / ENTERPRISE
“Own the durable annuity.”
Regulated mid-market and enterprise buy on a sovereignty mandate — recurring support and services, custom where the margin concentrates. Anchor co-sell into VAR/MSP fleet rollout.
§ 02 — WHAT AN OPERATOR HOLDSLOCAL OPERATING AUTHORITY
Keys, support, continuity.
For the sovereignty claim to be true, each deployment provides locally held operational and deployment authority, customer- or locally-controlled keys, no compulsory global control plane, signed offline update and recovery, and tested continuity if the parent or supplier becomes unavailable.