Meet Neo — the learning companion that grows up with your pupils.
From Reception to results day and beyond, Neo gives every child a patient, curriculum-grounded companion. Axon OS gives your staff the controls, the approval gates and the off-switch.
A design concept in development. Everything you will see is synthetic.
Two surfaces. One rule: the school stays in control.
Ask Neo is the side pupils see: a warm, patient companion that answers from teaching material the school has approved. Axon OS is the side staff see: age-band controls, source packs, approval gates, activity summaries and a real off-switch. Nothing reaches a pupil that staff have not allowed, and nothing about a pupil leaves the school's control.
Ask Neo — for pupils
A curriculum-grounded companion that explains, encourages and asks good questions — and says “let's ask your teacher” when it should.
See Neo for Students →Axon OS — for staff
A calm governance surface. Set the rules once, approve changes when they matter, switch anything off at any time.
See Axon OS for Staff →Seven promises, kept by design
These are the commitments the whole product is built around. Each links to the full explanation.
Teachers hold the keys.
Approval gates on anything new, and a real off-switch per pupil, per class, per school.
Grounded, or silent.
Neo answers from school-approved source packs and shows its source — or says “let's ask your teacher”.
No surveillance, no scoring.
No behaviour analytics, no mood inference, no automated grading, no league tables of children.
Memory the learner owns.
Tiered, consent-based, visible, exportable, erasable. Neo remembers milestones, not moments.
Safe hands, fast handoffs.
Signs of distress end the AI conversation and bring in a trusted adult.
Synthetic first.
Every demo runs on invented pupils and invented data.
Claims we can prove.
This is a design concept in development — no deployment, outcome or endorsement claims anywhere.
From first story to final exam — and beyond
Neo's role changes as a child grows: story helper in Reception, practice coach in Key Stage 1, study buddy in Key Stage 2, study partner in Key Stage 3, revision partner at GCSE, pathway guide post-16 — and, at 18, a companion the learner owns outright. The school's controls change with each stage, and so does consent.
- Reception
- KS1
- KS2
- KS3
- KS4
- Post-16
- Lifelong
Try the synthetic demo
Pick a stage, talk to Neo as a synthetic pupil, then open the Axon OS dashboard and use the off-switch yourself. Every pupil, question and data point in the demo is invented.
Frequently asked questions
Four of the questions schools ask first. The full set is on the Safety & Governance page.
An honest note on where we are
Ask Neo and Axon OS are a design concept. There is no deployment, there are no school partners yet, and we claim no outcomes. What exists today is a fully worked design and a synthetic demonstration. If you lead a school and want to shape what this becomes, we would like to hear from you.
A patient companion that always shows its working.
Neo explains, encourages and asks good questions — using only the teaching material your school has approved. When it doesn't know, it says so and points to the teacher.
What Neo is
Neo is a conversational learning companion for pupils in UK state schools, starting with early literacy, numeracy and general learning skills. It is warm without being overfamiliar, curious without being intrusive, and patient without limit. Neo works Socratically: it prefers a good question to a quick answer, and hints and method to finished homework. Neo is not a friend, a parent or an authority figure — it is a helper, and it says so. It is the only part of the system a pupil ever talks to.
Grounded, or silent — how Neo answers
Every Neo answer must trace to a source pack: a bundle of curriculum material — for example, drawn from the National Curriculum (England) or the Curriculum for Wales — that the school has reviewed and approved. When Neo answers, it shows which pack the answer came from. When the question falls outside every approved pack, Neo does not guess. It says “let's ask your teacher” and, where the school allows, flags the question so the teacher can pick it up. Silence outside its sources is a feature, not a failure: it is what makes Neo safe to put in front of a class.
A safety filter also checks every message in both directions and fails closed: if it cannot classify a message safely, the message does not go through.
What Neo will never do
Just as important as what Neo does is what it is built never to do. Neo never:
- replaces a teacher, or presents itself as one;
- marks or grades work, or predicts grades;
- diagnoses learning needs or infers sensitive traits;
- handles safeguarding — signs of distress end the conversation and bring in a trusted adult;
- collects private confessions or encourages secrets;
- manipulates emotions or plays on attachment;
- gives unsupervised advice on high-stakes decisions;
- operates outside the controls set by staff and guardians.
These are product rules enforced by the system's policy layer, not tone-of-voice guidelines.
What it sounds like — a synthetic example
Sam is a synthetic Reception pupil (age 4) at Brookfield Primary, a synthetic demo school. In Reception, Neo is used in teacher-led sessions only — this exchange happens on the class screen with Ms Bell, a synthetic Reception teacher, leading.
- Ms Bell (to class)
- Neo, we've been reading the story of the little fox and the shiny conker. Can you help us remember what happened?
- Neo
- I'd love to! Let's remember together. The little fox went looking under the tallest tree. Can anyone remember what it found there?
- Sam
- A conker!
- Neo
- Well remembered — one shiny conker, right under the tallest tree! I wonder… what do you think the fox wanted to do with it?
- Ms Bell
- Sam says show the owl!
- Neo
- What a kind fox. And the wise old owl knew just what a conker can grow into. Shall we ask Ms Bell to turn to the page and find out together?
Source: Reception Storytime Pack — approved by Brookfield Primary (synthetic)
Notice what Neo does: it stays inside the story the class is reading, it asks rather than tells, it shows its source, and it hands the moment back to the teacher. In Reception there is no open chat and no memory beyond the session.
One companion, seven roles
Neo's job description changes as pupils grow. The full model, with controls and consent at each stage, is on the Journey page.
Reception (4–5)
Story helper and classroom companion — teacher-led sessions only.
KS1 (5–7)
Practice coach for early literacy, numeracy and learning habits.
KS2 (7–11)
Study buddy and curiosity engine, inside approved source packs.
KS3 (11–14)
Study partner — hints and method, never final answers.
KS4 (14–16)
Revision partner, aligned to exam-board specifications.
Post-16 (16–18)
Pathway guide for UCAS and apprenticeship exploration.
Lifelong (18+)
A learner-owned companion — the school link ends.
Every control in one calm place.
Axon OS is the staff side of Neo: age-band controls, approved source packs, agent permissions, approval gates, safe activity summaries, an audit trail — and an off-switch that always works.
A tour of the dashboard
Axon OS is organised around seven things a school actually needs to control. Here is each one, as it appears in the synthetic demo.
Age-band controls
Set what Neo can do for each stage, from Reception's teacher-led-only sessions to post-16 independent study. Defaults follow the stage model out of the box; anything you tighten stays tight. A change to an age band takes effect only after an approval gate.
Source packs
See every pack Neo can draw on, who approved it and when. Add a pack from approved curriculum material; retire one instantly. If a pack is retired, Neo stops citing it at once — there is no cached copy of anything you have withdrawn.
Agent permissions
The system is built from six agents with fixed jobs. Axon OS shows what each agent is allowed to do at your school and lets you narrow it. No agent can widen its own permissions, and the policy agent's rules cannot be overridden by anything else in the system.
Approval gates
Anything new waits for a named member of staff: a new source pack, a new stage capability, a change to memory settings, a new class rollout. Gates show what is being requested, what it changes and what it does not. Approve, reject or hold — with one tap, and a record either way.
Safe activity summaries
Teacher-facing summaries are pseudonymised and descriptive: which topics a class practised, where pupils asked for help, which questions Neo declined and referred to the teacher. No grading, no ranking, no behaviour or mood inference — the summary agent is built not to produce them. In this concept demo, all summaries are synthetic; pseudonymised signals from real activity would come only in a later governed pilot.
The off-switch
Per pupil, per class, per school. It takes effect immediately, it is visible in red, and it asks for one clear confirmation that restates the scope — it never asks you to justify yourself. Anyone with the right role can use it; the audit trail records that it was used, not an argument for why.
Audit trail
Every approval, rejection, configuration change and off-switch use is recorded with who, what and when — written for a governor or an inspector to read, not just a technician. Designed to align with the record-keeping expectations of UK GDPR accountability. The trail records staff governance actions only; it is not a monitor of staff work.
Governance in minutes — not another system to feed
Axon OS asks for staff time only when a decision is genuinely needed. Set-up follows sensible stage defaults; after that, the surface is quiet until an approval gate needs a human. There is no data entry, no weekly upkeep, no dashboard that guilt-trips you for not logging in. A typical week's governance for a class teacher is designed to be a handful of approvals, each under a minute. If Axon OS ever feels like a second MIS, we have failed at our own design brief.
“The off-switch is not buried in settings. It is the biggest control on the screen.”
What Axon OS will never be
Axon OS never covertly monitors staff, never ranks teachers, never exposes raw pupil conversations as a surveillance feed, never automates disciplinary or safeguarding workflows, and never bypasses human approval. It is a governance surface, not a monitoring product.
One companion, from first day to first job.
Neo's role, the school's controls and the learner's consent all change as a child grows. Here is the whole journey, stage by stage.
The seven stages
Each card shows the role Neo plays, one example of something allowed, one example of something blocked, and who holds the controls. Allowed and blocked examples are illustrative and synthetic.
- ReceptionStory helper
- KS1Practice coach
- KS2Study buddy
- KS3Study partner
- KS4Revision partner
- Post-16Pathway guide
- LifelongLearner-owned
Reception (4–5) · Story helper and classroom companion
Allowed: retelling the class story with the teacher leading on the class screen.
Blocked: any open chat with a pupil — there is none at this stage, and memory lasts only for the session.
Controls: teacher-led sessions only; picture-first and voice-first; class screen or supervised device; parents informed.
KS1 (5–7) · Practice coach
Allowed: a five-minute phonics practice activity from a pack the teacher picked this week.
Blocked: Neo suggesting its own activities outside the teacher-picked packs.
Controls: short guided activities only; ephemeral memory with teacher-approved milestones only; school controls, guardian visibility.
KS2 (7–11) · Study buddy and curiosity engine
Allowed: “Why do rivers bend?” answered from the approved geography pack, with a show-your-thinking scaffold.
Blocked: a question outside every approved pack — Neo says “let's ask your teacher” instead of guessing.
Controls: guided open questions inside approved packs; milestone ledger with teacher-approved promotions; school controls, guardian visibility.
KS3 (11–14) · Study partner
Allowed: hints and method on a homework problem, step by step, without ever giving the final answer.
Blocked: writing the answer, or the essay, outright — at any level of pleading.
Controls: the pupil can see and question their own memory ledger; digital-literacy coaching built in; school controls, guardian visibility.
KS4 (14–16) · Revision partner
Allowed: retrieval practice and a revision plan built from exam-board source packs aligned to the pupil's specification.
Blocked: predicted grades or marking — Neo never does either.
Controls: learner assent plus school control plus guardian visibility (the 13–15 consent tier while the pupil is under 16).
Post-16 (16–18) · Pathway guide
Allowed: exploring UCAS routes and apprenticeships, and coaching independent study habits.
Blocked: telling a learner which choice to make — Neo informs high-stakes decisions; trusted adults supervise them.
Controls: learner-first consent with a school policy overlay.
Lifelong (18+) · Learner-owned companion
Allowed: exporting the Neo Passport and continuing privately — or deleting everything.
Blocked: any school access — the school link ends at 18.
Controls: the learner owns everything.
Consent that grows up too
Consent is not one checkbox at enrolment. It is a ladder that climbs with the learner, designed to align with UK GDPR (where the digital consent age is 13) and the ICO's Age Appropriate Design Code.
- Under 13: the school controls Neo's use; parents and guardians are informed and have visibility rights.
- 13–15: the learner gives assent, the school keeps control, guardians keep visibility.
- 16–17: consent becomes learner-first, with a school policy overlay.
- 18+: the learner owns everything — including the right to walk away with their data, or erase it.
Memory is opt-in and tiered at every rung: visible to the learner from KS2, exportable and erasable throughout.
The Neo Passport — memory the learner owns
Over the years, Neo builds a ledger of milestones — not transcripts, not moments, and never anything a teacher did not approve for the ledger at the younger stages. At 18, that ledger becomes the Neo Passport: an export the learner owns outright. Take it and continue with Neo privately, take it and go, or delete it entirely. The school keeps nothing personal; the learner keeps everything or nothing, as they choose.
Safety is the product, not a feature of it.
The Seven Promises in full, the data rules, the safeguarding boundary and the claims we refuse to make.
The Seven Promises, in full
- Teachers hold the keys. Nothing new reaches a pupil without a named member of staff approving it: not a source pack, not a capability, not a memory setting. And the off-switch is real — per pupil, per class, per school, immediate, and never more than one tap away.
- Grounded, or silent. Neo answers only from school-approved source packs and shows its source with the answer. Outside its packs, Neo does not improvise — it says “let's ask your teacher”. A wrong-sounding answer can be traced to its pack and the pack can be corrected or retired.
- No surveillance, no scoring. There are no behaviour analytics, no mood inference, no automated grading and no league tables of children — and no staff-monitoring equivalents on the Axon OS side. These are not settings that default off; they are capabilities the system does not have.
- Memory the learner owns. Memory is opt-in and tiered by stage: session-only in Reception, teacher-approved milestones only in KS1, a full ledger the pupil can read from KS2 — and question and challenge from KS3. It is exportable and erasable at every stage. Neo remembers milestones, not moments.
- Safe hands, fast handoffs. If a pupil shows signs of distress, the AI conversation ends and a trusted adult is brought in — at our synthetic demo school Brookfield Primary (synthetic), that route leads to Mrs Shah, the synthetic deputy head and designated safeguarding lead. Neo is never a counsellor, never asks follow-up questions about a disclosure, and never stores its content. The design is signpost and hand off, aligned to the school's own KCSIE-based processes; Neo is not a safeguarding tool and takes no safeguarding decisions.
- Synthetic first. Every demonstration, including everything on this site, runs on invented pupils and invented data. No real child data would enter the system before a school-governed pilot with a full Data Protection Impact Assessment (DPIA).
- Claims we can prove. This is a design concept in development. We claim no deployment, no outcomes, no approvals and no endorsements — and this page ends with a list of claims we commit never to make.
Three colours of data
| Class | What it covers | Where it can go |
|---|---|---|
| GREEN | Public curriculum outlines, synthetic demo data, school-approved teaching content. | The only class in this concept demo. Powers everything you see on this site. |
| AMBER | Pseudonymised progress signals and teacher-approved summaries. | A later governed pilot only, after a full DPIA — never in this demo. |
| RED | Identifiable pupil records, names and class lists, grades and marks, behaviour records, safeguarding material, health data, staff and parent private data, live MIS / Google Classroom / Workspace data, credentials. | Never enters the system. Not in the demo, not in a pilot, not ever. |
The safeguarding boundary
Neo is not a safeguarding tool and must never become one by accident. The boundary is simple: any sign of distress ends the AI conversation and routes the pupil to a trusted adult, following the school's own safeguarding processes under KCSIE. Neo does not probe, does not counsel, does not categorise concerns and does not keep the content of a handoff. Axon OS records that a handoff happened — for accountability — not what was said. Safeguarding judgement stays where it belongs: with trained people.
Two statements, in plain words
No surveillance: Neo and Axon OS do not watch children or staff. There is no behaviour scoring, no mood detection, no raw-conversation feed for adults to browse, and no staff analytics. No grading: Neo does not mark work, does not grade it, does not predict grades and does not rank pupils — and the summaries teachers see are built by an agent that cannot produce grades or rankings.
What parents and guardians see
Under 13, parents and guardians are informed before Neo is used with their child and hold visibility rights over what Neo is and how it is configured for their child's stage. From 13 to 15 they keep visibility while the learner adds assent. Schools decide, within the consent ladder, how that visibility is delivered — designed to fit existing home–school channels rather than adding a new app to check.
What we will never claim
A short list we intend to be held to. We will never claim:
- that Neo or Axon OS is deployed in any school, until it truly is;
- that any educational outcome has been achieved, without published evidence;
- that the product is “compliant with” or “approved by” any regulator, standard or body — we design to align, and say only that;
- that any school, teacher, parent or pupil endorses the product, without their documented, freely given agreement;
- that Neo replaces teachers, or ever could;
- that anything on this site involves real children or real school data — it never does.
Frequently asked questions
Neo is designed age-band by age-band around the ICO's Age Appropriate Design Code. In Reception there is no open chat at all: Neo appears only in teacher-led sessions, picture-first and voice-first, with memory that lasts only for the session. Every message in both directions passes a safety filter that fails closed, and any sign of distress ends the conversation and brings in a trusted adult. “Designed to align with” is the strongest claim we make — and everything so far runs on synthetic data only.
The AI conversation ends and the pupil is routed to a trusted adult, following the school's own safeguarding processes under KCSIE. Neo does not ask follow-up questions, does not counsel, does not categorise the concern and does not keep what was said. Axon OS records that a handoff happened — not its content. Neo is not a safeguarding tool and takes no safeguarding decisions; people do.
The design is built around both from the start: a consent ladder that respects the UK digital consent age of 13, data minimisation through the GREEN/AMBER/RED classification, learner-visible and erasable memory, and an audit trail written for accountability. We say “designed to align with” deliberately — no regulator has assessed this concept, and we will never imply otherwise.
Yes — a full Data Protection Impact Assessment is a precondition of any pilot, not a follow-up to one. No real pupil data enters the system before a school-governed pilot with a completed DPIA, and even then the ceiling is pseudonymised AMBER-class data. Identifiable records — names, class lists, grades, behaviour or safeguarding material — are RED class and never enter the system at any phase.
Pricing is deliberately unset at concept stage, and we will not invent a number to look further along than we are. The eventual model is expected to be a school or trust subscription reached through a pilot-to-licence path. Co-design participation costs nothing.
Yes, and this is the promise we most want to be tested on. The off-switch works per pupil, per class and per school; it takes effect immediately; it sits in plain sight rather than in a settings menu; and using it never requires a justification. The audit trail records that it was used — nothing about why. Try it in the synthetic demo.
No, and it is built so it cannot drift that way. Neo never presents itself as a teacher or authority figure, defers to the teacher by design — “let's ask your teacher” is a core behaviour, not an error state — and in the early years it only works with a teacher leading. Axon OS exists so that teachers govern Neo, not the other way round. Anything that reduced teachers to supervisors of an AI would fail our own never-list.
Neo is designed for short, purposeful sessions, not open-ended engagement. There are no streaks, no badges-for-time, no notifications pulling children back, and nothing designed to maximise minutes — engagement-maximising patterns sit on our never-list because they conflict with the Children's Code's best-interests standard. In Reception and KS1, session length and timing are wholly in the teacher's hands.
Two protections work together. First, grounding narrows the space for error: Neo answers only from school-approved source packs and shows its source, so a wrong answer is traceable to a correctable pack — and outside its packs, Neo says “let's ask your teacher” rather than improvising. Second, honesty handles the rest: no AI system is free of mistakes and we will not claim otherwise, which is why staff can retire a pack instantly and why Neo is never the final word on anything that matters.
Neo remembers milestones, not moments — and at the younger stages, only milestones a teacher has approved. Memory is opt-in and tiered: session-only in Reception, teacher-approved milestones only in KS1, a visible ledger from KS2 that the pupil can read — and, from KS3, question and challenge. It is exportable and erasable at every stage, and at 18 it becomes the learner's property outright as the Neo Passport — to keep, take elsewhere, or delete entirely.
Under 13, you are informed before Neo is used with your child and you hold visibility rights: what Neo is, what it is allowed to do at your child's stage, and how memory is configured. From 13 to 15 your visibility continues alongside your child's assent. You will never see raw conversation feeds — no adult does, because no such surveillance feed exists — but you will never be in the dark about what Neo is doing with your child either.
No — never, at any stage. Neo does not mark, does not grade, does not predict grades and does not rank pupils, and the teacher-facing summary agent is built without the capability to produce any of those. At KS4, Neo is a revision partner: retrieval practice and revision planning from exam-board source packs. Judging attainment stays entirely with teachers and exam boards.
See it work — on invented pupils only.
Everything in this demo is synthetic: the school, the pupils, the questions and every data point. Nothing you do here touches any real system or any real child.
What on this site is real?
The design thinking is real. Everything else — every pupil, teacher, school, conversation and data point — is synthetic. Sam, Amara, Leo, Priya, Dan, Maya, Ms Bell, Mr Okafor, Mrs Shah and Brookfield Primary are all invented for this demonstration. There is no deployment, no pilot, no school partner and no real child anywhere in this product yet — and there will be no real pupil data before a school-governed pilot with a full DPIA.
Before you start: what this demo is
This is a concept demonstration of Ask Neo and Axon OS running entirely on synthetic data. The pupils — Sam, Amara, Leo, Priya, Dan and Maya — are invented, as is Brookfield Primary (all synthetic). The demo shows design intent: how grounding, gating and the off-switch are meant to feel. It does not show a live product, and nothing you type is stored or sent anywhere.
Four things to try
1. The stage selector
Move between the six synthetic pupils — from Reception to Lifelong — and watch Neo's role, tone and permissions change: the same companion, governed differently at every age.
2. Talk to Neo
Ask Neo the sample questions provided at each stage — or, at the stages that allow typing, type your own — and watch it answer from its source pack, show the source, and decline what falls outside. Try to get a final homework answer out of KS3 Neo. You won't.
3. Open Axon OS
Switch to the staff view: a mock dashboard with age-band controls, source packs, pending approval gates and a synthetic activity summary. Approve or reject a waiting gate and watch the effect.
4. Use the off-switch
Turn Neo off for a synthetic pupil, then a whole class. It takes effect immediately, and the audit trail records it. Turning it back on requires the same deliberate action.
The synthetic demo
All of this runs in your browser's memory only. Refreshing the page resets everything to its invented starting state; nothing is saved, transmitted or logged.
Demo control. In a real school the stage is set by staff in Axon OS, never by the pupil. Choose a synthetic pupil:
Ask Neo pupil view
Synthetic demo dataScripted concept demo. Nothing you type is stored or sent anywhere.
Axon OS staff view · Brookfield Primary (synthetic)
Synthetic demo dataThe off-switch
Pause Neo immediately. No justification is ever required; the audit trail records that it was used, not why.
Maya's account is learner-owned — the school off-switch does not reach her. Pupil and class scopes are unavailable while Maya is selected.
Age-band controls
Tightening applies immediately. In the full design, loosening a band waits at an approval gate.
Source packs
The only material Neo may speak from. Retiring a pack takes effect in the pupil view at once.
Approval gates
Nothing new reaches a pupil without a named adult saying yes. There is no approve-all control and no auto-approve setting.
Decided in this session
Safe activity summaries
Class-level. Pseudonymised. No rankings, no individual profiles, no behaviour or mood inference. All figures here are synthetic.
Audit trail
Who did what, and when — written for a governor or an inspector to read. Read-only; nothing can edit or delete audit rows.
What you won't find here
No real integrations, no live data, no account creation, no pupil records — and no safeguarding scenarios. Handoff behaviour is described on the Safety page rather than dramatised with a synthetic child, deliberately. This demo submits nothing: every control on this page is self-contained in your browser. (The only part of the site that transmits anything is the pilot-interest form on the Contact page, and only the details you type into it.)
A roadmap with no dates and no promises we can't keep.
Five phases, in order. We are in the first. Each phase says what it is — and what it is not.
The five phases
Phase 1 — Concept and synthetic demo. You are here.
What it is: a fully worked design, this site, and an interactive demonstration running entirely on synthetic data.
What it is not: a product, a pilot, or anything that has touched a real school or a real pupil.
Phase 2 — Co-design with founding schools.
What it is: working sessions with a small number of UK state schools to reshape the design around real classroom practice — on synthetic data throughout.
What it is not: a trial with pupils, or any collection of school or pupil data.
Phase 3 — Governed pilot with a full DPIA.
What it is: the first contact with real school life: school-governed, opt-in, preceded by a full Data Protection Impact Assessment, with AMBER-class data at most and the school holding the off-switch throughout.
What it is not: a launch, and never a source of RED-class data — identifiable records stay out of the system permanently.
Phase 4 — Staged rollout, Reception to KS2.
What it is: primary-first expansion of what the pilot proves, stage by stage, each stage gated on the evidence and the school's approval.
What it is not: a big-bang rollout, or expansion to older stages before the youngest are properly served.
Phase 5 — All-phase architecture plus Neo Passport.
What it is: the full seven-stage model, through to the learner-owned Neo Passport at 18.
What it is not: a departure from the promises — every phase, including this one, keeps all seven.
No dates appear here because we will not invent them. Sequence is a promise; timing is not.
Serious school technology, built slowly on purpose.
We are building the learning companion we would trust with our own children — which is why we refuse to rush it into schools.
Why we are building this
Every child deserves a patient explainer that never tires, never mocks and never gives up on them — and every school deserves absolute control over any AI that speaks to its pupils. Most educational AI picks one side of that sentence. Ask Neo and Axon OS exist to prove you can build both at once: a companion that grows with a child from Reception to adulthood, under governance a headteacher can hold in one hand.
Principles we design by
- School control is not negotiable. Approval gates and a real off-switch come before every feature.
- Grounded, or silent. An AI that guesses at children is worse than no AI at all.
- Memory belongs to the learner. Milestones, not moments; visible, exportable, erasable.
- Synthetic first. Invented data until a school-governed pilot with a full DPIA says otherwise.
- Honest claims only. “Designed to align with” — never “compliant with” or “approved by”.
- Teacher workload is a design constraint. Governance in minutes, or we have built it wrong.
Where we are, honestly
Axon Education (a working name) is an independent UK education-technology project at concept stage. There is no deployment, there are no school partners yet, no pilot has run, and no outcome is claimed. What exists is a complete design, this site, and a synthetic demonstration. We publish this honestly because the trust of schools is the only asset this project cannot recover if lost.
Help shape it before it exists
The next phase is co-design with a small number of founding UK state schools — primary-first. Founding schools shape the stage controls, the approval gates, the summaries teachers actually want, and the boundaries that matter in real classrooms. Everything stays synthetic throughout co-design. If that sounds like your school, we would genuinely like to talk.
Bring your school into the design.
We are looking for founding UK state schools — primary-first — to co-design Neo and Axon OS before any pilot exists. No commitment, no data, no cost at this stage.
What registering interest means
Registering interest starts a conversation, nothing more. We will show you the full concept, walk your team through the synthetic demo, and listen hard to what your school would need before any of this could earn a place in your classrooms. Founding schools get a real say in the design — the stage controls, the summaries, the gates — and set the bar the eventual pilot must clear, including its full DPIA. There is no pricing to discuss yet: pricing is deliberately unset at concept stage.
Register interest
This form is for schools registering pilot interest. Tell us what you'd like to discuss, and please include only your own contact details — never any pupil data, or anything that could identify a child. It's a design concept in development, so there's nothing to sign up to and no product to buy.
Direct contact
The form above is the quickest way to reach us. A direct email route, hello@askneo.co.uk, is being set up; until it is live, please use the form.