Real design control
Not a theme picker. Blocks share their design system with the learner runtime, so the canvas and the finished lesson are the same column, the same type, the same spacing. What you arrange is what ships.
Course authoring · private beta
A visual canvas with real design control. What you deliver is a plain SCORM package you own: no account, no call back to us. Editing is live; publishing is a click, not a rebuild.
Not a theme picker. Blocks share their design system with the learner runtime, so the canvas and the finished lesson are the same column, the same type, the same spacing. What you arrange is what ships.
Authoring is live and collaborative, but delivery is a file you own. Change one block in a twenty-minute course and publish again in a click. The package already in your LMS keeps working until you choose to replace it. No module gets rebuilt because a screenshot went stale.
The package runs in Moodle, Cornerstone or any SCORM 1.2/2004 player with no network call to indivii. We grepped the exported bundle to be sure. No proprietary player, no hosting requirement, no “contact us to get your content out”.
Two authors can be in the same lesson at the same time, and an agent can be in it with them. Everyone edits the same document. Nobody checks anything out.
An avatar stack shows who is here. The block a colleague has focus in carries their name and colour, and it reaches you in under a second.
Edits merge field by field, not whole blocks. One author rewrites a question while another adds an option, and both changes land in both browsers. That case is a test, not a hope.
Your undo stack only walks back your own typing. Undoing your last sentence never removes a colleague's work.
Every update is persisted as a CRDT log with periodic snapshots, so a laptop that sleeps or loses wifi rejoins and replays into the same document.
indivii ships an MCP server, indivii-authoring. Point Claude Code, or any MCP
client, at a course with an API key and it can create courses, author lessons, add and reorder
blocks, apply a theme, validate and export. It is not a side door.
The block catalogue is derived from the schema on every call, so the agent cannot propose a block type we do not render. There is no hand-maintained list to drift.
Lesson and block edits take dryRun: the agent shows the resulting state and the
validator's verdict, writes nothing, and commits by re-issuing the identical call.
Tenant checks, row-level security, the role gate and schema validation sit inside the procedures it calls. An agent reaches what a signed-in author reaches, and nothing more.
Agent edits enter the lesson's shared document, so someone with it open watches them arrive. Every write is recorded in the audit log.
{
"mcpServers": {
"indivii": {
"command": "pnpm",
"args": ["--filter", "@indivii/mcp-server", "start"],
"env": { "INDIVII_API_URL": "http://localhost:3002",
"INDIVII_API_TOKEN": "ixk_…" }
}
}
}
indivii is in private beta. We’re working with a small number of instructional designers and L&D teams before opening the doors.