Colour only when it means something.
Only the fail stands out.
Red is a fail or a cancelled lesson, always with the word written out. Orange is a room change. Blue is now or new. A subject only gets a small dot in its own colour.
In development · looking for pilot schools for 2027–2028In development · pilot 2027–2028
This is how a school day
should feel.
Ludendo is a new school platform for Dutch secondary education, still in development. Timetable, homework, grades, attendance, messages and administration in one calm system, for students, parents, teachers, mentors, administrators and school leaders.
All screens on this site show made-up data.
· Parent
Reporting sick
takes two taps.
Sara isn’t feeling well. Her father reports her sick from the kitchen table. No phone call to the school office, no note, no form.
Already works in the real version. Parents reporting sick, also for several children at once.
Skip the school day- Choose ‘Report sick’. For today, or until a date you choose.
- Done. You get a confirmation straight away. Even if the school is still closed.
- The school knows. The mentor and today’s teachers see it right away, exactly where they need it. This mark follows the report through the day.
· Student
Knowing where to be,
before you walk in.
Lotte is at the bike shed. English has moved and history is cancelled. She sees it at a glance, without searching.
The notice at the top is a notice inside Ludendo itself. Notifications on your phone come later.
- A dot means new. You haven’t seen this yet. Open it, and the dot is gone.
- A room change in orange. Only that. No colours that mean nothing.
- Cancelled, with the word written out. You see right away how long you’re free.
· Teacher
One tap.
And the lesson begins.
Mr Bakker stands in front of 4V2. He set up his slides, the video and the homework on Tuesday. All he has to do is begin.
How it works in the prototype. In the real version, taking attendance at the start of the lesson already works; starting the lesson and the smartboard are being built.
- Start lesson. Everything for this lesson is on one screen.
- Attendance is almost done. Everyone is marked present. Sara is already marked sick: her father reported it at 07:46. Nobody has to retype anything.
- On the board. One more tap and the slides are on the smartboard. The homework is already in the students’ planners.
· Teacher and student
A grade is only final
when you say so.
Before his 13:45 lesson, Mr Bakker enters the last grades. Students and parents only see them once he taps ‘Show students and parents’. Then it arrives, with an explanation.
How it works in the prototype. In the real version, grades are being built.
- Enter without rushing. Nobody sees what you enter yet. The average updates as you go.
- Show students and parents. One button for the whole test. At that same moment, Lotte gets a notice.
- An answer, not a table. Lotte sees her grade and what it does to her average. Her parents see the same.
· Mentor
Seeing who needs attention.
With the reason attached.
Ms De Wit is the mentor of 4V2. She doesn’t have to dig through lists herself. Ludendo brings together what stands out, and says why.
How it works in the prototype. In the real version, this overview comes later.
- What stands out is at the top. Daan was late three times this week and got a fail.
- The reason is right there. No colours or scores, just what happened. Sara’s sick report from this morning is there too.
- Act right away. Plan a meeting or message the parents, from the same place.
· School leaders and IT
The bell.
Everything is where it belongs.
The data belongs to the school, not to us. You can export all of it at once, at any time, even if you ever want to switch. And you can always see who viewed what.
Already works in the real version. Export and the access log. Grades and messages join the export once they’re ready.
· Parent
A quiet evening.
No pile of notifications.
What mattered is in one place. The rest can wait until Monday.
Who it’s for
One system.
Every role sees what it needs.
Students, parents, teachers, mentors and school leaders work in the same system. Each role gets its own simple view.
Student
Your day at a glance.
- Your timetable, with what has changed.
- Homework and tests in one place, ready to tick off.
- Your grades, with what they do to your average.
Parent
Knowing how things are going. Without searching.
- Report your child sick in two taps.
- Grades and absences as soon as the school shares them.
- Messages from the mentor in one place.
Teacher
Teach. The rest takes care of itself.
- Start a lesson with everything on one screen.
- Attendance in a few taps, already filled in.
- Enter grades and decide yourself when they become visible.
Mentor
Seeing who needs attention.
- What stands out in your class, with the reason attached.
- Plan and record meetings.
- Contact parents from the same place.
School leaders and IT
An overview, without duplicate work.
- Timetables, classes and permissions in one place.
- Export all data, whenever you want.
- A log of who viewed what.
Also for administration, student care, careers guidance, exams and timetablers: those roles are in the prototype.
Why it’s different
Calm.
Because school is busy enough.
New disappears once you’ve seen it.
What you opened has no dot any more.
One kind of dot, for everything you haven’t seen yet. Open it, and it’s gone.
An answer, not a table.
The grade, and what it does.
Not just a grade, but what it means: ‘your average went from 7.8 to 7.6’.
One main button per screen.
One blue button: the next step.
What you most often want to do right now is the blue button. Everything else stays calm.
Light and dark, phone and laptop.
Follows your device.
Ludendo follows your device’s setting and works on any screen.
Made for Dutch secondary schools
The rules are built in.
It keeps count for you.
Ludendo knows the rules of Dutch education. The system keeps count and tells you in time what needs to happen, so you don’t have to track it yourself. The absence counter already works in the real version; the rest is in the prototype.
Compulsory schooling and absence
Example · unauthorised absence in four school weeks
The legal limit of sixteen hours in four school weeks is counted. The mentor sees the total well before the school has to report it.
This counter already works in the real version.
Exam programme (PTA)
Example · made-up data
Tests, resits and deadlines according to the school’s exam programme.
Teaching time
Example · made-up data
See how many lessons were actually taught, per class and per period.
Privacy
Privacy from
the very first design.
Each role only sees what it needs.
Permissions per role and per action. A subject teacher doesn’t see a care file.
A record of who viewed what.
The access log already exists. The school can always look at it.
Agreements before real data.
No real student data goes into Ludendo until the data processing agreement and the DPIA with the school are in place.
This website uses no cookies, no tracking and loads nothing from other parties. Privacy statement (in Dutch)
For the sector
Switching should be possible.
Away from us, too.
There are few suppliers of school platforms in Dutch secondary education. A new party with a simple, honest approach gives schools more choice. Ludendo builds on the sector’s shared agreements, and the data stays with the school: everything can be exported.
A new supplier
More choice for schools.
Built on the sector’s agreements
Entree login is being built; OSO (transfer between schools) and DUO (the national education agency) are in design.
The data stays with the school
Export everything, whenever you want.
Honestly
How far along we are.
We’re on our way.
Ludendo is still in development. No schools use it yet. This is where we stand.
October 2026
Prototype ready.
A clickable prototype with all roles, on made-up data. The screens on this site come from it.
Now
The real version is being built.
Login, timetable, sick reporting, attendance with the absence counter, import, export and the log are built. Grades, homework, starting lessons and messages are being built. The rest comes after that.
2027
Preparing together.
With pilot schools: agreements, the data processing agreement, the DPIA and setting up the school.
School year 2027–2028
The first pilot.
We’re looking for schools that want to build it with us.
Status of the real version
Built
- Login
- Timetable
- Sick reporting by parents
- Attendance and the absence counter
- Import from CSV
- Timetable from Zermelo not yet tested with a real school
- Export everything
- Access log
Being built
- Grades
- Homework
- Starting lessons and the smartboard
- Messages
- Login via Entree
Later or in design
- Mentor overview with signals
- Notifications on your phone
- Switching schools with OSO in design
- Link with DUO in design
Anything being built, planned for later or in design doesn’t work in the real version yet. We’d rather say so now than later.
Questions
Good questions.
Honest answers.
Can we use Ludendo now?
Not yet. There is a clickable prototype and the real version is being built. We’re looking for schools that want to run a pilot from school year 2027–2028.
Are the screens on this site real?
They’re rebuilt from our prototype, with made-up names and grades. Not everything you see works in the real version yet. What already works is listed under ‘How far along we are’.
What does a pilot ask of our school?
What the pilot looks like, with which department or year group and how much time it takes, hasn’t been decided yet. We agree on that together during the introduction. What is fixed: we start with the agreements (data processing agreement and DPIA), and only after that does any real data go in. And if the pilot stops, the school takes all of its data with it through the export.
What does it cost?
That hasn’t been decided yet. We’ll make agreements together with pilot schools.
How does our data get in?
You import students, parents, classes and teachers from a CSV file. First you see a check, without anything being saved. That already works in the real version. Ludendo reads the timetable from Zermelo, read-only. That link is built, but not yet tested with a real school. Switching with OSO is in design.
Where is the data stored?
With one hosting provider in the European Union. Which one exactly, we’ll set down with the pilot schools in the data processing agreement, before a single piece of real student data goes in. This is about the platform; this website itself is hosted by Cloudflare.
What about security?
Nobody can do anything unless their role allows it: for every action, Ludendo checks whether your role may do it. The data of each school board and each school is kept separate in the database. Every time someone views a student’s data, it goes into the log. Before any real student data goes in, an independent specialist reviews the security. And no real data goes into Ludendo until the data processing agreement and the DPIA with the school are in place.
Can we leave again later?
Yes. All of the school’s data can be exported, whenever you want, in one file (JSON). The access log can also be exported as CSV.
Does it work with Entree, OSO and DUO?
We’re building towards it. Login via Entree is in development; OSO and DUO are in design. So they don’t work yet.
Pilot schools wanted for 2027–2028
Become one of
the first schools.
Want to see how Ludendo would work for your school, or help build it as a pilot school in 2027–2028? Book an introduction. We’ll show you the prototype, tell you honestly what already works, and above all, listen.
Your email goes to Thomas and Geert, the makers of Ludendo.
Parents, students and others in the sector are welcome to get in touch too.