Courses & curriculum
Nothing ships until somebody says so
Academics & Content
Video that is yours, wherever it lives
Upload, chapters, captions and signed-URL playback over a storage port that speaks local disk, S3-compatible or Azure Blob.
media · 14 API routes
What it does
Upload and playback
Signed URLs, so a link that leaks stops working.
Chapters and captions
Authored per asset; captions are a first-class record, not a sidecar file.
Three storage drivers
local-disk, s3 (covering MinIO and R2) and azure-blob, chosen by an environment variable.
How it actually works
The port is the point
No feature module imports a cloud SDK. Storage is an interface with three implementations, selected at boot — which makes “move your data” a connection-string change rather than a project. Mail, search, AI and cache have the same shape.
The permission keys it adds
A sample. Each is a real key in the catalogue, described for a school administrator rather than an engineer.
content.media.uploadcontent.media.viewcontent.caption.manage
Who holds it
- Content Author
- Teacher
The shipped role templates that hold it by default. Each is a copy you own and can edit — nothing in the code reads a role's name.
And what it does not
Naming these here is cheaper for both of us than discovering them in week six of a pilot.
What this does not do yet
Naming these is cheaper for both of us than discovering them in week six.
- Transcoding and HLS — the port exists, the worker does not
- DRM
- Automatic transcription
Related
Learning delivery
Built for a bad connection
Start on the free tier. Bring your spreadsheet.
A hundred seats, twenty-five courses and no conversation. If you would rather see it driven by someone who knows it, that takes twenty minutes.
Or open the sandbox (opens in a new tab) and click around first. No form.