Mickai versus private cloud AI: which is actually sovereign?

The difference is who holds the keys and whether the system keeps working when the network cable is pulled. Private cloud AI is a real improvement on public multi-tenant services and is enough for many workloads, but it still runs on infrastructure a provider owns, updates, and can reach. Mickai is a Sovereign Intelligence Operating System that runs on hardware you control, keeps operating fully offline, and leaves the encryption keys and the model weights in your possession. Sovereign means the answer stays yes when the connection is gone.

• Private cloud reduces multi-tenancy risk, but the provider still holds root, keys, and the update pipeline.
• Mickai runs on your own hardware, so control and custody stay inside your walls.
• The honest test of sovereignty is the network cable: pull it, and the system either keeps answering or it does not.
• Data ownership means holding the keys and the weights, not renting isolation on someone else's estate.
• Private cloud is often the right choice; sovereignty is a different property, not a higher tier.

What does private cloud AI actually give you?

Private cloud AI carves out a dedicated slice of infrastructure for a single customer. Instead of sharing a model service with thousands of other tenants, an organisation gets isolated compute, a private network boundary, and contractual promises about where data sits and who may touch it. This is a genuine improvement: it removes the noisy-neighbour problem, narrows the blast radius of a breach, and satisfies a large share of compliance requirements. For many workloads it is the proportionate answer.

What it does not change is the shape of the arrangement. The infrastructure is still owned, patched, and operated by a provider, and the control plane, the root credentials, and the key service usually live on their side of the boundary. A private cloud is a well-fenced plot on someone else's estate, and the landlord still holds a master key.

What makes an AI system actually sovereign?

Sovereignty is not a stronger grade of privacy. It is a question of custody and independence. A system is sovereign when the data, the encryption keys, and the model weights sit in your possession, and when it keeps functioning with no outside connection at all. If a vendor can reach in to read, change, suspend, or switch off the service, the sovereignty is partial at best.

The clearest test is physical. Pull the network cable and watch what happens. A sovereign system carries on answering, because everything it needs already lives on hardware under your control. A dependent system stops, degrades, or waits for permission from somewhere else. That single test cuts through most of the marketing.

Where does Mickai draw the line?

Mickai is a Sovereign Intelligence Operating System, not a hosted service dressed in private-cloud language. It runs on hardware the customer holds, inside their own walls, and its studios do their work locally. The model weights stay on the machine. The keys stay with the operator. There is no default path back to a provider, because the design assumes the connection may never exist.

That posture is backed by engineering rather than promises. Custody of keys and weights, tamper-evidence over sensitive actions, and hardware-bound entitlement are built into how the system runs. Mickai LTD holds 104 filed UK patent applications, approximately 2,340 claims, covering much of this ground. Micky Irons, founder of Mickai, has kept one line fixed throughout: the answer to who is in control should never depend on a working internet connection.

Does running offline really change anything?

It changes the three things that matter most under pressure: availability, jurisdiction, and evidence. An offline-capable system keeps working through an outage, a supplier dispute, or a region going dark. Its data does not cross a border it was never meant to cross, because it never leaves the building. And when every sensitive action is recorded where you can inspect it, you can prove what happened rather than trust an external log.

For regulated sectors, contested environments, and anyone handling information that must not leak, offline capability is not a luxury feature. It is the difference between owning an outcome and hoping a third party behaves.

Is private cloud ever the right call?

Often, yes. If a workload can tolerate provider custody, needs elastic scale more than independence, and sits comfortably within a vendor's jurisdiction and uptime, private cloud is a reasonable choice. Sovereignty carries its own responsibilities, and not every task needs it.

The mistake is treating the two as rungs on one ladder, where sovereign is simply the premium step above private. They are different properties. Private cloud optimises for isolation and convenience on rented ground; a SIOS optimises for custody and continuity on ground you hold. Choosing well means naming which property the workload requires, then being honest about who holds the keys.

Frequently asked questions

Is private cloud AI the same as sovereign AI?

No. Private cloud AI gives an organisation isolated infrastructure, which reduces multi-tenancy risk and satisfies many requirements. Sovereign AI goes further by keeping custody of data, keys, and model weights with the operator and running without any external dependency. Private cloud improves privacy; sovereignty settles control.

If my data is encrypted in a private cloud, why is that not enough?

Encryption protects data at rest and in transit, but the real question is who holds the keys and the control plane. In most private-cloud arrangements the provider manages the key service and retains root access to the platform. Encryption without custody of the keys is a strong lock whose spare sits with someone else.

How can I tell whether a system is genuinely sovereign?

Apply the cable test. Disconnect it from every outside network and see whether it keeps working. A sovereign system continues because the weights, keys, and compute are already in your hands. If it stalls or waits for a remote service, the sovereignty was conditional.

Does Mickai need an internet connection to work?

No. Mickai is designed to run fully offline on hardware the customer controls, with model weights and keys held locally. A connection can be used when it is wanted, but the system does not depend on one to keep operating.

Can we start with private cloud and move to a SIOS later?

Yes. Many organisations run suitable workloads on private cloud while moving their most sensitive intelligence to a sovereign posture, and the two can coexist. The right split depends on which workloads truly need custody and continuity rather than isolation alone. Teams weighing that move are welcome to apply to the selective closed beta at mickai.co.uk/beta, where places are limited and not every application is accepted.