Vibecode Vyravid
track this build5 steps, step by step0%KINDA · weekend project
A local version of the core workflow is buildable: project dashboard, script-to-scenes generation, voiceover, media generation, timeline assembly, and local ffmpeg rendering. The hard parts are not the CRUD shell but the media edge cases, provider integrations, long-running render jobs, and the editor polish that makes the timeline pleasant instead of fragile.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Vyravid. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Vyravid indie build ## Goal Build the smallest trustworthy replacement for the core Vyravid workflow for one developer or a tiny team. ## Scope Create a local project, generate or paste a script, generate voiceover, split the script into scenes, create visual prompts/assets, arrange a timeline, apply simple effects, and render the final video locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - someone else's servers & support - provider-specific voice/image/video integration details - timeline rendering polish - custom voice and character workflows If those capabilities are essential, use FFmpeg instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a local AI-assisted video generator to replace Vyravid. Requirements: - Node + Express + better-sqlite3, server-rendered pages with a little vanilla JS. App data in SQLite, generated media on the local filesystem served by the backend. All provider keys in .env. - A dashboard showing project count, recent renders, and drafts. - A project editor with script, scenes, media, voice, captions, and timeline tabs. - Let me paste a script, split it into editable scenes, and generate a visual prompt per scene with the Anthropic API. - Voiceover through one configured TTS provider (key in .env), plus manual audio upload as the no-key fallback. - A simple timeline: scene duration, background image/video, caption text, voice track, music bed, and transition choice. - Render MP4 locally with ffmpeg: captions burned in, audio synced, still-image scenes with Ken Burns movement, and simple crossfade transitions. - Show render progress, success, failure, retry, and a download link per finished MP4. Never overwrite a previous render. - No accounts, no telemetry; everything stays on my machine except the API calls. - Out of scope: publishing to social platforms, teams, templates, and hosted rendering. - README: setup, the .env keys, where media lives on disk, and a note that video generation APIs are metered, so estimate cost per render. ## Required capabilities - AI provider API keys - local filesystem storage - ffmpeg ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Vyravid. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Vyravid indie build ## Goal Build the smallest trustworthy replacement for the core Vyravid workflow for one developer or a tiny team. ## Scope Create a local project, generate or paste a script, generate voiceover, split the script into scenes, create visual prompts/assets, arrange a timeline, apply simple effects, and render the final video locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - someone else's servers & support - provider-specific voice/image/video integration details - timeline rendering polish - custom voice and character workflows If those capabilities are essential, use FFmpeg instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a local AI-assisted video generator to replace Vyravid. Requirements: - Node + Express + better-sqlite3, server-rendered pages with a little vanilla JS. App data in SQLite, generated media on the local filesystem served by the backend. All provider keys in .env. - A dashboard showing project count, recent renders, and drafts. - A project editor with script, scenes, media, voice, captions, and timeline tabs. - Let me paste a script, split it into editable scenes, and generate a visual prompt per scene with the Anthropic API. - Voiceover through one configured TTS provider (key in .env), plus manual audio upload as the no-key fallback. - A simple timeline: scene duration, background image/video, caption text, voice track, music bed, and transition choice. - Render MP4 locally with ffmpeg: captions burned in, audio synced, still-image scenes with Ken Burns movement, and simple crossfade transitions. - Show render progress, success, failure, retry, and a download link per finished MP4. Never overwrite a previous render. - No accounts, no telemetry; everything stays on my machine except the API calls. - Out of scope: publishing to social platforms, teams, templates, and hosted rendering. - README: setup, the .env keys, where media lives on disk, and a note that video generation APIs are metered, so estimate cost per render. ## Required capabilities - AI provider API keys - local filesystem storage - ffmpeg ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Vyravid. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Vyravid product brief ## Problem A local version of the core workflow is buildable: project dashboard, script-to-scenes generation, voiceover, media generation, timeline assembly, and local ffmpeg rendering. The hard parts are not the CRUD shell but the media edge cases, provider integrations, long-running render jobs, and the editor polish that makes the timeline pleasant instead of fragile. ## Product outcome Create a local project, generate or paste a script, generate voiceover, split the script into scenes, create visual prompts/assets, arrange a timeline, apply simple effects, and render the final video locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - AI provider API keys - local filesystem storage - ffmpeg ## Explicit non-goals for v1 - someone else's servers & support - provider-specific voice/image/video integration details - timeline rendering polish - custom voice and character workflows ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a local AI-assisted video generator to replace Vyravid. Requirements: - Node + Express + better-sqlite3, server-rendered pages with a little vanilla JS. App data in SQLite, generated media on the local filesystem served by the backend. All provider keys in .env. - A dashboard showing project count, recent renders, and drafts. - A project editor with script, scenes, media, voice, captions, and timeline tabs. - Let me paste a script, split it into editable scenes, and generate a visual prompt per scene with the Anthropic API. - Voiceover through one configured TTS provider (key in .env), plus manual audio upload as the no-key fallback. - A simple timeline: scene duration, background image/video, caption text, voice track, music bed, and transition choice. - Render MP4 locally with ffmpeg: captions burned in, audio synced, still-image scenes with Ken Burns movement, and simple crossfade transitions. - Show render progress, success, failure, retry, and a download link per finished MP4. Never overwrite a previous render. - No accounts, no telemetry; everything stays on my machine except the API calls. - Out of scope: publishing to social platforms, teams, templates, and hosted rendering. - README: setup, the .env keys, where media lives on disk, and a note that video generation APIs are metered, so estimate cost per render. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Vyravid capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Vyravid indie build ## Goal Build the smallest trustworthy replacement for the core Vyravid workflow for one developer or a tiny team. ## Scope Create a local project, generate or paste a script, generate voiceover, split the script into scenes, create visual prompts/assets, arrange a timeline, apply simple effects, and render the final video locally. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - someone else's servers & support - provider-specific voice/image/video integration details - timeline rendering polish - custom voice and character workflows If those capabilities are essential, use FFmpeg instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a local AI-assisted video generator to replace Vyravid. Requirements: - Node + Express + better-sqlite3, server-rendered pages with a little vanilla JS. App data in SQLite, generated media on the local filesystem served by the backend. All provider keys in .env. - A dashboard showing project count, recent renders, and drafts. - A project editor with script, scenes, media, voice, captions, and timeline tabs. - Let me paste a script, split it into editable scenes, and generate a visual prompt per scene with the Anthropic API. - Voiceover through one configured TTS provider (key in .env), plus manual audio upload as the no-key fallback. - A simple timeline: scene duration, background image/video, caption text, voice track, music bed, and transition choice. - Render MP4 locally with ffmpeg: captions burned in, audio synced, still-image scenes with Ken Burns movement, and simple crossfade transitions. - Show render progress, success, failure, retry, and a download link per finished MP4. Never overwrite a previous render. - No accounts, no telemetry; everything stays on my machine except the API calls. - Out of scope: publishing to social platforms, teams, templates, and hosted rendering. - README: setup, the .env keys, where media lives on disk, and a note that video generation APIs are metered, so estimate cost per render. ## Required capabilities - AI provider API keys - local filesystem storage - ffmpeg ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Vyravid product brief ## Problem A local version of the core workflow is buildable: project dashboard, script-to-scenes generation, voiceover, media generation, timeline assembly, and local ffmpeg rendering. The hard parts are not the CRUD shell but the media edge cases, provider integrations, long-running render jobs, and the editor polish that makes the timeline pleasant instead of fragile. ## Product outcome Create a local project, generate or paste a script, generate voiceover, split the script into scenes, create visual prompts/assets, arrange a timeline, apply simple effects, and render the final video locally. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - AI provider API keys - local filesystem storage - ffmpeg ## Explicit non-goals for v1 - someone else's servers & support - provider-specific voice/image/video integration details - timeline rendering polish - custom voice and character workflows ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a local AI-assisted video generator to replace Vyravid. Requirements: - Node + Express + better-sqlite3, server-rendered pages with a little vanilla JS. App data in SQLite, generated media on the local filesystem served by the backend. All provider keys in .env. - A dashboard showing project count, recent renders, and drafts. - A project editor with script, scenes, media, voice, captions, and timeline tabs. - Let me paste a script, split it into editable scenes, and generate a visual prompt per scene with the Anthropic API. - Voiceover through one configured TTS provider (key in .env), plus manual audio upload as the no-key fallback. - A simple timeline: scene duration, background image/video, caption text, voice track, music bed, and transition choice. - Render MP4 locally with ffmpeg: captions burned in, audio synced, still-image scenes with Ken Burns movement, and simple crossfade transitions. - Show render progress, success, failure, retry, and a download link per finished MP4. Never overwrite a previous render. - No accounts, no telemetry; everything stays on my machine except the API calls. - Out of scope: publishing to social platforms, teams, templates, and hosted rendering. - README: setup, the .env keys, where media lives on disk, and a note that video generation APIs are metered, so estimate cost per render. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Vyravid capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay for hosted services, managed storage, fewer setup steps, reliable provider orchestration, templates, collaboration, asset libraries, support, and polished timeline UX. A local rebuild can replace the workflow for technical users, but hosted products still win on convenience and reliability.
xsomeone else's servers & support
xprovider-specific voice/image/video integration details
xtimeline rendering polish
xcustom voice and character workflows
share on X ↗"I just replaced Vyravid ($19.99/mo) with one prompt"
Don't feel like building it? These folks already made it free.
MMoneyPrinterTurboTurns a topic or script into a narrated, captioned stock-footage short; tasteful restraint is not bundled.open source↗no votes, no pay-to-list · just what's real
Vyravid pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0 | $0 | Unlimited projects; the official pricing page does not expose a numeric monthly scene-generation allowance. |
| starter | $19.99 | — | Up to 1,000 scene generations/month, advertised as about 2.5 hours of generated video; all aspect ratios. |
| growth | $39.99 | — | Growth plan is sold for scaled production, but its numeric monthly generation quota is not exposed in the official parsed page. |
free tierUnlimited projects; the official page does not publish the numeric free generation allowance.
billingmonthly only; no annual plan is displayed
verified 2026-08-14 · source ↗
Vibecode Vyravid
Kinda. The core of Vyravid is buildable in a weekend with the prompt on this page, but there are real gaps: someone else's servers & support, provider-specific voice/image/video integration details. Read the honest list above before committing.
How much does Vyravid cost?
Vyravid costs about $19.99/month (Starter, checked 2026-08-14), which is $239.88 per year.
What do I lose by replacing Vyravid?
Honestly: someone else's servers & support; provider-specific voice/image/video integration details; timeline rendering polish; custom voice and character workflows. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Vyravid?
Yes: MoneyPrinterTurbo (Turns a topic or script into a narrated, captioned stock-footage short; tasteful restraint is not bundled.) The prompt is for when you want it exactly your way.