Home/The Three
Yours to run · Yours to keep · Yours alone

Three things you can't
have taken back.

"Sovereign" isn't a slogan here — it's a technical property with a precise meaning. Sovereign AI, Sovereign Stack, and Sovereign Data. Here's what each one actually is, and the specific mechanism that makes it impossible to revoke.

I. Sovereign AI · Yours to run
I.

Agents and models that answer to you — not to a provider's roadmap.

Rented AI lives on someone else's account, behind someone else's API, governed by someone else's policy. It can be suspended, deprecated mid-project, or repriced out from under your business — and you have no recourse, because you were never the customer that mattered.

Sovereign AI runs open-weight models locally, served through a standard runtime on hardware you control. The harness — the orchestration and control layer — abstracts the model away, so you are never bound to a single model. When a better or replacement open-weight model ships, the harness adopts it without you re-architecting anything.

Nobody can suspend your account, because there is no account to suspend. Nobody can deprecate your model, because the next one slots in underneath you.

What this looks like technically

  • Open-weight models, served locally — abstracted behind the harness so the choice of model is yours and is swappable by task.
  • No external dependency on the critical path — the inference that runs your business runs on your side of the wire.
  • Model migration as a service — when the frontier moves, the maintenance relationship moves you with it. That's a feature you're paying for, not a tax.
What you escape

Suspension over a policy you never read. A model retired in the middle of your project. A price that triples because you're one account in hundreds of millions and they can. None of these have a lever to pull when the AI is yours to run.

II. Sovereign Stack · Yours to keep
II.

Built on genuinely open foundations. No license to revoke.

The stack is built on permissively-licensed software — MIT and Apache 2.0 at the core. That is not a marketing detail; it is the legal reason the stack is yours to keep. Permissive licenses hand over full freedom: run it, modify it, keep it, with no seat to cancel and no rug to pull.

The open core is genuine — a usable harness that runs a real single-node stack, the hardened-base scripts, full documentation, and a starter template set. The high-value layers that decay — current harness releases, security hardening, model migration, the premium template library — are the paid, continuously-maintained part.

A member or the co-op may fork the open core. Doing so transfers the entire maintenance burden onto them — the exact burden they joined to avoid. The fork is legal and self-defeating by design.

The open-core split

Open / low-cost — yours outright
Paid — because it decays and must be maintained
A usable core harness running a real single-node stack
Current maintained harness releases & the control plane
The basic hardened-base deployment scripts
Ongoing security hardening as threats move
Full documentation
Model migration as the frontier moves
A starter template set
The premium template & skill library, kept current

The full picture of what's in the box — models, runtimes, deployment tooling, and the open licenses it's all built on — lives on The Stack page.

III. Sovereign Data · Yours alone
III.

It never leaves ground you control. It never becomes the product.

On rented inference, your data doesn't sit still. Every record your agents touch can become training material — sharpening the very product your competitor rents next quarter. You pay a subscription, and the price includes handing over your edge.

Sovereign Data runs on your own private VPS or hardware. The integration layer — MCP and connectors — reaches your files, databases, internal services, and tools without that data ever crossing to a third party. It does real work against real systems, on your side of the wire.

It never leaves ground you control, never trains someone else's model, and never becomes the product.

Why this is structural, not a promise

  • The compute is fungible and yours — your own hardware, commodity bare-metal arranged through the co-op, or a mix. No provider holds your data hostage.
  • Confidentiality and residency are settled by location, not policy — if the data physically stays on your hardware, no terms-of-service change can reach it.
  • The "get off rented inference" audit quantifies your current exposure — what breaks if the account is suspended, what a price increase costs, what confidentiality or residency risk you already carry.
Taken together

Three properties, one outcome: a capability nobody else can switch off.

I.

Sovereign AI

Agents and open-weight models that answer to you. They can't be suspended, deprecated, or repriced out from under your business.

Yours to run
II.

Sovereign Stack

Genuinely open foundations — MIT and Apache 2.0. Yours to run, modify, and keep. No license to revoke, no seat to cancel.

Yours to keep
III.

Sovereign Data

Running on hardware you control. It never leaves, never trains someone else's model, never becomes the product.

Yours alone
The whole choice, in one line each
Rented — today
Owned — the co-op
Your AISuspended, deprecated, repriced at will.
Your AIAnswers to you. Cannot be revoked.
Your StackA seat you lease until further notice.
Your StackOpen foundations, yours to keep.
Your DataTraining their next model.
Your DataNever leaves ground you control.

The operators who own all three compound. The ones still renting get marginalized.

Slowly, then all at once. The founding cohort is being assembled now — claim your place while it's still hands-on.

Request an invitation →

Own the intelligence. Own the
stack. Own the data.

Request an invitation to the founding cohort, and we'll show you concretely what all three look like running in your business.