The problem, before.
Education platforms fail in quiet ways — a lecture that buffers, a login that loops, a quiz that loses a student’s answers. Sivi Academy was briefed to be unremarkable in exactly those places, and remarkable elsewhere: curation, pedagogy, pace.
Before
Off-the-shelf LMS tools either dictate a UX the institute doesn't want, or they can't hold mid-class bandwidth drops. A student on 3G shouldn't get a different lesson from a student on fibre — but most platforms act like they do.
After
A bespoke LMS where video transcodes on upload into adaptive bitrates, quizzes check-point every answer, and instructor analytics show real completion, not vanity opens. The architecture, not the marketing copy, is the pedagogy.
“His approach to our assessment platform was refreshingly grounded. No jargon, no over-engineering. Just clean solutions that our team could actually maintain.”
System shape.
Running an edtech or assessment platform?
Video delivery, quiz resumability, cohort analytics — these are the edtech differentiators that don't come out of an off-the-shelf LMS. 30-minute call for a read on your stack.
Content delivery — where edtech lives or dies.
Video is the product. Every lesson is transcoded on upload into adaptive bitrates, chunked into HLS segments, served from a CDN. A student on 3G gets the same pedagogy as a student on fibre; the platform just rebalances quality around them.
Theory of strong design.
In edtech, the architecture is the pedagogy. A platform that drops a student is a platform that interrupts learning.
The design disciplines were resumability (every action is check-pointed: a student who closes a laptop mid-quiz returns to the same question), observability(instructors see real completion, not vanity metrics), and offline-gentleness(content metadata is small and cached; media is streamed but resumable).
How it was built.
Build timeline
- Pedagogy mapWeek 1
Course unit, lesson, quiz, progress model — designed with the institute before any code.
- Core servicesWeek 2–4
Course, lesson, progress, quiz, assessment — each with explicit resumability guarantees.
- Media pipelineWeek 4–6
Upload, transcode, HLS packaging, CDN distribution. Adaptive bitrate from day one.
- Student + instructor UXWeek 6–8
Next.js front-ends. Analytics for real completion, not vanity.
- Hardening + launchWeek 8–10
Load tests for live cohorts, observability dashboards, production rollout.
Outcome.
A live edtech platform with course management, authentication and content delivery — quietly correct in the places students need it to be.
Building a course platform or LMS?
From small cohorts to public courses at scale, the engineering differences are subtle but decisive. Book a 30-minute call and we'll map yours.