Every AI tool pitched to a school makes a privacy claim, and most of those claims are about a vendor's cloud and a contract. There is another option: running the model on hardware inside the building. It gets described two wrong ways, as a compliance answer that settles everything, or as something only a university can manage. Here is what it actually changes.
What on-premises changes
When a model runs on a machine you control, the text a student types is processed on that machine. It is not sent to a third-party service to be stored or used to improve someone else's product. The retention policy is whatever you set. The logs are yours to read or delete. That is the concrete difference, and it is the reason to consider it.
It also changes who is accountable. There is no vendor between you and the behavior of the tool. If the model says something unhelpful, that is your configuration and your oversight, not a support ticket.
What it does not settle
It is not a COPPA or FERPA determination. Those are questions about what data you collect, why, who sees it, and how long you keep it. On-premises changes where processing happens. It does not answer the policy questions, and a school still needs its own answers.
It is not a safety guarantee. A local model can produce inappropriate output exactly like a hosted one. Content controls, instructor visibility, and a bounded activity matter more than where the model runs.
It is not a curriculum. A model running in the building is a capability. What students do with it, and what the teacher sees, is the actual work.
What a bounded activity looks like
The useful unit is not "students can chat with an AI". It is an activity with a teacher-visible objective and a result you can grade. Two we run:
- Fairness Lab: students give a generative model a neutral prompt, watch what it assumes, change one word, and watch the assumption move. They leave with evidence, not a slogan.
- Sound Lab: data becomes sound. A class hears a pattern, then builds the graph to check it.
In both, the instructor picks the activity, sees what students did, and keeps authority over what counts.
What it takes to run
For our sessions, nothing from the school beyond devices with a browser. We bring the activity and run it on hardware we operate. A school that wants its own setup needs a capable machine, a named person who owns it, and a written list of what students may do with it. Masterful can run workshops on the owner's self-hosted zOvermind platform and walk through what operating something similar would require. If that setup is not practical for your school yet, the sessions still run on our hardware.
The one-sentence version
On-premises is an operating model that keeps student input inside your building. Treat it as that, make your policy decisions on top of it, and put the effort into the activity and the oversight.