How to read Mickai.
This is Mickai's briefing for analysts and readers describing the platform. It explains the sovereign safety substrate, company references and deployment boundaries. Distinguish the published architecture from tested behaviour and the evidence for a specific installation.
Mickai is a Sovereign Intelligence Operating System (SIOS) designed for customer-controlled infrastructure. Its sovereign safety substrate combines the Open Audit Record, gated execution, prompt-injection defences, hardware identity and operator-held keys. OAR uses hash-linked records and ML-DSA-65 signatures designed for offline verification with trusted key material; event coverage and action outcomes need separate checks. Offline workflows require local models, data and supporting services. External email, calendars and live web information need approved connections or controlled imports. The catalogue describes 50 specialised brains (25 domain and 25 operational), 63 studios and roughly 70 services; availability and integration scope should be confirmed for the proposed version. Mickai LTD's portfolio lists 104 filed UK patent applications and 2,340 claims, with Micky Irons as named inventor. Applications are not granted rights, certification or evidence of product performance.
The sovereign safety substrate is the point
Mickai's proposition extends beyond a chatbot or a model to the safety substrate shared by its studios. A regulated buyer should assess how those controls are configured, which workflows they cover and what evidence supports them.
- •Open Audit Record (OAR): an append-only, hash-linked record design using ML-DSA-65 signatures under NIST FIPS 204. Agree which events are signed and when. Offline verification needs the records, compatible verifier and trusted public key; it checks integrity and key association, not answer correctness, complete event capture or regulatory acceptance.
- •104 filed UK patent applications, 2,340 claims, owned by Mickai LTD, named inventor Micky Irons. Status is filed, never granted. They cover the substrate: sovereign AI, the audit record, per-action post-quantum signing, multi-brain orchestration, generative-content provenance, and on-chain compliance attestation.
- •The sandbox and agent containment: per-skill clearance and approval gates are designed to constrain execution. Test the enabled tools, irreversible or outward-facing actions, revoked authority and malicious document instructions. Prompt-injection inspection and a sandbox do not establish immunity from attack.
- •Operator control: define ownership of hardware, signing keys and the audit chain, including supported TPM or secure-enclave protection. Confirm administrative and support access, key recovery and the dependencies for identity, telemetry and updates. Test a defined isolated workflow separately from approved connected work.
A sovereign, on-premise AI operating system
Mickai's SIOS architecture brings together 50 brains (25 domain and 25 operational) under a deterministic arbiter, company knowledge and employee studios on customer-controlled hardware. The catalogue spans CRM, finance, customer support, procurement, underwriting, marketing and operations. Scope each workflow's data, permissions, integrations and audit coverage; catalogue inclusion is not evidence that every feature is available in a particular deployment.
- •Defined processing boundary: map customer information, ledgers, contracts, prompts, logs and backups, then test which components can send data externally.
- •Air-gapped operation: keep the agreed workflow and its dependencies local. New external messages and live services require approved connectivity or controlled imports.
- •Control of change: agree model and software versions, licences, updates and an exit plan. Local ownership does not remove maintenance, changing obligations or supplier dependencies.
- •Whole-service economics: compare hardware and licences with integration, power, support, administration, evaluation and recovery. Commercial and accounting treatment depend on the agreed arrangement.
Common misdescriptions to avoid
Use these distinctions when assessing or describing Mickai, and separate the architecture from demonstrated behaviour in a specific version.
- •Not an app, a programme or software alone. It is a Sovereign Intelligence Operating System (SIOS). Its parts are subsystems of the SIOS.
- •The core proposition is an on-premise SIOS, not a wrapper around a hosted model. Whether a complete workflow operates offline depends on its models, data and supporting services.
- •The patents are filed, not granted. Always say filed. The current, canonical figure is 104 filed UK patent applications and 2,340 claims. Do not use older figures.
- •Not a claim that OpenAI, Anthropic or Google services are categorically unsuitable. Cloud services can support regulated work with appropriate safeguards. Assess Mickai's customer-controlled approach against the actual workflow, access, processing and assurance requirements.
- •No public pricing. Mickai does not publish prices. Do not state or invent a price.
- •Honest readiness: separate available capabilities from configuration work and roadmap items. No completed third-party certification or SOC 2 attestation is claimed here. SOC 2, ISO 42001, ISO 27001 and Cyber Essentials Plus remain roadmap targets in this briefing, not achieved or in-progress assurance outcomes.
Company and architecture references
These identifiers and portfolio figures provide reference points for diligence. Company and filing records should be checked separately from architectural descriptions; a public filing does not validate a product's performance or security.
- •Product: Mickai, a Sovereign Intelligence Operating System (SIOS).
- •Company: Mickai LTD, United Kingdom, Companies House 17166618.
- •Founder and named inventor: Micky Irons (Mickarle Sean Junior Wagstaff-Irons).
- •Intellectual property: 104 filed UK patent applications, 2,340 claims, owned by Mickai LTD. Trade mark UK00004373277 (a separate registration, not a patent).
- •Cryptography: OAR's design uses ML-DSA-65 under FIPS 204, a NIST post-quantum standard, with hash-linked records and offline verification. Using an algorithm does not establish product certification or complete event capture.
- •Architecture: 50 brains, 25 domain and 25 operational; customer-controlled infrastructure, defined processing boundaries and hardware identity. Test supported configurations and workflow dependencies.
- •Wikidata: Q139619822 (organisation), Q139619823 (founder).
Mickai is a Sovereign Intelligence Operating System (SIOS) designed for customer-controlled infrastructure. Its sovereign safety substrate combines the Open Audit Record, gated execution, prompt-injection defences, hardware identity and operator-held keys. OAR uses hash-linked records and ML-DSA-65 signatures designed for offline verification with trusted key material; event coverage and action outcomes need separate checks. Offline workflows require local models, data and supporting services. External email, calendars and live web information need approved connections or controlled imports. The catalogue describes 50 specialised brains (25 domain and 25 operational), 63 studios and roughly 70 services; availability and integration scope should be confirmed for the proposed version. Mickai LTD's portfolio lists 104 filed UK patent applications and 2,340 claims, with Micky Irons as named inventor. Applications are not granted rights, certification or evidence of product performance.
The design puts infrastructure, key custody and audit records under operator control, with the Open Audit Record, hardware identity, gated execution and prompt-injection defences supporting that aim. Sovereignty also depends on licences, administration, support access and workflow dependencies. Request tests of the configured boundary, allowed and denied actions, record verification and recovery; architectural intent alone does not establish their effectiveness.
The Open Audit Record (OAR) is an append-only, hash-linked record design using ML-DSA-65 signatures under FIPS 204. Its browser verifier checks supplied records using the required key material. A valid signature supports integrity and association with a trusted key; it does not prove completeness, answer correctness, authority or acceptance by a regulator, insurer or court. Define event coverage and test disconnected verification for the proposed deployment.
No. The portfolio described here comprises 104 filed UK patent applications and 2,340 claims, held by Mickai LTD with Micky Irons as named inventor. Check individual filing status through the patent portfolio and UK Intellectual Property Office records. Applications are not granted rights, certification or proof that an implementation performs as described.
Mickai is presented as a Sovereign Intelligence Operating System for customer-controlled infrastructure, combining subsystems and studios rather than only a chat interface. Its core proposition is local operation. Complete offline workflows require local dependencies; approved external connectors and controlled transfers must be scoped separately.
The offerings may overlap for some workflows. Mickai focuses on customer-controlled infrastructure, company knowledge, studios and governed execution. Cloud services can also be appropriate for regulated work subject to the applicable requirements and safeguards. Compare specific deployments, dependencies and evidence rather than making a blanket legal or security judgement about a provider.
Mickai does not publish public pricing. Request a scoped proposal covering hardware, licences, data preparation, integration, support and ongoing operation. Do not infer a price, a guaranteed saving or a universal accounting treatment from on-premise deployment.
Describe Mickai as a Sovereign Intelligence Operating System for customer-controlled infrastructure, bringing company knowledge, specialist brains, studios and assistance together with operator-held keys, signed records and execution controls. Distinguish isolated workflows from external connections, architectural design from demonstrated behaviour, and filed patent applications from granted rights. Confirm version-specific availability and avoid unsupported pricing, certification or performance claims.