Multi-Academy Trusts (Primary and Secondary)
Multi-academy trusts hold some of the most sensitive records in the public sector: child data, safeguarding logs, attendance flags and pastoral notes spanning thousands of pupils across dozens of schools. Trusts want to spot vulnerable students earlier by joining these signals together, but UK GDPR Article 8 protections for children's data and statutory safeguarding duties make it unacceptable to send that material to a third-party cloud for processing. Mickai installs the full AI capability on hardware the trust owns, under keys the trust holds, so safeguarding analytics run air-gapped inside the trust's own estate. This removes the third-party cloud-exposure vector for child data, and the trust keeps its existing safeguarding and data-protection obligations intact.
Multi-academy trusts and their central safeguarding, data-protection and IT leadership.
GDPR Article 8 child data and safeguarding records cannot sit on a third-party cloud, yet the signals that flag vulnerable pupils are scattered across schools and systems.
Air-gapped safeguarding analytics installed on hardware the trust owns, under keys the trust holds, joining pupil signals across every academy inside the trust's own estate.
Vulnerable students are flagged earlier, the third-party cloud-exposure vector for child data is removed, and what happens in the server room stays in the server room.
Five advantages hold across every sector, and they are architectural, not promotional. The third-party cloud-exposure vector is removed; your own physical, insider, and compliance controls remain yours.
The data never leaves your hardware, so no third party and no cloud-provider employee ever sees it. What happens in the server room stays in the server room.
You own the compute and the capability, so the system runs independent of the internet and of any cloud vendor's pricing, terms, or availability.
The data never crosses a geographical or digital border because it never leaves the building, which removes the cross-border-transfer and third-party-processing friction of UK GDPR, Schrems II, and the sector rules. You keep your own obligations.
Fine-tune and run retrieval on your deepest archives to build a hyper-customised co-pilot, with no risk of your proprietary edge training a public model or leaking.
After the hardware and licence, queries cost essentially electricity. A capital asset you own and depreciate, instead of volatile per-token cloud bills.
There is no third-party cloud path, so no competitor and no vendor insider can scrape, intercept, or subpoena your prompts or your fine-tuned weights from the internet. The trust vault is closed by architecture.
You own the software snapshot on your own hardware, so a change to a cloud vendor's terms, a model deprecation, or an outage cannot reach you. The system stays predictable and auditable on-premise as the rules evolve.
The specific rules that bar mainstream cloud AI from this sector's regulated data. Each one demands a named, auditable perimeter the operator controls, which a shared multi-tenant cloud cannot give.
The kind of organisation this serves, named illustratively from public information to characterise the market. These are target profiles, not customers: Mickai has no relationship, engagement, trial, or endorsement with any of them.
The enterprise studios that lead in this sector, drawn from the eighteen that sit on the one sovereign substrate. Each runs on hardware the organisation owns, under one set of operator-held keys, writing to one Open Audit Record.
Compliance and Regulator Mode
Maps every safeguarding workflow to UK GDPR Article 8, KCSIE and DfE data rules, and produces the audit-ready records a trust needs to evidence lawful processing of child data on its own estate.
Executive BI
Gives the trust board and central team a cross-school view of safeguarding, attendance and wellbeing signals so vulnerable students surface earlier, while pupil data stays inside the trust.
CRM
Holds the unified pupil and family record that ties pastoral, attendance and safeguarding contacts together inside the trust, replacing scattered third-party tools that would otherwise widen child-data exposure.
Training and LMS
Runs staff safeguarding and KCSIE training and tracks completion across every academy, keeping designated-safeguarding-lead readiness current trust-wide.
HR
Manages staff vetting status, safer-recruitment checks and central HR records across all schools in the trust on hardware the trust controls.
See all eighteen on the sovereign services catalogue.
Multi-academy trusts are consolidating central functions across growing numbers of schools while facing tightening expectations on how children's data is handled, which creates strong demand for safeguarding and pupil-data analytics that can run without exporting child records to external processors. A sovereign, on-premises capability lets trusts modernise safeguarding insight while removing the cross-border-transfer and third-party-processing friction that cloud tools introduce.
Money won, money saved, risk removed, on hardware you own.
Trusts gain earlier identification of vulnerable students from joined-up safeguarding, attendance and pastoral signals while removing the third-party cloud-exposure vector for child data; physical and insider controls remain the trust's own. Running independent of the internet and external vendors also displaces recurring per-pupil SaaS and cloud-processing costs and narrows the data-protection-impact-assessment surface that external processors would otherwise widen.
Map the sovereign stack to your multi-academy trusts (primary and secondary) estate.
Briefings are for organisations weighing a sovereign, on-premises deployment. Tell us about your estate and we will walk the pack, the regulatory crosswalk, and the deployment that fits your estate.