Videowiki
A collaborative video wikipedia for learners and educators — with a media pipeline that recovers from failure instead of stranding content.
What they needed — in their own words
“Educators create video explanations, others improve them, and learners always see the best current version. Think wikipedia, but the edits are video segments.”
The system they run on today
- Collaborative video creation and segment-level editing
- Version history with rollback on every article
- Moderation and review workflow for community edits
- A media pipeline that self-recovers from failed renders
Arrived, assessed, hardened
Every Neolen engagement follows the same path: an honest assessment of what's actually there, then the hardening work that makes it a system. Here is how it played out on this one.
What arrived
A genuinely novel product — video edited like text — sitting on a processing pipeline where a failed render mid-job stranded an article between versions, with no way back except a developer poking at the database.
What the assessment found
The assessment identified long-running media jobs as the reliability core: renders failed a small but steady percentage of the time, every failure needed manual repair, and version history couldn't be trusted after one.
What we hardened and shipped
We made every processing job resumable and idempotent — a crashed render restarts from its last completed segment — and made version pointers transactional, so an article never references a half-processed version.
What the client runs on today
Videowiki's community edits video with the confidence of editing text: versions stay coherent, rollbacks always work, and failed renders recover without an operator ever noticing.
Added to the playbook
Resumable, idempotent media jobs became a verified module we reuse in every media-heavy engagement.
Hit a wall with something you've built?
The audit is fixed-fee and standalone — a plain-language report of what's actually wrong, ranked by risk, yours whether or not you continue.