Air-Gapped Intelligence
Intelligence for the places the cloud cannot reach: contested environments, the degraded edge, and the systems that must keep thinking with the cable pulled.
I have spent years now building for the moment the cable gets pulled. Most of the industry has spent those same years assuming the cable never will. Those are two very different engineering cultures, and the gap between them is the subject of this book. I am Micky Irons, and I founded Mickai to build a Sovereign Intelligence Operating System, a SIOS, that keeps thinking on the operator's own hardware whether the link to the wider world is healthy, degraded, or gone entirely. This is not a thought experiment for me. It is the core design constraint of everything we have filed and everything we
Why connectivity-dependent intelligence fails exactly where it matters most?
The modern AI stack carries a hidden assumption so deep that most builders never name it: that there is always a route to a datacentre. Inference happens somewhere far away, on hardware you do not own, reached over a network you do not control, and the answer returns along that same fragile thread. When the thread holds, the illusion is seamless. The model feels local, instant, omnipresent. But the cloud is not an abstraction floating above the world. It is a specific set of
Offline-first as a discipline, and the trade-offs partition tolerance forces you to face?
The phrase offline-first gets used loosely, so let me be precise. Offline-first is not a degraded mode you switch into when the network drops. It is the primary mode, the one the system is built around, with online treated as an enhancement layered on top. The difference is not cosmetic. In a fallback architecture the offline path is the afterthought, the poorly tested branch nobody exercises until it fails. In an offline-first architecture the offline path is the main road a
Tamper-evident records, durable queues, and intelligence that holds the line alone?
Here is a question that exposes most edge architectures immediately. When your system takes a consequential action during a total communications blackout, where does the proof go? In a cloud-first design the answer is uncomfortable: nowhere, or into a local file anyone could later edit, because the real audit log lived on a server you could not reach. The outage that took your connectivity also took your accountability. That is a failure I was not willing to accept, because t
Micky Irons
Founder of Mickai LTD (Companies House 17166618, England and Wales). Named inventor on the Mickai SIOS patent corpus, recorded on the UK Intellectual Property Office public register at numbers GB2607309.8 to GB2611702.8. Trade mark Mickai registered at UK00004373277 (classes 9 and 42, filed 15 April 2026). Before founding Mickai, Micky was a Sellafield site worker, and the egress constraint observed from inside the regulated workstation is the engineering origin of the substrate.
- Web: mickai.co.uk
- Crunchbase: crunchbase.com/person/micky-irons
- LinkedIn: linkedin.com/in/mickyirons
- GitHub: github.com/Micky-CMO
- Mickai company: linkedin.com/company/mickai
- Mickai Crunchbase: crunchbase.com/organization/mickyirons
- Contact: press@mickai.co.uk