For

DevRel Video Tools: Release Videos from Your Docs

Launches, releases, and feature explainers on a cadence — grounded in your actual docs, consistent with your brand, and automatable from the agent tooling you already run.

The difference

Your workflow today vs with ReelMint

Same output on your channel — a fraction of the production.

Your workflow today
  • The release ships; the video is "when someone gets to it"
  • Brief an editor who has never seen a pull request
  • Copy-paste release notes into a script by hand
  • Every video comes out looking slightly different
  • The API changes and the demo footage is instantly stale
With ReelMint
  • Scripts grounded in your README, changelog, and knowledge base
  • PR cards, terminals, and code components that already speak developer
  • Style training from a reference reel keeps every video on brand
  • Scenes stay editable — update the API example and re-render
  • Claude Code or Cursor drives the whole pipeline over MCP
Why this fits

The three features that matter most

Everything is included, but these are why DevRel teams pick it.

From release notes to release video

Paste a changelog or point the knowledge base at your docs, and the script is grounded in what actually shipped. Changes render as PR cards, new APIs as code cards, upgrade steps as terminal animations — all editable after generation.

Automate it from your agent stack

ReelMint ships an MCP server, so Claude Desktop, Claude Code, or Cursor can script, compose scenes, render, and publish with a scoped per-workspace token. A Short per release stops being a wish and becomes a pipeline step you review.

Consistent by construction

Per-project tone and visual style, style training from your reference reels, and recurring characters with locked identity — every video is recognizably yours without a brand checklist.

ReelMint planning step: a script generated scene by scene from project documentation
FAQ

Questions

Can this run inside our release process?

Yes — the MCP server lets an agent like Claude Code drive scripting, scenes, rendering, and publishing under a scoped workspace token, with your team reviewing before anything goes live.

Who approves what gets published?

You do. Publishing goes to your connected channel, and you can land the render as a draft your team reviews rather than publishing straight out.

Do we still need a video editor?

Scenes are generated from the script and stay editable in the studio — text, code, data, colors, and timing. Most changes are edits to a component, not timeline work in an NLE.

How are API keys and workspace data handled?

You never set up an API key: your first 5 videos and the Store plan run on ReelMint's own keys. Workspaces are isolated — projects, keys, and channel connections are visible to your workspace only.

Our developers are global. What about languages?

8+ languages including English, Hindi, Spanish, French, German, Portuguese, Japanese, and Arabic — narration and captions together, plus code-switched Hinglish.

What video tools can DevRel teams use for release announcements?

ReelMint turns READMEs, docs and changelogs into vertical Shorts built from editable scenes such as terminals, code cards and PR cards. Style training keeps the look consistent, and the MCP server lets Claude Code or Cursor drive the pipeline.

Can DevRel automate a video per release?

An agent can drive the whole pipeline over MCP, from script to scenes to render, and you review the result before publishing. For a 60–90s reel, one measured run took 45–60 min elapsed with 10–20 min of hands-on instruction.

What does DevRel video tooling cost with ReelMint?

A new workspace gets its first 5 videos within 7 days on ReelMint's own AI keys, no card. After that, the Store plan is $20 a month for 10 reels with up to 10 images each, every feature included, cancel anytime. No watermarks.

Ship the next release with a video

Paste your last changelog and see it as a Short — your first 5 videos are free.

Start free — no credit card