Skip to content
Invigilo

Our mission

We help schools integrate AI.

Invigilo is the one application a student installs. In teaching, the school sets its own AI policy; at exams and the large written projects, the exam regulations set it. Invigilo enforces both and documents how AI is actually used.

Why now

Exams are splitting into two tracks. The tool is still missing.

Exams without AI and exams with declared AI, often at the same school, in the same term. Schools across Europe need one tool that can safely enforce both, and make it easy to use AI well along the way. That is why Invigilo exists.

The direction

2023/24
Exam boards across Europe start writing AI rules: the IB and the UK’s JCQ both publish policies for declared AI use in assessed work.
2025/26
The trials are running. National ministries are piloting AI-permitted sections in written exams, with thousands of students using generative AI in assessed work, while other exams at the same schools stay closed.
Today
Ministries urge schools to monitor written exams, and data-protection authorities watch the tools they choose.

The record so far

A state-built exam guard
Scrapped after criticism.
The market-leading tool
Criticised twice by a national data-protection authority.

The platform

The policy, the enforcement and the record live in one place.

A student installs one app on their computer: Invigilo. The school and its teachers use a website, where they set the rules and follow along. New pieces arrive a little at a time, as ministries, schools and teachers approve them.

01

An AI policy in four levels

From a closed exam to full AI. For teaching, the school sets its own default level. At exams and the large written projects, the exam regulations set the level, and Invigilo enforces it.

02In closed testing

Vigila

Exam monitoring

The module runs only while the exam is open. A person opens it, and the recording deletes itself once the appeal deadline expires.

03Coming

Long assignments, in windows

Project work is monitored in bounded windows the student opens and closes. Not for weeks on end.

A student seen from behind working at their laptop in a classroom, daylight through tall windows, a notebook and books on the desk
04

The login the school already has

No new passwords and no separate user administration.

The app and the website

Students have an app. The school has a website.

Two sides of the same system. The student installs the app once on their computer. The school and its teachers sign in to a website, where they set the rules and read the record.

The student's computer

The Invigilo app

Lives on the student's own computer and follows the rules the school has set. The student can always see what applies.

The school's website

Everything runs in the browser

Teachers create exams, pick the level and read the record afterwards. Nothing is installed on school machines.

An empty auditorium of tiered wooden seats in green and grey, daylight through a glass facade at the left
Our mission

We help schools integrate AI, not prevent it.

Monitoring is where we start. Exams and assignments are where schools have the most urgent need today. The goal is broader: making it easy to set an AI policy the school can stand behind, and to use AI in a way that is visible and documented, not hidden.

Monitoring is the start
Exams and assignments are today's most urgent need, and where we began.
The policy is never ours
In teaching we enforce and document the policy the school itself chooses. At exams and the large written projects we enforce the rules the exam regulations set. Never rules of our own.
Visibility over prohibition
The goal is AI used in a way everyone can see and stand behind, not AI that disappears.

The direction

One application, modules that keep arriving.

A student installs Invigilo once. Vigila (exams) and LUCA (writing support) are the modules that live inside it, and the list grows as new initiatives from ministries, schools and teachers are approved. Whichever policy applies travels with them: the school’s own in teaching, the exam regulations at exams and the large written projects.

In closed testingVigila
Exams and assignments: the policy is enforced and documented where the consequences are greatest. The module is built and we are testing it ourselves. We are looking for the first schools to trial it with before it rolls out.
ComingPolicy beyond the exam
The same policy engine is meant to cover everyday teaching work, not only exam day.
In developmentLUCA
Our own language model for students. It is not built yet, and we are putting no date on it.

LUCA

Writing support for studentsIn development

LUCA is meant to help a student write better. Not to write for them.

The same application, two sides of one thing: the school gets its policy enforced, and the student gets help with sources and structure while they work. We train and host the model ourselves on our own servers in the EU, inside the policy the school has chosen.

LUCA is in training. Not all of the above arrives at once, and some of it is considerably harder to build than the rest. It is not part of the price and cannot be used today.

The first moduleIn closed testing

Vigila

Vigila observes during the exam. The teacher decides afterwards.

Exam regulations prohibit AI chatbots at exams and at the large written projects. Vigila enforces that on the student's own machine and documents that it held. The module runs only while the exam is open, and no flag becomes a decision while the exam is running: afterwards the teacher gets one document per seat, with every finding, the rule's steps, and a status only the teacher sets.

Launching in Q4 2026, ahead of the winter exams.

01During the exam02After the exam
Two steps. First the exam room while the exam runs: 40 seats with no names, and the events the rules record along the way. Then the document the teacher gets afterwards. 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.

Boundaries

What we never do.

During an examSystem running
  • We never use the webcam or microphone
  • We don't log what students type
  • We don't read process lists or network traffic
  • There is not a single national ID number in the system
  • We don't log which sites or applications have nothing to do with the exam: Netflix and Spotify appear nowhere
  • No decision is made automatically, a teacher decides

And we don't claim to catch everything

The boundaries exist because trust is what makes it possible to use AI well.

The ground it stands on

What we build on, and what we do not claim.

01

The data-protection authority's ruling, April 2024

The authority approved exam proctoring and criticised one thing: the software collected more than intended. Invigilo strips that away on the student’s machine before anything is sent.

02

The rules are built in

A processing agreement, data minimisation, and automatic deletion once the appeal deadline expires. Nobody has certified us, because there is no GDPR certification to hold.

03

Hosted in the EU

The servers and the self-hosted language model run in the EU. That includes LUCA, when it is ready.

You will not find the EU emblem, a GDPR seal or a regulator’s logo on this page. Authorities do not certify vendors, and a mark nobody granted us would be the exact opposite of what this section is about.

See the full security page

Uptime promise

Invigilo will never prevent a student from writing or submitting an exam, if our software fails, the exam continues unmonitored.

The modules

Two modules, each with a page of its own.

Both live in the same application, Invigilo, which a student installs once. One is built and in closed testing with us. The other is still in training.

A written exam in a large hall, rows of students at their computers, seen from behind

Vigila

01 VigilaIn closed testing

Exams and long-form work

The school’s level is enforced on the student’s machine while they write, and afterwards the teacher gets what it takes to assess a single seat.

Exam day
One delimited window, enforced seat by seat
Long-form work
Several short windows across the weeks
Afterwards
Findings with their rule trace, and a per-seat summary

Built and in closed testing. Launching in Q4 2026, ahead of the winter exams. Rates and the full feature list live on the module’s own page.

See rates and features

LUCA

02 LUCAIn development

Writing support for students

Our own language model, which a student can write with inside the level the school has already set. Same software, two sides of one thing.

Settled
Our own weights, EU hosting, the school’s policy
Not settled
Price and launch date

In training. No price and no date, and not all of the direction arrives at once.

Read about LUCA

Sign up

Get notified when Invigilo is ready.

We'll write to you well ahead of the exam term where it becomes relevant.

Feel free to mention if the school wants to be a pilot school in 2026.