For developers and dev-rel
Explainer videos for developers
Explain a concept, an API or an architecture in a short narrated video with diagrams that build up on the words. Make it from your docs, or let your agent make it over MCP.
- 500 free credits at sign-up
- Free storyboard review
- 45–180 s, vertical 9:16
- 8 voices, 10 languages
Your link
9:16 · 1080×1920“docs.example.com/guides/rate-limits. Audience: developers. Must show: the token bucket refilling.”
- Length
- 90–120 s
- Look
- Night
- Voice
- George
- Rendering
- 2D · English
Storyboard · 6 scenes
- 0–7 sHook. A wall of requests hits an API box at once and the box flashes red. Title: “Why your API said 429.”
- 7–30 sThe bucket. A bucket of tokens sits in front of the API; every request takes one token to get through.
- 30–55 sRefill. Tokens drip back in at a fixed rate. A short burst passes, then the bucket runs dry and extra requests get a 429 Too Many Requests.
Developers learn from diagrams: a request travelling from client to server, a cache in the middle, a queue soaking up a spike. Developer advocates draw those diagrams all day, in talks, docs and threads. Turning one into a short video usually means hours in a motion tool, so most never leave the whiteboard.
Motiongist writes the narration, plans the scenes and animates the diagram in step with the voice. Set the audience to developers and it skips what an HTTP request is. Set it to beginners and it explains everything with an everyday comparison first.
How it works
From a docs page to a video in the feed
- Step 1
Point it at the source
Link a docs page or a blog post, paste a script, or drop a Markdown file. When you give a source, the script sticks to it.
- Step 2
Say what must be on screen
Notes like “must show: client → CDN edge → origin” or “avoid: vendor names” keep the diagram honest. Mark the key moment that should stick.
- Step 3
Check the storyboard
Review each scene for free: the order of the steps, the labels on the boxes, the terms you want named once.
- Step 4
Ship it, or automate it
Download the MP4 and SRT. Or, from the Studio plan, call the REST API from CI, or ask an agent in Claude, ChatGPT or Cursor to make it over MCP.
Example
How a rate limiter protects an API
What you give: “docs.example.com/guides/rate-limits. Audience: developers. Must show: the token bucket refilling.”
What the video shows, scene by scene
- 0–7 s
Hook. A wall of requests hits an API box at once and the box flashes red. Title: “Why your API said 429.”
- 7–30 s
The bucket. A bucket of tokens sits in front of the API; every request takes one token to get through.
- 30–55 s
Refill. Tokens drip back in at a fixed rate. A short burst passes, then the bucket runs dry and extra requests get a 429 Too Many Requests.
- 55–80 s
The response. A response card highlights the Retry-After header a well-behaved client reads before trying again.
- 80–100 s
Client side. A retry loop with exponential backoff spaces requests out until they fit the refill rate.
- 100–110 s
Takeaway. “Respect the bucket: back off, then retry.”
An illustrative storyboard for this brief (Night look, 2D). Motiongist writes its own scenes from your input, and you can edit them for free before rendering.
A real render, made with Motiongist
How a CDN makes videos load fast
1:10 · Illustrated look · more examples
Why Motiongist
Built for technical explanations
Diagrams that build on the words
Boxes, arrows and flows appear as they are named, so viewers follow a request step by step instead of reading a slide.
An API and an MCP server
From the Studio plan: a REST API with webhooks, plus an MCP server for Claude, ChatGPT and Cursor. Each render needs an approved, signed quote.
Grounded in your docs
Give a link or a Markdown file and the script sticks to it, with a fact review before rendering.
A look for a terminal crowd
Night is dark and technical, Illustrated suits beginner content, or apply your project’s colors and logo.
Your docs, in 10 languages
Narrate the same concept in English, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Turkish and Indonesian, with captions to match.
Easy to drop into docs
Each video gets an embeddable share page, plus post copy for YouTube, TikTok, Instagram and LinkedIn.
Good topics for a short dev video
One mechanism per video works best. If you would explain it with a whiteboard diagram, it fits.
- How a concept works: caching, CDNs, load balancing, DNS, OAuth flows.
- Why an error happens: a 429, a CORS failure, a race condition.
- What changed in a release, and what it means for users of your API.
- Your system’s architecture at a glance, for new contributors.
What it won’t do
It doesn’t record your screen, run your code or replay an editor session. It explains ideas with diagrams, titles and mock-ups. For a hands-on coding walkthrough, a screen recording is still the right format; a short explainer can introduce the idea before it.
Start faster
Templates that fit
Each template is a ready-made brief: an example subject, a target length, a look and notes. Open one and change the subject.
What it costs
One credit balance. A short video is 400 credits, a standard one 700, a long one 1,000, plus 1 credit per 10 narrated characters for the final voice.
Free
$0
500 credits at sign-up
To try it out: a first video, draft voice, discreet watermark.
Solo
$19 / month
3,000 credits / month
To post every week: final voice, clean exports, your brand.
StudioMost popular
$49 / month
30,000 credits / month
To produce at volume: priority rendering, custom looks, API and MCP.
Team
$149 / month
100,000 credits / month
For teams and agencies: 5 seats, 4 renders in parallel, one invoice.
Prices before tax, in US dollars. Yearly billing is 35% cheaper. Failed renders are refunded automatically.
FAQ
Questions, answered
Can my agent create videos from our docs?
Yes, from the Studio plan. Connect the MCP server to Claude, ChatGPT or Cursor: the agent drafts a video from a docs page, gets a quote, and starts the render once the quote is approved. See the MCP docs.
Is there a REST API?
Yes, with webhooks when a video is ready. It follows the same rule as the studio: no approved quote, no render. See the API docs.
Will it get the technical details right?
With a source, the script sticks to it and a fact review runs before rendering. Read the storyboard anyway: a wrong label on a diagram is free to fix there, and costs a 50% revision after the render.
Which audience setting should I pick?
Developers for peers who know the basics, beginners for newcomers and non-technical users, ops for infrastructure people, decision-makers for buyers.
Where can I post the videos?
Download the MP4 and SRT, embed the share page in a blog post, or publish to YouTube, TikTok, Instagram or LinkedIn directly. Publishing costs no credits.
Ready to make your first one?
500 free credits at sign-up. Review the storyboard for free, see the exact price, then render.
Create your video