About Lumaris Studio
We make the video because we built the products first.
Lumaris Studio is led by Marko Živić, a former GitHub Actions Technical Lead and IBM Product Owner. A decade building developer products, now making the video that explains them. The people who cut your video write production code. That is the whole company.
- founded
- 2024 · Zaječar, Serbia
- focus
- Technical video for developer tools
- record
- 200+ videos · 0 syntax errors
From the founder
Two minutes on why this exists.
No script, no studio voice. Just me on why technically wrong video keeps happening, and what we built to stop it. If you are deciding whether to trust a team with your product, start here.
Marko Živić · Founder
How it started
The commit history of a studio built by engineers.
-
init decade-of-production-code
Before the first video, a decade of engineering. I led GitHub Actions and Codespaces, and I was a Product Owner at IBM, shipping enterprise software and running engineering teams. I learned how software actually gets built, not how it gets explained in a demo.
// stack acquired over a decaderole: GitHub Actions Technical Lead · Codespacesrole: IBM Product Owner · enterprise systemsdomain: CI/CD, DevEx, API design, cloud infra -
insight market-failure-identified
I kept watching good developer products get explained badly. Wrong syntax. Commands that would not run. Architecture diagrams that did not match the product. The studios making these videos were not bad at video. They just did not understand the thing they were filming.
editor.knows('cinematography') // trueeditor.knows('storytelling') // trueeditor.knows('how-the-code-runs') // false ← the gap -
decision leave-engineering → build-lumaris
The move was not to become a videographer. It was to build the studio that should already have existed. One where the editors have programming backgrounds, every script is checked by a developer before a frame is cut, and “video editors who write code” describes the team, not the marketing.
-
feature first-client: code-with-antonio
The first creator validated the premise on day one. Brief in. The editor read the codebase. No briefing call. First draft out, zero revision rounds on technical accuracy. Antonio runs a 417K full-stack channel, and every claim in the cut was correct.
client: Code with Antonio · 417Kbriefing_call: not requiredrevisions: 0 syntax_errors: 0 -
scale 200-videos · 0-syntax-errors
Code with Antonio. Thu Vu on AI and data science. Each new channel tested the same premise, and each delivery held the same record. Two hundred plus videos, zero syntax errors, intro retention holding between 95 and 99 percent.
-
current onboarding 2 new clients
Ten clients at a time. Two seats open. The studio built to fix a structural problem is now the proof that the fix holds at scale.
status: active · capacity availableseats: 2 open// the record stands.
The problem
Technical video is structurally broken.
It is not that production companies are bad at their jobs. The job was defined wrong. Great cinematography and real technical understanding get treated as separate skills. They are not separate. They are inseparable.
When the editor does not understand your product, the revision cycle turns into a tutoring session. Your engineers explain what a Dockerfile is. Your PM runs feedback rounds that should never have existed. Your calendar slips. And the developers watching the final cut can tell something is off, even when they cannot say what.
How we are built
Hire the engineers first. Teach them video second.
We did not hire videographers and train them in technical products. We hired people with programming backgrounds and trained them in production. The order matters. Someone who has shipped a CI pipeline reads a technical brief differently than someone who just learned the words.
-
Read the code before the brief
Every project starts with the docs and, where we can get it, the repo. The editor understands the product at the code level before the first line of script exists.
-
Dev validation on every draft
An in-house engineer checks every command, API reference, and diagram against current docs before you see the cut. Errors get caught in production, not in your inbox.
-
EditWise holds the cadence
The production system I built runs the standard and the timeline across every client, so quality never depends on who happens to be on the edit.
Every video clears a Dev Validation Receipt like this before it reaches you. The thing no competitor documents, made inspectable.
The record
The numbers, with the industry beside them.
- 95 to 99% intro retention Most technical video has lost about half its audience by this point.
- 13.4% sponsored click-through Against a 2 to 6 percent industry norm.
- 0 syntax errors shipped Across 200+ videos, every command checked line by line.
- 1 to 2 revision rounds Where the industry typically runs four to six.
- ~5 days to first draft Premium studios run weeks to months.
- 200+ technical videos delivered Produced to the same standard as paid work.
Retention and click-through measured on the creator channels we cut, Code with Antonio and Thu Vu, labeled as such and never framed as developer-tools client results.
The team
Editors who write code. Literally.
The distinction sounds small. In practice it is the difference between an editor who asks what a container registry is and one who already knows, and flags that your Dockerfile example will not run in the environment you described.
-
01 / 02
Marko Živić
Founder
Marko spent a decade writing production code before picking up a camera, and that decade is the product. Every system here, the validation layer, the briefing, the hiring bar, came from watching technical video fail from inside the companies it was meant to serve. He reads the codebase on every Foundation engagement and owns technical validation across all plans.
- Led teams across CI/CD, DevEx, enterprise API, and cloud infrastructure
- Built the in-house validation that has held zero syntax errors across 200+ videos
- Owns the accuracy standard, because he verified it was safe to stand behind
-
02 / 02
Ljubica Živić
Co-Founder and Creative Director
Ljubica owns the creative output: the motion language, the way a diagram animates, the pacing of a demo against a code walkthrough. The standard is simple. A technically wrong visual is a bad visual, however polished it looks. She reads a brief for accuracy before she reads it for aesthetics.
- Leads creative direction across every client account
- Built the motion-design system from scratch, no stock templates
- Co-owns the visual-accuracy standard, so every diagram is correct and clear
// the studio Lumaris Studio · Zaječar, Serbia · since 2024 · 200+ videos · 0 syntax errors
Work with us
Want a team that already understands your product?
Ten retainer clients at a time. Two seats open. We reply the same day.
- we reply the same day
- ten clients at a time
- two seats open