Sovereignty here is the architecture — not a setting.
Aotearoa West Coast · © My Digital SovereigntyThe Village
Sovereign community infrastructure. Members-only communities on infrastructure they own — your record, your rules, your AI.
The sovereign alternative to the whole stack
Almost every business platform works the same way: an organisation's records sit on Microsoft, Google or Amazon's US-owned cloud, and the AI wired in to read them — Copilot, Gemini, Meta AI — belongs to those same vendors, reachable under the US CLOUD Act. The Village changes the foundation: the community owns its record, the record lives on sovereign ground, and the AI answers to the community's own constitution.
Three capabilities the big stacks structurally can't offer
Not by choice — because of the cloud they run on and the model they wire in. Microsoft 365 + Copilot, Google Workspace + Gemini, Meta's platforms, and the business apps built on them cannot match these.
- The sovereign record
- Federation on consented, governed, audited terms
- Situated Language Models — the real answer to AI capture
Your records are their business. The Village hands them back.
Aotearoa ngahere · © My Digital SovereigntyThe sovereign record
Every community owns its data outright — member-held, sealed off from every other community, hosted only on New Zealand / EU sovereign infrastructure, with cryptographic deletion: "deleted" means cryptographically erased, not merely hidden.
Federation
Villages interconnect on consented, governed, audited terms — each side shares only what it agrees to — so communities collaborate without merging, surrendering their data, or being absorbed. Federation runs today — for example, a business and its accountant can each keep their own Village and share only the records they both agree on: connected, neither absorbed.
Situated Language Models
The world is right to move to small models — it proves you no longer need a hyperscaler's giant cloud model. But small is only size. The Village's AI is situated: an open-source model (Qwen 14B today), fine-tuned on the platform's governance and run under each community's written constitution — answering within the rules, logging every step, leaving the decision to a human. Open weights, auditable, yours to host on a single GPU on NZ ground.
Why hasn't a hyperscaler simply added sovereignty?
Because it can't, without abandoning its own business — its profit is your data's residency and your lock-in, the very things the Village hands back to the community. Sovereignty isn't a feature they are missing; it is the model they would have to dismantle.
Nor is it a frozen stack
Owning the platform and running open models lets us continuously adopt the best the field offers — models, tools, infrastructure — at the balance of capability, cost and sovereignty that serves communities best, rather than moving at one vendor's pace and price.
By architecture — not by promise.
Rural Aotearoa · © My Digital SovereigntyWhat a Village delivers
- Governance built in — roles, a written constitution, decision records
- Communications and a members-only space
- The sovereign record
- Federation on agreed terms
- The Situated Language Model — learning from the community's own content only with consent, never leaving sovereign ground
No advertising, no surveillance, no US-owned cloud anywhere — by architecture, not by promise.
Owned, not rented. That is the whole difference.
© My Digital SovereigntySovereignty here is not a setting or a promise — it is the architecture. A community owns its record, connects with others on its own terms, and runs an AI that answers to its own constitution. That is what no reseller of someone else's cloud can offer.
My Digital Sovereignty Limited (NZ) · mysovereignty.digital