Scheduling and attendance
Sessions are scheduled against the course, and physical attendance is recorded alongside the online kind rather than tracked separately.
Capability
Live sessions that stay connected to the course
Conferencing, whiteboards, and chat run on your own infrastructure and inherit course membership. Nobody joins because they were forwarded a link.
Sessions
Conferencing and recording
Live audio and video run on a self-hosted LiveKit deployment, with recording handled by its own egress service.
Session discussion
Each session carries its own discussion and attachments, so the material stays with the occasion it belongs to.
Whiteboards
A self-hosted Excalidraw workspace, scoped to the course.
- Live collaboration
- Scenes synchronise over Socket.IO with defined behaviour when two people edit the same thing at once.
- Protected persistence
- Scenes are stored under the same protected access rules as other course material, not in a public bucket.
- A local asset boundary
- Whiteboard assets stay inside the installation. The board does not reach out to a third-party service to render what a class drew.
Chat
Chat runs on a Matrix homeserver inside the installation, with Mirket managing sessions and shared state. Attachments are protected rather than public URLs, and behaviour follows the route the user is on, so a course conversation is a course conversation.
Do it, step by step.
The manual covers this as a task, with prerequisites, what finishing looks like, and what to do when it does not work.
Bring Mirket to your facility.
Run it on your own infrastructure or let us host it for you. Both licences ship the same product; the difference is who operates the data plane.