Can I vibecode BlitzReels?
price $29/moyou'd save $348/yrbuild time closest consolation build: a weekend; credible replacement: long-term engineeringcategory audio-videoreplaced by 0 people
NOT REALLY
MOATexecution polishscale infra
Turns recordings into clips with a full NLE, API, CLI, and agent integrations
The Build Prompt
copy it and go buildready to paste · 2,235 chars
Build the closest honest personal substitute for BlitzReels in an empty repository. Use exactly Node.js 22, TypeScript, React, Remotion, SQLite, FFmpeg, and the OpenAI API. Run as a single-user local web app with one documented command. The core loop is import one user-owned long video, transcribe it, rank five clip candidates, edit one, and export 9:16 MP4. Preserve the original file and store projects, transcripts, candidates, and edits in SQLite. Use ffprobe for duration and stream metadata before accepting a file. Extract audio with FFmpeg and transcribe it with word timestamps. Ask a text model for five 30 to 90 second candidates with exact boundaries, titles, hooks, and reasons. Reject overlapping or out-of-range candidates and show the model output as suggestions, never facts. Let the user adjust in and out points, edit caption text, and preview the vertical composition. Use a static center crop with a manual horizontal offset; do not claim subject tracking. Render burned captions from verified word timings with one readable style. Export through Remotion to a new file and never overwrite source media. Show import, probing, transcription, analysis, preview, rendering, success, and recoverable failure states. Persist job state so an interrupted transcription or render can be retried safely. Put the OpenAI key in .env, ship .env.example, and never log secrets or transcript contents. Add safe filenames, upload size limits, input validation, and explicit local data deletion. Write focused tests for time-range validation, candidate overlap, caption grouping, and project persistence. Add one end-to-end smoke test using a tiny generated video fixture. Create a README with setup, FFmpeg installation, architecture, data location, costs, backup, and limitations. Deliberately exclude smart reframing, B-roll generation, voice isolation, silence cleanup, and a complete multitrack NLE. Deliberately exclude the public API, CLI, agent integrations, accounts, teams, cloud rendering, share pages, and social publishing. Do not call this a BlitzReels clone; label it a narrow local clip finder and exporter. Run the tests and a real sample render before finishing, then report the exact commands and output path.
What you lose
- ✕reliable ingestion and recovery for large or malformed recordings
- ✕production-tuned clip selection and timestamp alignment
- ✕subject-aware speaker and screen reframing
- ✕complete NLE, caption styles, paid templates, and keyframed timeline editing
- ✕public API, CLI, agent integrations, cloud rendering, retries, and share workflows
Prior art / alternatives
Why it still works
media pipeline, editor and render parity, and production reliability