Loading
About
Every exam season ends the same way: the syllabus in one tab, the lesson in another, a half-watched playlist in a third, and a chat window that has to be re-briefed every single time.
There is more explanation available for any topic than anyone could watch. What is missing is a place that knows which of it matters for you: which unit a topic sits in, how deep your course goes, and what you have already covered.
So we made the syllabus the first thing a space learns. Once it knows the scope, everything else can be arranged around it: cards for the topics, chat scoped per card, videos filtered per card, progress tracked per card.
The result is a space you open in week one and still open the night before the exam.
Principles
A tutor that does not know your syllabus will always teach the wrong amount. Everything in Dock starts from the material you actually have to cover.
A lesson is structured, not linear. A grid of cards keeps that structure visible instead of burying it in chat history.
Notes, explanation and video for a topic belong in the same place. Every switch you avoid is attention you keep.
How you arrange your topics is part of how you understand them. Dock stores the arrangement, it does not reset it.
Where we are
Accounts, then a space per lesson: share the lesson with its syllabus section and its topics come back as cards on the grid.
Per-card chat grounded in your material, plus the video shelf matched to that one topic. Both run on your own model key, which is encrypted before it is stored and never shown back.
Every space asks what it is for (an interview, an exam, or your own words) and how far along you are. Both answers travel into every explanation and every video search, so the same lesson reads differently for a beginner and for someone the night before a final.
Stuck on what a lesson covers? Ask, and five topics come back as suggestions you can take or ignore, either while you create the space or later from the canvas when you find a gap. Ask again for five more.
A card on the space that lays out what to cover and in what order, yours to rewrite. A plan made in week one never survives contact with the term, so this one is meant to be edited rather than followed.
A layout that stays exactly where you dragged it, and revision progress that reflects what you have actually worked through instead of sitting at zero.
Further out: export a space to PDF for the night before, and turn a lesson into a condensed revision sheet you can read in one sitting.
Every line of it is public: the Next.js frontend and the FastAPI backend live in one repository. Read the source on GitHub.
Early access is open. The people using it now shape what ships next.