Can Reel Farm be vibe coded?
Generates faceless TikTok slideshow posts in bulk from a topic, captioned and auto-posted.
The pipeline here is not a secret: an LLM writes a short script, a TTS API reads it, stock or generated clips get stitched behind it, and word-level timings drive burned-in captions. ffmpeg does the heavy lifting and an agent can wire the whole chain in a focused implementation, including a queue that renders fifty variations overnight. Where it stops being fun is everything after the render: scheduled posting to TikTok, Instagram and YouTube means real API access, app review, tokens that expire, and platform rules that change without warning. You will also spend more time than you expect on the boring parts, safe-area layout for captions, loudness normalization, and clips that do not visually repeat every third video. Build it if you want control over the script and the look, pay if the value you actually want is the post button.
Jump to the build brief ↓Legacy-calibrated assessment
Checked Aug 2026
What you pay today, before any DIY hosting
low editorial confidence
Tracked separately from the pricing check
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- A local CLI that takes a topic, writes a short script, synthesizes a voiceover, stitches stock clips with word-timed burned-in captions, and renders a vertical MP4 batch.
- Assemble clips, captions, and renders around a scripted, bounded pipeline.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- Scheduled auto-posting to TikTok, Instagram Reels and YouTube Shorts, which is the part that needs approved platform apps
- Hosted rendering, so long batches tie up your own machine
- Curated templates and caption styles that already look native to each platform
- Any built-in sense of what is performing, analytics loops and hook variants
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Build, switch, or keep paying
Narrower, with trade-offs
A local CLI that takes a topic, writes a short script, synthesizes a voiceover, stitches stock clips with word-timed burned-in captions, and renders a vertical MP4 batch.
Use the build brief ↓No checked option yet
Compare the prior art below or build only the workflow you need.
$95/mo
Because a faceless content operation is not one video, it is two hundred, and the friction that kills it is scheduling and upload, not generation. Getting write access to the major short-form platforms is a bureaucratic slog that nobody wants to do twice, and a hosted tool that already holds those tokens is worth a subscription to people running this as a volume game. There is also the honest fact that the default output of a DIY pipeline looks like a DIY pipeline for the first week, until you fix the caption placement, the loudness, and the clip repetition. If you are making a handful of videos with a specific look you care about, build it. If you are farming, pay.
Visit Reel Farm ↗Why people still pay
Because a faceless content operation is not one video, it is two hundred, and the friction that kills it is scheduling and upload, not generation. Getting write access to the major short-form platforms is a bureaucratic slog that nobody wants to do twice, and a hosted tool that already holds those tokens is worth a subscription to people running this as a volume game. There is also the honest fact that the default output of a DIY pipeline looks like a DIY pipeline for the first week, until you fix the caption placement, the loudness, and the clip repetition. If you are making a handful of videos with a specific look you care about, build it. If you are farming, pay.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Reel Farm
Context
Reel Farm — Generates faceless TikTok slideshow posts in bulk from a topic, captioned and auto-posted. It currently costs $95/mo.
The pipeline here is not a secret: an LLM writes a short script, a TTS API reads it, stock or generated clips get stitched behind it, and word-level timings drive burned-in captions. ffmpeg does the heavy lifting and an agent can wire the whole chain in a focused implementation, including a queue that renders fifty variations overnight. Where it stops being fun is everything after the render: scheduled posting to TikTok, Instagram and YouTube means real API access, app review, tokens that expire, and platform rules that change without warning. You will also spend more time than you expect on the boring parts, safe-area layout for captions, loudness normalization, and clips that do not visually repeat every third video. Build it if you want control over the script and the look, pay if the value you actually want is the post button.
This brief describes a focused, single-operator replacement for the part of Reel Farm 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
A local CLI that takes a topic, writes a short script, synthesizes a voiceover, stitches stock clips with word-timed burned-in captions, and renders a vertical MP4 batch.
Assemble clips, captions, and renders around a scripted, bounded pipeline.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Ffmpeg and ffprobe installed locally.
Disk space and patience for render queues.
Data and integrations
An LLM API key for scripting.
A TTS API key, or a local TTS model.
A stock footage API key, or your own clip library.
Whisper.cpp or a transcription API for word-level caption timings.
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 a local command-line tool that mass-produces vertical faceless short-form videos. No web UI, no accounts, no telemetry, no cloud storage.
Stack: TypeScript on Node 20, run with tsx. Use commander for the CLI, zod for config validation, and fluent-ffmpeg shelling out to a locally installed ffmpeg. SQLite via better-sqlite3 for the job queue and render history. No frontend framework, no Docker.
Secrets in .env, loaded with dotenv: OPENAI_API_KEY, ELEVENLABS_API_KEY, PEXELS_API_KEY. Fail loudly on startup if a key needed by the chosen command is missing.
Commands:
1. reelfarm script --topic "..." --count 5 : call an LLM to produce N short scripts as JSON, each with a hook line, 3 to 5 body beats, and a closing line, target 25 to 40 seconds when spoken. Store each as a pending job row.
2. reelfarm voice --job-id X : send the script to ElevenLabs TTS, save MP3 to media/voice, and normalize loudness to -14 LUFS with the ffmpeg loudnorm filter in two passes.
3. reelfarm captions --job-id X : transcribe the rendered voiceover with whisper.cpp if a local binary is configured, otherwise the OpenAI transcription API with word timestamps, and write an ASS subtitle file with 2 to 4 words per screen, centered in the middle third, thick outline, no more than 90 percent of frame width.
4. reelfarm clips --job-id X : pull vertical stock clips from Pexels matched to keywords extracted from each beat, cache downloads in media/clips, and never reuse the same clip twice within one batch.
5. reelfarm render --job-id X : with ffmpeg, scale and center-crop clips to 1080x1920, cut between them on beat boundaries, overlay the ASS captions, mix voiceover over an optional background track at -22 dB, and write out/{job-id}.mp4 with faststart, H.264, yuv420p, 30 fps.
6. reelfarm batch --topic "..." --count 10 : run the whole chain end to end, serially, resumable, skipping steps whose output already exists on disk.
Explicitly out of scope: posting or scheduling to any social platform, analytics, AI video generation models, multi-user anything. Print the output path and let the human upload.
Write a config.example.json with caption style, voice id, target duration, and clip source. Include a README with the ffmpeg install line, the .env template, and one working batch example. Add a smoke test that renders a 5 second clip from a bundled sample audio file and a solid-color background so the pipeline can be verified without spending API credits.
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:
Scheduled auto-posting to TikTok, Instagram Reels and YouTube Shorts, which is the part that needs approved platform apps.
Hosted rendering, so long batches tie up your own machine.
Curated templates and caption styles that already look native to each platform.
Any built-in sense of what is performing, analytics loops and hook variants.
Someone else absorbing model and stock-footage cost changes.
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: low. No reviewed project implementation is linked yet.
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/reel-farm
You still own the product
- 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.
Projects built from this idea
No reviewed implementation has been linked for Reel Farm yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of Reel Farm?Submit the project as evidence for this report.
Before you start
Can Reel Farm be vibe coded?
Partly, if you narrow it. The pipeline here is not a secret: an LLM writes a short script, a TTS API reads it, stock or generated clips get stitched behind it, and word-level timings drive burned-in captions. ffmpeg does the heavy lifting and an agent can wire the whole chain in a focused implementation, including a queue that renders fifty variations overnight. Where it stops being fun is everything after the render: scheduled posting to TikTok, Instagram and YouTube means real API access, app review, tokens that expire, and platform rules that change without warning. You will also spend more time than you expect on the boring parts, safe-area layout for captions, loudness normalization, and clips that do not visually repeat every third video. Build it if you want control over the script and the look, pay if the value you actually want is the post button.
What can an AI coding agent reproduce from Reel Farm?
A local CLI that takes a topic, writes a short script, synthesizes a voiceover, stitches stock clips with word-timed burned-in captions, and renders a vertical MP4 batch. Assemble clips, captions, and renders around a scripted, bounded pipeline. A responsive interface with real empty, loading, success, and error states.
What will a DIY Reel Farm replacement still be missing?
Scheduled auto-posting to TikTok, Instagram Reels and YouTube Shorts, which is the part that needs approved platform apps; Hosted rendering, so long batches tie up your own machine; Curated templates and caption styles that already look native to each platform; Any built-in sense of what is performing, analytics loops and hook variants; Connectors, OAuth flows, and vendor API changes require constant upkeep.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Reel Farm alternative?
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.