Beta · built and tested · architecture, safety and privacy design verified end-to-end; pending a deployment's own on-site hardware wiring and DPIA sign-off
Research + Education Beta · built & tested

Project Astrid

An AI tutor that teaches you to build games — in Roblox, Unity, Unreal Engine, or Blender. It does not just do the task, it explains the principles as you go, works inside your project through the real creative tools, and runs on the classroom's own hardware. It remembers each learner between sessions and never stores a name. A tutor console gives one human a live, room-wide view of it all.

Runs on your hardwareTeaches, does not doRoblox · Unity · Unreal · Blender68 skill-mapped lessonsPer-student memory, name-blindNo personal data to the cloud
Project Astrid hero

What it is

Each learner works 1:1 with an AI tutor across four real creative-tool tracks — Roblox, Unity, Unreal Engine, and Blender — built to teach the principles as they go, not to do the work for them. A tutor console gives one human oversight of the whole room.

Architecture

Each learner station pairs 1:1 with a local compute node running its own model, speech and 3D generation. A single host is the control plane and the only data store — orchestration, per-learner memory, the tutor console, and the safeguarding layer all live there, and no model inference ever runs on it. Nothing shared can take out the room.

LEARNER PAIR (×N)Station · WindowsBrowser dashboard + loginCreative tool (Roblox · Unity · Unreal · Blender)In-browser voice + talking faceCompute node · LinuxLocal LLM (default brain)Speech-to-text (ASR)Local 3D generationFixed to the station · isolatedHOST · control planeOrchestration + rolesTutor console + messagingSafeguarding guardrailPer-member memory vaultsDeterministic egress gateFrontier gateway (optional)No model inference hereCREATIVE TOOLSRoblox · UnityUnreal · Blender68 skill-mapped lessonsvia MCP · reads free, writes backed upFRONTIER (optional)Pooled seats, off by defaultCode tasks onlysanitised, no personal data
1:1 paired stations · a single host control plane · four creative-tool tracks over MCP · a pooled frontier tier, labelled optional and off by default, reached only for sanitised code tasks.

Four creative-tool tracks

The tutor works inside the real tool a learner is building in, not a simulation of it — Roblox Studio, Unity, Unreal Engine, and Blender, bridged over MCP so its reads are exact and its writes go through the same project the learner sees. Alongside it sits a library of 68 real, skill-mapped lessons across all four tools — drawn from Roblox Creator Hub, Unity Learn, Unreal Online Learning, and Blender Fundamentals — paced by skill and assignable by the tutor to one learner or the whole room.

Roblox Creator HubUnity LearnUnreal Online LearningBlender Fundamentals

Tutor console

The console is a paced-progress cockpit, not a support-ticket queue. One human oversees the whole room from it.

Messaging & content library

A tutor and a learner can message each other directly, and the tutor can push a vetted video, link, lesson, or asset straight into a learner's chat — or broadcast it to the whole room at once, the same tutor-vetted card either way.

FOUR CREATIVE-TOOL TRACKSRoblox · UnityUnreal · Blender68 skill-mapped lessonspaced by skill, tutor-assignedTUTOR CONSOLEpaced-progress cockpitPer-student pace & skill masteryLive “N of M stuck on X”Drill-down + chat-log oversightAsset library + lesson assignmentTwo-way messaging + send-to-chat(every link prescanner-vetted)SAFEGUARDINGViolence · sexual/explicitSelf-harm · hate/extremismwatches content + searchesHUMAN REVIEWERnever resolved by the AIalways routed, every timeBACKUP-BEFORE-WORKEvery project snapshotted before Astrid writesRestore to before — one click, any time
Four creative-tool tracks feed one tutor console. Safeguarding always routes to a human — never resolved by the AI — and every write is snapshotted first, so nothing a learner builds is ever at risk.

Safety & safeguarding

Security & privacy

Privacy is enforced by construction, not by trusting a model. The system is name-blind, and a deterministic gate guarantees only non-personal code context can ever leave the building. The cloud tier itself is labelled optional in the product and is off by default — a centre can run entirely local-only.

Learner requestchat · code · voiceDeterministicrouterby surface, not AI guessEverything else → local model, stays in the buildingEgress allowlistcode + game context onlyname / roster redactionFrontier seatcode helpno personal dataoptional tier, off by defaultcode task
Default is the local model. Only code tasks are eligible for the cloud; the egress allowlist forwards a fixed set of non-personal fields, so personal data cannot be included by accident — and the frontier tier itself is labelled optional, off until a deployment chooses to enable it.

The stack

Local-first and permissively licensed end to end, so operating cost stays near zero and no learner data has to leave the building.

Orchestration

A single host schedules the fleet. Machines dual-boot between a learner role and a compute role, and the host wakes and assigns them per session, so a class of concurrent learners draws on a pool of many machines.

Host orchestratorassigns roles · pairs · sessionsDirectory / policyimaging · lockdown · WOLDual-boot fleetlearner ⇆ compute roleFrontier pool (optional)allocate · queue · meter
The host assigns roles and wakes machines on demand; the fleet flexes between learner and compute duty; the optional frontier pool is allocated and metered centrally when a deployment enables it.

← All projects   View source on GitHub ↗