Data sovereignty

Your files. Your building. Your keys.

Every file, every record, everything it learns — on a machine you own, and no one else holds a copy.

Everything, meaning everything.

"On your premises" usually means just the sensitive parts. Here it means all of it.

What Where it lives Copies held elsewhere
Your files — documents, mail archives, records, the knowledge base Stored twice inside the machine, encrypted, keys held by you None
The machine's reading of your files — how it finds things across every document Inside the machine only None
The code-word lists that could link a Hybrid Reasoning request back to real names On the machine only None — by design, ever
What the machine has learned from your team's corrections Locked to the machine itself None
The sign-ins to your CRM, accounting system, mail and portals Locked to the machine itself None — we never hold one
The record of every job, every approval, and everything that has ever left On the machine — you can export it Only if you export them
The backup An encrypted drive in your own office None

Indexed where it sits.

During install week the machine reads your whole archive on site — nothing is shipped away. Every search after that stays inside your walls, and the record proves it.

The appliance working with its network cable coiled beside it, unplugged
Runs with the WAN unplugged.

We can see the box is healthy. We cannot read a word on it.

Only a health signal goes out, and there is no way in. The feed, in full:

TELEMETRY · OUTBOUND ONLY

last 24h · 96 heartbeats · 0 inbound connections

  • sent health: ok · queue depth · latency p95
  • sent error classes, counts only
  • never documents, filenames, queries
  • never names, figures, embeddings
remote shell
none
support tunnel
none
swap recovery
restores from your on-site backup

the health signal, in full

An illustrative example — the structure is exactly what the real feed looks like.

It learns your firm. It stays your firm's.

Your team's corrections teach the machine overnight, without anything leaving the building. The improvement is an asset you own — never a contribution to someone else's AI.

Your machine gets better at being yours every month — and forgets it entirely if you leave.

When you leave.

  • Every connection to your systems is cut, with proof.
  • Everything it learned, everything it read, and every code-word list is deleted — shown to you.
  • The machine is yours either way — what ends is the service, and every trace of the engagement.

Everyone else sells the airlock. We sell the building — with the airlock installed, and the record of every departure locked into the machine itself.

Ask us where any byte lives. We'll point at it.

Bring your IT lead — the diligence pack shows where everything sits.