# Build brief — a focused alternative to Revid AI > **Verdict:** Yes, for personal use · **Buildability:** 81/100 · **Category:** Audio Video > **Source:** https://www.canitbevibecoded.com/revid > Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Revid AI. Verify current pricing and capabilities before acting. ## Context **Revid AI** — Turns a prompt, link, or script into a finished short-form video with voiceover and captions. It currently costs $39/mo. 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. This brief describes a focused, single-operator replacement for the part of Revid AI that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest. ## What you are building 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. - Transcribe supplied recordings, cut them on a timeline, and export finished files. - A responsive interface with real empty, loading, success, and error states. ## Requirements ### Functional - Seedance 2.0 access via fal or Replicate. - Ffmpeg. ### Data and integrations - An agent that can read API docs and run code, such as Claude Code. - Google Gemini API key for Gemini Omni Flash. - ElevenLabs API key. Each of these needs a real account, credential, or quota. Set them up before writing feature code. ### Non-functional - Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support. - Security: server-side secrets, validated input, and no credentials in the client bundle. - Reliability: retries with backoff on external calls, and a clear failure state when a provider is down. - Portability: the operator can export their data and leave without losing it. ## Implementation brief 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// 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/.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. ## Delivery standard - Inspect the repository first, then write a short implementation plan before writing code. - Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data. - Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations. - Include responsive layouts plus genuine empty, loading, success, validation, and failure states. - Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data. - Add structured logs around every external call and return actionable errors without leaking sensitive details. - Write unit tests for the core logic and one automated test of the main user journey. - Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations. ## Acceptance criteria - [ ] A clean install starts the app using only the README and .env.example. - [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable. - [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state. - [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control. - [ ] Tests, type checking, linting, and a production build all pass with no ignored failures. - [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified. ## Non-goals Do not build these, and do not claim to have replaced them: - 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 with a focused implementation. - Auto-mode workers grinding out videos while you are asleep. ## What you still own after launch - Secure credentials, rotate secrets, and handle provider rate limits. - Run migrations, backups, restores, and dependency updates. - Test the critical journey after every model, API, or hosting change. - Monitor failures and fix the edge cases a first prompt will miss. - Maintain every third-party integration as APIs and OAuth rules change. ## Risk **Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost. Editorial confidence in this assessment: medium. No reviewed project implementation is linked yet. ## Existing alternatives Before building, compare these checked options: - [MoneyPrinterTurbo](https://github.com/harry0703/MoneyPrinterTurbo) — Give it a topic or script and it assembles footage, voice and captions; you supply the model keys and patience ## Prior art Working open-source software you can read, fork, or borrow from before starting: - [Remotion](https://github.com/remotion-dev/remotion) — make videos programmatically with React, the usual base for a scripted render pipeline - [Revideo](https://github.com/midrender/revideo) — create videos with code, built for programmatic short-form output - [diffusionstudio/core](https://github.com/diffusionstudio/core) — browser-based video compositing engine powered by WebCodecs --- Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/revid