
Omileno
A school’s free hub: teaching, administration, families and staff in one place, with one installation per school.
In progressPilot in preparationWhat it is
Omileno is a school’s hub, free software ( licence), in French and English. It brings together what a school usually manages with separate tools: teaching, administration, families and staff. I am building it for schools that prefer a single tool to a stack of subscriptions, and its pilot is in preparation.
Every feature belongs to the open distribution, with no paid edition: the money comes from hosting and from customisation in each school’s colours. The hub is built on the lower secondary curricula, in all their successive editions, kept in a reference matrix that each installation can activate.
How it works
The core stays small, and features are added as versioned modules, reviewed and then assembled at build time, so nothing is loaded at random at runtime. The screens are those of the hub itself. For the rest, it relies on free services: Keycloak for identity and access rights, OpenCloud and Collabora for files and online office tools, Matrix for end-to-end encrypted messaging, and a mail server.
Each school has its own installation, which holds only one organisation. Releases are signed, and the chain rehearses installation, updating with rollback and restoring a backup. A pupil’s work stays private until it is deliberately published, the host has no automatic access to that work, and sharing with families stays closed until the school opens it.

Why it exists
Omileno comes from my teaching. I had first written a platform for my own pupils and private lessons, then found that a school asks for the same facts under other names: people, groups, homework, assessments, attendance. Two products by the same author for the same things is a duplication I refuse, so the first platform is being absorbed into the hub.
The first school in view is the Edeys school in Le Haillan. A trial installation precedes it on the TousDys association’s cloud, where sign-in goes through the existing directory, and that is where I put each release to the test. Service commitments will be set from the pilot.