Skip to content
Invigilo
A large lecture hall, rows of empty tip-up seats with writing tablets, daylight from tall windows at the back

Vision

AI isn't leaving the classroom. The question is whether its use is visible.

Invigilo is a school AI platform: one application a student installs once, with named modules inside it. The first enforces and documents the school's AI policy during exams and assignments. The direction is broader: making it easy to set a policy the school can stand behind, and making AI use visible rather than hidden.

Why

A ban is one setting out of four.

Exam boards across Europe already recommend formats where AI plays a part, not only formats where it is blocked, and student bodies have pushed for a focus on responsible use rather than on catching misuse. A tool that can only prohibit solves half the problem: a school has to enforce a closed exam and document an open assignment with the same application.

01

We never set the level ourselves

The four levels come from the rule engine inside the application itself, from open AI to fully blocked. At exams and the large written projects the exam regulations set the level; in teaching and in the school’s own assignments the school sets it. The software enforces exactly whichever applies.

An open laptop on a classroom desk, more desks and machines out of focus behind it
02Coming

An open assignment is documented, not blocked

An exam is one unbroken window. An assignment running over weeks is short windows with ordinary schoolwork in between. Where AI is declared, the same rule trace becomes a source reference instead of a flag.

TodayIn closed testing

Vigila

We begin at the exam, because that is where the need is greatest.

Vigila is the first module. It runs only while the exam is open, enforces the school's policy on the student's own machine, and afterwards assembles one document per seat: every finding, the steps of the rule behind it, and a status only a teacher can set. No flag turns into a decision while the exam is running.

Vigila is built, and we are running it through ourselves. We are looking for the first schools to trial it with. Launching in Q4 2026, ahead of the winter exams. And we do not claim that any monitoring tool can make misuse impossible: it can make use visible and documented, so a teacher decides on an informed basis.

See Vigila in detail
An extract. The document reproduces every finding for the seat with the rule's steps, the teacher's status, and the language model's advisory answer where it was consulted.

Direction

The same foundation should do more than monitor, over time.

The trust a school shows by letting us enforce and document an exam is the foundation everything else is built on. The list of modules grows as new initiatives from ministries, schools and teachers are approved, and the policy the school has set applies in all of them. We build at the pace schools and regulation allow, not faster.

  1. In closed testing

    Vigila

    Exams and assignments: the policy is enforced and documented where the consequence for a student is greatest.

  2. Coming

    Policy beyond the exam

    The same policy engine is meant to cover everyday classroom work, so a school does not need one rulebook for exam day and another for the rest of the year.

  3. In development

    LUCA

    Our own language model for students: help with sources and structure, inside the school's policy. It is not finished, it is not part of the price, and we put no date on it.

Together with schools

A tool nobody trusts gets dropped, however well it works technically.

The goal is for AI to lift how much students learn as much as it has lifted the pace at which software gets built. That takes a tool teachers and students helped shape, not one rolled out over their heads. So the policies and the modules that come next are to be shaped together with the first schools that join, before anything rolls out widely.

01In closed testing

The first schools run it through before launch

We are testing the module ourselves, and looking for the first schools willing to run it at real exams and correct it while we build. What teachers and students report back is what should decide the changes before launch.

A wide teaching room, rows of desks along a wall of windows, nobody present

Vigila

What doesn't change

Whatever module we build next.

The policy does not come from us
At exams and the large written projects it is set by the exam regulations; everywhere else by the school itself. We enforce it and we document it, and we do not sell an opinion about what it should be.
A teacher makes the call
No decision that affects a student is made automatically. A finding is a question for the teacher, not a verdict.
Visible, never hidden
What is recorded, and what a student declares, is always visible to that student. No module uses the webcam, the microphone or keystroke logging.
An empty school corridor, doors along one side and windows along the other, daylight at the far end

Next step

Want your school in from the start?

We take a handful of schools in at a time, and we write to them before each new step rolls out.

Sign me upTry the live demo