Why we built this
A letter from a first-grade classroom.
Ibuilt Multilinguals because I watched multilingual students nod along to lessons they could not follow. They were not behind. They were not less curious. They just did not have the words yet.
Every year, a handful of kids in my first-grade class would show up speaking a language I did not know — Urdu, Amharic, Haitian Creole. They were bright, they were engaged for the first ten minutes, and then some word would go by and the rest of the lesson would happen without them.
The existing tools did not fit the classroom. Translation apps asked students to type. Pull-out ESOL meant missing the lesson. Full-curriculum translation was expensive, slow, and took the lesson out of the teacher’s hands.
What we needed was something small. A way to say “this word — the one I’m saying right now — here’s what it means, in the language you think in.” And then keep teaching.
Multilinguals is that. Nothing more, nothing less.
— Baeta Moulou · co-founder
What we believe
The teacher is the expert
No student-facing chatbot. The teacher drives what students see. The tool serves the lesson, not the other way around.
Home language is a bridge, not a replacement
Students access the content in the language they think in, then move toward English. This is how the research says it should work.
Children deserve architectural privacy
No student PII. No accounts. No data sale. Compliance by design, not by disclosure.
Seventeen languages, treated equally
Not an English product with translation bolted on. Every script is first-class — layout, typography, audio.