[verdict][curated prompt][source: blitzreels.com]
Can I vibecode BlitzReels?
// the value is the network, the data or the infrastructure
A toy clip finder is a one-session build. A credible BlitzReels replacement is not: the product combines reliable long-video ingestion, timestamp-accurate AI selection, smart reframing, a complete nonlinear editor, browser preview and export parity, public API and CLI contracts, agent integrations, storage, and render orchestration. Its founder reports that the production system took a year even with prior Remotion experience and paid templates.
confidence: high
what it is: Turns recordings into clips with a full NLE, API, CLI, and agent integrations
Buildability index · an editorial game
- Price 29 $/month weight: plus 3
- Time closest consolation build: a weekend; credible replacement: long-term engineering weight: minus 1
- Category audio and video no weight
- Moat execution quality · infrastructure scale weight: minus 3
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site blitzreels.com (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Import one long video, transcribe it, rank clip candidates, let the user adjust boundaries and captions, then export a 9:16 MP4.
what you need
- Node.js 22
- FFmpeg and ffprobe
- OpenAI API key in .env
- local disk space for source and rendered media
Founder-submitted boundary case: the demo is vibecodeable; the dependable media product took one year despite prior Remotion experience and paid templates.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
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.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
- 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
Why people still pay
People pay for the dependable path from an arbitrary long recording to editable, on-brand clips, whether they work in the full NLE or automate through the API, CLI, and agent integrations. The recurring value is avoiding codec failures, lost jobs, weak clip boundaries, bad crops, caption drift, preview and export mismatches, and the operational work behind storage and rendering.
moat: Execution quality Infrastructure scale what a moat is
media pipeline, editor and render parity, and production reliability
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- auto-editor (opens in a new tab) — Open-source command-line video and audio editor for automatic cuts.
- Kdenlive (opens in a new tab) — Mature open-source nonlinear video editor.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
