A sovereign AI procurement checklist for buyers

Sovereign artificial intelligence procurement comes down to four plain tests: is the system owned rather than rented, does it keep running with the network cable pulled, can you prove where every byte went by reading the logs yourself, and do you hold the keys without asking a supplier for permission. If a vendor cannot demonstrate all four on your own hardware, the system is not sovereign, whatever the brochure claims. The right question is never how clever the model sounds, but who controls it on the day the contract sours.

• Pull the network cable and confirm the system keeps answering rather than going dark.
• Open the raw audit log yourself, in a format you can read without the vendor's own tools.
• Hold and rotate the encryption keys on your own schedule, with no support ticket required.
• Revoke the supplier entirely and confirm operations continue on hardware you control.
• Capture the network traffic and prove nothing leaves your walls without your say-so.
• Export every weight, record, and configuration, and walk away with a working copy.
• See the owner of the intellectual property named in writing before anyone signs.

Does it keep working when you pull the cable?

This is the fastest test of sovereignty, and the one most systems quietly fail. A system that pauses, degrades, or refuses to answer once it loses its connection to an outside cloud was never yours to begin with: it was a thin client wearing a local badge. Ask for a live demonstration where an engineer unplugs the network in front of you and the assistant keeps reasoning, keeps drafting, and keeps retrieving from its own store.

Mickai is built to pass this test by design. As a Sovereign Intelligence Operating System, or SIOS, it runs the model, the retrieval, and the interface on the buyer's own machines, so pulling the cable changes nothing about what it can do.

Who actually holds the keys?

Encryption is common. Custody of the keys is rare. Many suppliers encrypt data at rest and in transit, then keep the decryption keys in their own account, which means they can read what you cannot revoke and revoke what you cannot read. Sovereignty requires that the keys sit with the buyer, that they can be rotated on the buyer's schedule, and that no reissue depends on the supplier being reachable, solvent, or willing.

Put the question bluntly in the contract: if the supplier disappeared tomorrow, could the buyer still decrypt and operate? If the honest answer involves a phone call to support, the keys are in the wrong hands.

Can you read the audit log yourself?

A log you cannot open is not an audit trail, it is a promise. Buyers should be able to read the raw record of what the system did, in a plain format, on their own terms, without a portal that the vendor controls and can switch off. That record should show every action, every retrieval, and every outbound request, so that a compliance team can reconstruct events without trusting a summary written by the party being audited.

Tamper-evidence matters as much as access. The strongest arrangement writes signed checkpoints that the buyer can verify independently, so that a missing or altered entry is obvious rather than hidden. Mickai follows this pattern, keeping the log readable and verifiable by the organisation that owns it.

Can you revoke the vendor without asking them?

Lock-in is the opposite of sovereignty. Before signing, a buyer should establish exactly what happens if the relationship ends badly: whether the system keeps running, whether the data and models stay usable, and whether any of it depends on a licence server that the supplier can switch off from a distance. The test is simple to state and hard to fake: can the vendor be removed from the loop entirely while the organisation carries on working?

This is where ownership beats rental. When the weights, the records, and the runtime already sit inside the buyer's estate, revocation is a decision the buyer makes alone, not a negotiation.

Who owns the intellectual property, and can you prove it?

Sovereignty is also a legal fact, not only a technical one. Ask who owns the underlying invention, and ask to see it in writing. A clear estate signals that the system rests on defensible ground rather than on borrowed components that a third party could withdraw. Mickai's foundations sit on 104 filed UK patent applications, approximately 2,340 claims, owned by Mickai LTD, filed rather than granted, and the point for a buyer is simple: the ground the system stands on is named and owned, not rented.

Frequently asked questions

How do I test sovereignty in a single afternoon?

Run the cable test first, then ask to read one raw audit log entry, then ask who holds the keys. Those three checks, done live, separate genuine sovereignty from marketing faster than any questionnaire. A supplier confident in its architecture will welcome the unplugged demonstration rather than reschedule it.

Does sovereign AI mean I lose access to strong models?

No. Sovereignty is about where the model runs and who controls it, not about settling for something weak. Capable systems can operate entirely inside an organisation's walls, and the trade being asked for is control, not quality.

What if my team is not technical enough to check the audit log?

The format should be plain enough that a compliance officer, not only an engineer, can read it. If understanding the record requires the vendor's own tools or training, treat that as a warning sign rather than a convenience.

How is Mickai different from a cloud assistant with a private mode?

A private mode is still someone else's cloud with a setting turned on, and settings can change. Mickai is a Sovereign Intelligence Operating System that runs on the buyer's own hardware, so the guarantees are structural rather than a promise that can be revised in an update.

Where can I start if I want to try this?

Buyers can apply for the beta at mickai.co.uk/beta. Places are selective and not every applicant is accepted, so it helps to describe the environment and the controls that matter most to the organisation. Micky Irons, founder of Mickai, and the team review applications with sovereignty requirements in mind.