Not one big app. A small family that works together.

Aevum Foundry AI isn't building a single do-everything assistant. It's a small family of AI tools that share one design language, one set of values, and one promise: your data never leaves the building, and nothing you enter is sent to us or used to train anything.

Five tools, five jobs

There are five, and each has a specific job rather than trying to be everything at once. A teaching assistant, for the parts of teaching that take over a teacher's evenings. A school operations tool, for running a school, the work that has nothing to do with teaching. A tutoring environment, for the learning that happens between teacher, parent and pupil outside the classroom. A working environment for a business of one, for the legal, financial, customer and admin work a solo founder juggles. And a multimedia pipeline, generating audio, image and video to support the rest.

Why a family, and not one model

A tool built for a specific job, running where the data already lives, beats a general chatbot that has to send everything away to be useful. Each Aevum tool does one thing well, and the sensitive parts of the work stay put.

What they share

Four things, in every tool. Local-first: your data stays in the building, and nothing you enter comes to us. Accessible by design: built for AAC, Makaton and SEND users first, and everyone else too. Built by a teacher: twenty years in classrooms shape every decision. British, on purpose: designed in the UK, trained on UK national infrastructure, accountable to UK law.

Everything is in development. When each piece is ready, you'll get one email with the link. No countdowns, no weekly nudges.