SovereignAI

Sovereign AI · fair source · self-hosted

Sovereign AI. You own every layer.

One AI that runs on your machine, thinks with models you choose, remembers with receipts, and proves you can leave. No cloud required. No account. Nothing to trust but code you can read.

⬡ Zero-dependency core · fair-source licensed, MIT after two years · your data never trains anyone's model.

Every other "private" AI

Your data lives on their servers, behind their login, under their terms. "Private" means they promise not to look. Leaving means starting over — your conversations, memory, and tuned behavior stay locked in the account you're trying to close.

⬡ SovereignAI

Runs on your hardware. One file, zero dependencies, readable code. The database sits in a folder you can copy; everything exports into one checksummed file whenever you want it. Ownership isn't a slogan here; it's an exit path we test.

Ten unlocks · one first week

The first week it's actually yours.

Told in the second person, because it will be you. The week is an illustration — the receipts are not: every mechanism named under a moment ships today, none of it is roadmap.

  1. 01Saturday9:12 am

    It boots. Nobody asks for your email.

    One downloaded file is the whole thing — runtime, app, interface. It asks what to call itself and gets to work. There's no account screen, because there's no one between you and it.

    ⬡ single binary · zero runtime dependencies

  2. 02Saturday9:31 am

    You move four years of your old AI life in.

    Your ChatGPT and Claude exports drop straight in. It reads them on your machine and distills what matters into memory — by the second coffee it greets you with what it learned, citing the conversation that taught it each fact.

    sovereign import-chat --distill

  3. 03Sunday4:05 pm

    Your inbox confesses.

    You feed it a mail export. Out come the subscriptions, renewals, and receipts hiding in there — including the ones you forgot you're paying for. Parsed locally, nothing uploaded, and every finding links the email that proves it.

    sovereign import-email · subscription audit · renewals radar

  4. 04Monday10:40 am

    A forty-page contract answers in seconds.

    The PDF goes in; you ask what you actually agreed to. Every answer arrives with the source passage attached, so you're checking a claim, not trusting a vibe.

    ⬡ local knowledge base · sources attached to every answer

  5. 05Tuesday2:15 pm

    You rent a frontier brain. It doesn't get to keep you.

    A hard problem earns a big rented model for the afternoon — while the only thing allowed to write your memory is a small local model you own. The receipts name which model wrote what.

    ⬡ the “cognition stays home” switch · the cognition role

  6. 06Wednesday30,000 ft

    Airplane mode changes nothing.

    Chat, memory, documents, search — all of it runs with the Wi-Fi off, because all of it lives with you. The passenger next to you is arguing with a spinner.

    ⬡ local open weights · offline BM25 retrieval

  7. 07Thursday11:20 am

    It shows up inside your editor.

    The same memory and knowledge answer in VS Code, JetBrains, and your browser — any assistant that speaks MCP reads the one store only you hold, instead of keeping its own copy of you.

    sovereign mcp · VS Code, JetBrains & browser extensions

  8. 08Thursday11:58 pm

    You strike a memory. It's actually gone.

    Not hidden, not flagged deleted in someone's database — overwritten on your own disk, bytes zeroed. Some things shouldn't be remembered, even by you.

    ⬡ SQLite secure_delete · playable below

  9. 09Friday6:30 pm

    A better model drops. You swap brains, keep the mind.

    New open weights land in the news; minutes later they're serving your chat. Your memory, personas, and documents don't move an inch — and every reply names the exact weights that produced it.

    ⬡ per-persona models · weight-digest receipts on every reply

  10. 10Saturdayone week in

    You run the exit drill you'll never need.

    One command folds everything into a checksummed file; another proves it intact without even importing it. You're not staying because leaving is hard. You're staying because it isn't.

    sovereign export --encrypt · sovereign verify

That's week one. The years after are the point — memory that compounds somewhere no vendor can reach it. Don't take the story's word either — press the buttons ↓

Operate it, right here

Don't take our word. Press the buttons.

Three of the product's core gestures, replayed on this page exactly as they behave after install. No servers were contacted in the making of these moments.

⬡ Strike a memory

Prefers Friday demos with the whole teamadded by you · Jul 9
Ships on Windows, tests against WSLauto-extracted · written by ollama/llama3.1
Drinks too much espressorecorded before provenance tracking

Watch the bytes zero out. In the product, secure_delete does this to the real ones. Deletion is deletion.

⬡ The first five minutes

chatgpt-export.zip ready — parsed on your machine, nothing leaves it.

Import → distill → a greeting grounded only in what was actually learned. Your AI knows you before lunch.

⬡ The exit ritual

The whole workspace, checksummed, yours.

Export, verify, leave — the drill every claim on this page answers to.

What you get

Five layers. All yours.

Owning an AI means owning the stack it stands on. Each layer below is a concrete guarantee, audited claim by claim in the sovereignty ledger that ships with the repo — where an unknown is marked unknown, never rounded up.

The complete map — twelve things that are yours here, each one shipped, none of them a promise:

01 hardware 02 runtime 03 data 04 identity 05 models 06 fine-tuning 07 memory 08 cognition 09 knowledge 10 history 11 access 12 exit

Everything inside the wall is yours. Touch a district — or note the open wall at 12, where the boat is always waiting.

  1. your hardware — laptop, homelab, your VPS, your call
  2. your runtime — zero-dependency code you can actually audit
  3. your data — one folder; deleted means zeroed
  4. your AI's identity — its name and personas are your records
  5. your models — local weights, swappable per persona
  6. your fine-tuning — your datasets, your consent, your trainer
  7. your memory — every fact with origin, source, and author
  8. your cognition policy — choose which models may write memory
  9. your knowledge — parsed on-machine, previewable retrieval
  10. your history — chats born here or imported, inbox included
  11. your access — every channel reads a store only you hold
  12. your exit — verified export, portfolio, provable deletion

Counterintuitively, the ability to leave is the strongest reason to trust us.

— the whole product philosophy, in one line
  • One-file export — personas, chats, memory with its receipts, documents, life records, recipes, and training lineage. Checksummed; optionally encrypted with a passphrase only you hold.
  • Verify without importing sovereign verify backup.json proves an archive is intact, any time, on any machine.
  • A documented format — the export schema is public, so your archive stays readable even if this project vanishes.
  • Provider independence — local models, your own API keys, or any compatible endpoint. Switch anytime; nothing re-plumbs.
  • The portfolio — your memories, personas, and knowledge inventory as one markdown file, pasteable into any AI you'll ever use.

Private early access · fair-source licensed

Three ways in. All of them yours.

We're in a gated early-access phase: request access with your work email and we send the build, the docs, and your onboarding path. Once it's yours, first launch opens a guided setup — drop in a ChatGPT or Claude export and your AI knows you within minutes. The gate is on the door, not in the product: nothing you receive ever phones home to ask permission.

Single binary No Node, no installer

One file for Windows, macOS, or Linux, delivered with your access grant — runtime, app, and UI inside. Check it against the release's SHA256SUMS.txt, then run it.

One-line install Script it

A one-line installer — irm … | iex on Windows, curl … | sh on macOS and Linux — with the exact command in your welcome note. Docker Compose if you prefer containers.

Any box you own VPS · homelab · on-prem

sovereign byoc deploy --host you@your-box puts a hardened instance on any Linux machine with SSH and Docker — health-checked upgrades, export-to-owner, verifiable delete.

Prefer reading before running? Say so in your request — source access comes with the grant, and zero runtime dependencies means the audit is actually finishable.

Private early access · every request read by a person

Request access.

Tell us who you are and what you'd own with it. We review every request personally and reply with the build, the docs, and your onboarding path — self-hosted on your machine, or the managed edition if you'd rather we run the ops while you keep the boundary, the export, and the exit.

Work email required — it's how we verify a request without asking for anything else. No spam, no reselling your address. You'll be able to leave the product as easily as this list — which is the whole point.