Why we run a closed beta for sovereign AI

Mickai runs a closed beta because sovereign AI is deployed into sensitive environments, and sensitive environments deserve care rather than a crowd. Rather than opening the doors to everyone, we work closely with a small number of design partners who run the Mickai SIOS on their own hardware, owned and offline and provable. This is disciplined sequencing, not scarcity theatre: we would rather earn a handful of deployments that hold up under scrutiny than chase a queue of sign-ups we cannot support to a standard we would stake our name on.

• A closed beta is a design-partner programme, not a public launch: we take on a small number of organisations, and not everyone who applies is accepted.
• The Mickai SIOS runs on your own hardware, owned and offline and provable, so nothing has to leave the building.
• Selectivity is about care and sequencing, not scarcity: we take on only what we can support properly.
• Design partners shape the roadmap, because what we learn from real deployments feeds directly into how the SIOS matures.
• You can apply now at mickai.co.uk/beta.

Why not an open beta?

An open beta optimises for volume. Sovereign AI does not reward volume, it rewards fit. When a system is designed to run inside a bank, a defence supplier, or a health provider, the interesting questions are about data boundaries, hardware, governance, and proof, and none of those are answered by a large anonymous sign-up list. A closed beta lets us sit alongside each partner and get those answers right.

There is also a duty of care. Sovereign AI is deployed into environments where a mistake is not a poor demo, it is a real consequence for real people. We would rather move deliberately with a few partners than move loosely with many, and a design-partner programme is how we hold ourselves to that.

What does a closed beta give a buyer?

Direct access, for one. Design partners talk to the people building the SIOS, not a ticket queue, and the things they raise are acted on quickly because the group is small enough to hear every voice. Priorities move because a partner asked, not because a form was filled in.

It also gives evidence. Running the Mickai SIOS on your own hardware, offline, means you can prove where your data sits and prove that nothing leaves. That is the difference between being told a system is sovereign and watching it behave that way on infrastructure you already control.

How do we choose design partners?

We look for organisations with a genuine sovereignty requirement and the will to work through a real deployment, not a spectator seat. The strongest partners bring a concrete problem, a clear owner on their side, and the appetite to test the SIOS against their own standards rather than ours.

Selectivity here is a feature. Every partner we accept is a partner we can support to a high standard, and turning some applications away is how we protect that. Micky Irons, founder of Mickai, built the programme around a simple principle: earn each deployment, and never take on more than can be done properly.

What are we learning in the beta?

A great deal about the seams. Real environments have their own hardware, their own network rules, and their own governance, and the SIOS has to meet all of it without asking the organisation to bend. Every deployment sharpens how the Mickai SIOS installs, proves itself, and runs day to day.

We are also learning what proof means to different buyers. A compliance lead, a security team, and a board each want to see sovereignty demonstrated in a different way, and the beta is where we refine how the SIOS shows its working to each of them.

Is this about scarcity?

No. A closed beta is not a velvet rope, and there is no fixed count being dangled for effect. The limit is honest capacity: how many partners we can support to the standard the work demands. As that capacity grows, so does the programme.

The engineering behind the SIOS is substantial, protected by 104 filed UK patent applications, approximately 2,340 claims, owned by Mickai LTD. Work of that depth deserves to be rolled out with care, and a design-partner programme is how we do it.

Frequently asked questions

How do I apply to the closed beta?

Applications are open at mickai.co.uk/beta. Tell us about your environment and your sovereignty requirement, and the team will follow up to talk through whether a design-partner deployment is a good fit.

Will my organisation definitely be accepted?

Not necessarily. The programme is selective by design, and only a small number of partners are taken on at a time so each one can be supported properly. A thoughtful application that describes a real requirement is the strongest thing to send.

Does the Mickai SIOS run on my own hardware?

Yes. Design partners run the SIOS on hardware they own, offline, so data stays inside the building and sovereignty can be proven rather than promised.

Is my data sent anywhere during the beta?

No. The SIOS is built to run without anything leaving your control, which is the whole point of sovereign AI. Being in the beta lets a partner verify that behaviour on infrastructure they own.

When will a wider release follow the closed beta?

The programme opens up as the capacity to support partners grows, and being a design partner now is the most direct way to shape what that wider availability looks like. To register interest, apply at mickai.co.uk/beta.