[verdict][curated prompt][source: revid.ai]
Can I vibecode Revid AI?
// one session, and a personal version you can actually use
Revid does not own a model or a render farm. The shots come from Seedance 2.0 and Gemini Omni Flash, the voice comes from ElevenLabs, and the stitch is ffmpeg. All three are public APIs with public docs, so the honest replacement is an agent skill that reads those docs and calls them: a project folder per video, a style file holding the look, aspect ratio, pacing, captions, and voice, and a cache so a re-render does not repay for unchanged shots. This is why it lands on yes where the older video tools on this site land on kinda. Those wrap encoding and editing infrastructure you would have to rebuild. Revid wraps three endpoints. What you are really paying for is that someone already wired them together and pointed them at a publishing button.
confidence: medium
what it is: Turns a prompt, link, or script into a finished short-form video with voiceover and captions
Buildability index · an editorial game
- Price 99 $/month weight: plus 3
- Time one sitting weight: plus 3
- Category audio and video no weight
- Moat execution quality · integrations weight: minus 2
- Confidence medium weight: zero
- What you lose 5 items weight: minus 2
- Site revid.ai (si apre in una nuova scheda) no weight
The maths works, but not by much: look at what you lose before you start.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Write a script, define a reusable style file, generate each shot through Seedance 2.0 or Gemini Omni Flash, narrate with ElevenLabs, burn captions from the word timings, and stitch to a single vertical mp4 with ffmpeg.
what you need
- an agent that can read API docs and run code, such as Claude Code
- Seedance 2.0 access via fal or Replicate
- Google Gemini API key for Gemini Omni Flash
- ElevenLabs API key
- ffmpeg
The rare wrapper thin enough to admit it: three documented endpoints and an ffmpeg stitch. The build is a skill plus a style file, not an app.
The prompt
One session with a coding agent and your version runs.
Build me a Claude Code skill that makes short-form videos to replace Revid AI. Requirements:
- The deliverable is a skill folder, not a web app: SKILL.md plus a Node + TypeScript CLI
run with tsx, no build step. ffmpeg does every stitch, mux, and caption burn-in.
- Projects live in ./projects/<slug>/ with brief.md, script.md, shots.json, and a render/
folder, so everything about one video sits in one directory I can delete.
- Styles are files, not prompts I retype: styles/<name>.json holds the look, aspect ratio,
pacing, caption font and position, voice id, and a shot-prompt preamble. A project names
one style and inherits all of it.
- Generate each shot with Seedance 2.0 when it needs native audio or lip sync, or Gemini
Omni Flash when I want to revise it conversationally without re-prompting · the choice
is per shot in shots.json. Keys in .env.
- Narrate with ElevenLabs where a shot has voiceover rather than native dialogue, and burn
captions from the returned word timings, styled by the style file.
- Cache every clip by a hash of its prompt plus style, so re-rendering a project never
pays twice for a shot that did not change.
- SKILL.md must tell the agent to read the live API docs before writing any call:
replicate.com/bytedance/seedance-2.0, ai.google.dev/gemini-api/docs/video, and
elevenlabs.io/docs. These models ship fast, so never write a request shape from memory.
- No accounts, no telemetry, everything on my machine except the three model APIs.
Secrets in .env with a committed .env.example.
- Out of scope: publishing to TikTok, Instagram, or YouTube, and any stock or viral-clip
library. Do not build a web UI, the interface is the skill and the CLI.
- README: the .env keys, how to install ffmpeg, and a worked cost estimate for a 30 second
video at current per-second model prices, so I know what a render costs before I run it.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- the 3M+ viral video library to remix, which is a licensing problem and not a coding one
- one-click publishing to TikTok, Instagram, and YouTube
- AI avatars, face swaps, and the 100+ prebuilt tools around the core generator
- one predictable bill instead of three metered APIs you can overspend on in an afternoon
- auto-mode workers grinding out videos while you are asleep
Why people still pay
They pay because the assembly is the product. Revid keeps up with whichever video model is currently best, absorbs the breakage when an API changes shape, and turns a finished render into a posted video without leaving the tab. A credit balance is also easier to reason about than three metered APIs, and for anyone who does not want to think about ffmpeg flags or per-second model pricing, that alone is worth the subscription.
moat: Execution quality Integrations what a moat is
the wiring and the publish button, not the models
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (2) — and why
- OpenMontage (si apre in una nuova scheda) — Impressive engine, but the non-builder desktop app is still private alpha; today it expects an AI coding assistant.
- YumCut (si apre in una nuova scheda) — Source-available under a noncommercial licence, while the usable hosted workflow is credit-metered; neither story qualifies.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Remotion (opens in a new tab) — make videos programmatically with React, the usual base for a scripted render pipeline
- Revideo (opens in a new tab) — create videos with code, built for programmatic short-form output
- diffusionstudio/core (opens in a new tab) — browser-based video compositing engine powered by WebCodecs
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
