Vibecode Rendemo
track this build5 steps, step by step0%KINDA · weekend project
The mechanics of a demo builder are not mysterious: capture or import clips, trim them, add zooms, captions and a background, then render an MP4. An agent can wire that up locally with ffmpeg and a canvas timeline in a weekend, and for a solo founder shipping one launch video that is probably enough. What it will not hand you is the taste baked into the presets: the easing on the auto-zoom, the mouse smoothing, the default padding that makes a raw screen recording look intentional. You also lose hosted playback, analytics on who watched, and the ability to re-render at 4K without your laptop fans screaming. Fine if you make demos occasionally, annoying if demos are your job.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Rendemo. 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 ===== # Rendemo indie build ## Goal Build the smallest trustworthy replacement for the core Rendemo workflow for one developer or a tiny team. ## Scope Import screen recordings, arrange them on a timeline with auto-zoom, captions and a padded background, then render an MP4 locally with ffmpeg. ## 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: - Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding - Hosted playback with a share link, embeds and view analytics - Fast cloud rendering instead of pinning your own CPU for ten minutes - Template library and brand kits, so every demo looks like part of a set - Someone else keeping up with codec and browser capture quirks If those capabilities are essential, use Rendemo 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 a local-only product demo video editor. No accounts, no cloud, no telemetry. Stack, no substitutions: - Vite + React + TypeScript - Tailwind for UI - Zustand for editor state - fluent-ffmpeg driving a locally installed ffmpeg binary, via a small Express server on port 8787 - Projects stored as JSON files in ./projects, media in ./media Features in scope: 1. Import: drag and drop .mp4 / .mov / .webm files, plus an in-app recorder using navigator.mediaDevices.getDisplayMedia that saves a .webm to ./media. 2. Timeline: single video track, drag to reorder clips, trim handles for in/out points, delete clip. 3. Keyframed zoom: user clicks a point on the preview at a given time and sets a zoom level; interpolate between zoom keyframes with an ease-in-out cubic curve. Default zoom is 1.6x over 700ms. 4. Framing: solid or linear-gradient background, configurable padding, corner radius and drop shadow on the video frame. Presets: 16:9, 1:1, 9:16. 5. Captions: text overlays with start/end time, position, font size, one clean sans font. 6. Preview: canvas-based scrubbing preview at reduced resolution, driven by requestAnimationFrame. 7. Export: POST the project JSON to the server, which builds an ffmpeg filter_complex chain and writes ./exports/NAME.mp4 at 1080p, 30fps, h264, yuv420p. Stream progress back over SSE and show a progress bar. Out of scope, do not build: - multi-track audio, music library, transitions beyond hard cuts - hosted sharing, embeds, view analytics, collaboration - auto zoom detection from cursor movement - any login or hosted storage Requirements: - Fail loudly at startup if ffmpeg is not on PATH, with the install command in the error. - No secrets needed, but include .env.example with PORT and MEDIA_DIR anyway. - README with setup, a worked example project, and a short note on expected render times. - Type-check clean, no any. ## Required capabilities - Node 20+ - ffmpeg installed locally - a browser that supports getDisplayMedia if you want in-app capture - patience for render times on long clips ## 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 Rendemo. 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 ===== # Rendemo indie build ## Goal Build the smallest trustworthy replacement for the core Rendemo workflow for one developer or a tiny team. ## Scope Import screen recordings, arrange them on a timeline with auto-zoom, captions and a padded background, then render an MP4 locally with ffmpeg. ## 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: - Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding - Hosted playback with a share link, embeds and view analytics - Fast cloud rendering instead of pinning your own CPU for ten minutes - Template library and brand kits, so every demo looks like part of a set - Someone else keeping up with codec and browser capture quirks If those capabilities are essential, use Rendemo 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 a local-only product demo video editor. No accounts, no cloud, no telemetry. Stack, no substitutions: - Vite + React + TypeScript - Tailwind for UI - Zustand for editor state - fluent-ffmpeg driving a locally installed ffmpeg binary, via a small Express server on port 8787 - Projects stored as JSON files in ./projects, media in ./media Features in scope: 1. Import: drag and drop .mp4 / .mov / .webm files, plus an in-app recorder using navigator.mediaDevices.getDisplayMedia that saves a .webm to ./media. 2. Timeline: single video track, drag to reorder clips, trim handles for in/out points, delete clip. 3. Keyframed zoom: user clicks a point on the preview at a given time and sets a zoom level; interpolate between zoom keyframes with an ease-in-out cubic curve. Default zoom is 1.6x over 700ms. 4. Framing: solid or linear-gradient background, configurable padding, corner radius and drop shadow on the video frame. Presets: 16:9, 1:1, 9:16. 5. Captions: text overlays with start/end time, position, font size, one clean sans font. 6. Preview: canvas-based scrubbing preview at reduced resolution, driven by requestAnimationFrame. 7. Export: POST the project JSON to the server, which builds an ffmpeg filter_complex chain and writes ./exports/NAME.mp4 at 1080p, 30fps, h264, yuv420p. Stream progress back over SSE and show a progress bar. Out of scope, do not build: - multi-track audio, music library, transitions beyond hard cuts - hosted sharing, embeds, view analytics, collaboration - auto zoom detection from cursor movement - any login or hosted storage Requirements: - Fail loudly at startup if ffmpeg is not on PATH, with the install command in the error. - No secrets needed, but include .env.example with PORT and MEDIA_DIR anyway. - README with setup, a worked example project, and a short note on expected render times. - Type-check clean, no any. ## Required capabilities - Node 20+ - ffmpeg installed locally - a browser that supports getDisplayMedia if you want in-app capture - patience for render times on long clips ## 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 Rendemo. 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 ===== # Rendemo product brief ## Problem The mechanics of a demo builder are not mysterious: capture or import clips, trim them, add zooms, captions and a background, then render an MP4. An agent can wire that up locally with ffmpeg and a canvas timeline in a weekend, and for a solo founder shipping one launch video that is probably enough. What it will not hand you is the taste baked into the presets: the easing on the auto-zoom, the mouse smoothing, the default padding that makes a raw screen recording look intentional. You also lose hosted playback, analytics on who watched, and the ability to re-render at 4K without your laptop fans screaming. Fine if you make demos occasionally, annoying if demos are your job. ## Product outcome Import screen recordings, arrange them on a timeline with auto-zoom, captions and a padded background, then render an MP4 locally with ffmpeg. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20+ - ffmpeg installed locally - a browser that supports getDisplayMedia if you want in-app capture - patience for render times on long clips ## Explicit non-goals for v1 - Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding - Hosted playback with a share link, embeds and view analytics - Fast cloud rendering instead of pinning your own CPU for ten minutes - Template library and brand kits, so every demo looks like part of a set - Someone else keeping up with codec and browser capture quirks ## 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 a local-only product demo video editor. No accounts, no cloud, no telemetry. Stack, no substitutions: - Vite + React + TypeScript - Tailwind for UI - Zustand for editor state - fluent-ffmpeg driving a locally installed ffmpeg binary, via a small Express server on port 8787 - Projects stored as JSON files in ./projects, media in ./media Features in scope: 1. Import: drag and drop .mp4 / .mov / .webm files, plus an in-app recorder using navigator.mediaDevices.getDisplayMedia that saves a .webm to ./media. 2. Timeline: single video track, drag to reorder clips, trim handles for in/out points, delete clip. 3. Keyframed zoom: user clicks a point on the preview at a given time and sets a zoom level; interpolate between zoom keyframes with an ease-in-out cubic curve. Default zoom is 1.6x over 700ms. 4. Framing: solid or linear-gradient background, configurable padding, corner radius and drop shadow on the video frame. Presets: 16:9, 1:1, 9:16. 5. Captions: text overlays with start/end time, position, font size, one clean sans font. 6. Preview: canvas-based scrubbing preview at reduced resolution, driven by requestAnimationFrame. 7. Export: POST the project JSON to the server, which builds an ffmpeg filter_complex chain and writes ./exports/NAME.mp4 at 1080p, 30fps, h264, yuv420p. Stream progress back over SSE and show a progress bar. Out of scope, do not build: - multi-track audio, music library, transitions beyond hard cuts - hosted sharing, embeds, view analytics, collaboration - auto zoom detection from cursor movement - any login or hosted storage Requirements: - Fail loudly at startup if ffmpeg is not on PATH, with the install command in the error. - No secrets needed, but include .env.example with PORT and MEDIA_DIR anyway. - README with setup, a worked example project, and a short note on expected render times. - Type-check clean, no any. ## 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 Rendemo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Rendemo indie build ## Goal Build the smallest trustworthy replacement for the core Rendemo workflow for one developer or a tiny team. ## Scope Import screen recordings, arrange them on a timeline with auto-zoom, captions and a padded background, then render an MP4 locally with ffmpeg. ## 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: - Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding - Hosted playback with a share link, embeds and view analytics - Fast cloud rendering instead of pinning your own CPU for ten minutes - Template library and brand kits, so every demo looks like part of a set - Someone else keeping up with codec and browser capture quirks If those capabilities are essential, use Rendemo 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 a local-only product demo video editor. No accounts, no cloud, no telemetry. Stack, no substitutions: - Vite + React + TypeScript - Tailwind for UI - Zustand for editor state - fluent-ffmpeg driving a locally installed ffmpeg binary, via a small Express server on port 8787 - Projects stored as JSON files in ./projects, media in ./media Features in scope: 1. Import: drag and drop .mp4 / .mov / .webm files, plus an in-app recorder using navigator.mediaDevices.getDisplayMedia that saves a .webm to ./media. 2. Timeline: single video track, drag to reorder clips, trim handles for in/out points, delete clip. 3. Keyframed zoom: user clicks a point on the preview at a given time and sets a zoom level; interpolate between zoom keyframes with an ease-in-out cubic curve. Default zoom is 1.6x over 700ms. 4. Framing: solid or linear-gradient background, configurable padding, corner radius and drop shadow on the video frame. Presets: 16:9, 1:1, 9:16. 5. Captions: text overlays with start/end time, position, font size, one clean sans font. 6. Preview: canvas-based scrubbing preview at reduced resolution, driven by requestAnimationFrame. 7. Export: POST the project JSON to the server, which builds an ffmpeg filter_complex chain and writes ./exports/NAME.mp4 at 1080p, 30fps, h264, yuv420p. Stream progress back over SSE and show a progress bar. Out of scope, do not build: - multi-track audio, music library, transitions beyond hard cuts - hosted sharing, embeds, view analytics, collaboration - auto zoom detection from cursor movement - any login or hosted storage Requirements: - Fail loudly at startup if ffmpeg is not on PATH, with the install command in the error. - No secrets needed, but include .env.example with PORT and MEDIA_DIR anyway. - README with setup, a worked example project, and a short note on expected render times. - Type-check clean, no any. ## Required capabilities - Node 20+ - ffmpeg installed locally - a browser that supports getDisplayMedia if you want in-app capture - patience for render times on long clips ## 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
# Rendemo product brief ## Problem The mechanics of a demo builder are not mysterious: capture or import clips, trim them, add zooms, captions and a background, then render an MP4. An agent can wire that up locally with ffmpeg and a canvas timeline in a weekend, and for a solo founder shipping one launch video that is probably enough. What it will not hand you is the taste baked into the presets: the easing on the auto-zoom, the mouse smoothing, the default padding that makes a raw screen recording look intentional. You also lose hosted playback, analytics on who watched, and the ability to re-render at 4K without your laptop fans screaming. Fine if you make demos occasionally, annoying if demos are your job. ## Product outcome Import screen recordings, arrange them on a timeline with auto-zoom, captions and a padded background, then render an MP4 locally with ffmpeg. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20+ - ffmpeg installed locally - a browser that supports getDisplayMedia if you want in-app capture - patience for render times on long clips ## Explicit non-goals for v1 - Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding - Hosted playback with a share link, embeds and view analytics - Fast cloud rendering instead of pinning your own CPU for ten minutes - Template library and brand kits, so every demo looks like part of a set - Someone else keeping up with codec and browser capture quirks ## 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 a local-only product demo video editor. No accounts, no cloud, no telemetry. Stack, no substitutions: - Vite + React + TypeScript - Tailwind for UI - Zustand for editor state - fluent-ffmpeg driving a locally installed ffmpeg binary, via a small Express server on port 8787 - Projects stored as JSON files in ./projects, media in ./media Features in scope: 1. Import: drag and drop .mp4 / .mov / .webm files, plus an in-app recorder using navigator.mediaDevices.getDisplayMedia that saves a .webm to ./media. 2. Timeline: single video track, drag to reorder clips, trim handles for in/out points, delete clip. 3. Keyframed zoom: user clicks a point on the preview at a given time and sets a zoom level; interpolate between zoom keyframes with an ease-in-out cubic curve. Default zoom is 1.6x over 700ms. 4. Framing: solid or linear-gradient background, configurable padding, corner radius and drop shadow on the video frame. Presets: 16:9, 1:1, 9:16. 5. Captions: text overlays with start/end time, position, font size, one clean sans font. 6. Preview: canvas-based scrubbing preview at reduced resolution, driven by requestAnimationFrame. 7. Export: POST the project JSON to the server, which builds an ffmpeg filter_complex chain and writes ./exports/NAME.mp4 at 1080p, 30fps, h264, yuv420p. Stream progress back over SSE and show a progress bar. Out of scope, do not build: - multi-track audio, music library, transitions beyond hard cuts - hosted sharing, embeds, view analytics, collaboration - auto zoom detection from cursor movement - any login or hosted storage Requirements: - Fail loudly at startup if ffmpeg is not on PATH, with the install command in the error. - No secrets needed, but include .env.example with PORT and MEDIA_DIR anyway. - README with setup, a worked example project, and a short note on expected render times. - Type-check clean, no any. ## 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 Rendemo 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 · this prompt is generated from the build plan · improve it via PR
Because the output is public-facing. A demo video is marketing material, and nobody wants to ship a launch clip that looks slightly off because the zoom eased wrong. Paying a small monthly fee to get presets that were tuned by someone who does this all day is a rational trade against an afternoon of tweaking cubic-bezier values, especially when the alternative also means babysitting your own renders.
xPreset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding
xHosted playback with a share link, embeds and view analytics
xFast cloud rendering instead of pinning your own CPU for ten minutes
xTemplate library and brand kits, so every demo looks like part of a set
xSomeone else keeping up with codec and browser capture quirks
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Rendemo ($39/mo) with one prompt"
Vibecode Rendemo
Kinda. The core of Rendemo is buildable in a weekend with the prompt on this page, but there are real gaps: Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding, Hosted playback with a share link, embeds and view analytics. Read the honest list above before committing.
How much does Rendemo cost?
Rendemo costs about $39/month (Pro, checked 2026-08-18), which is $468 per year.
What do I lose by replacing Rendemo?
Honestly: Preset motion design that actually looks good without fiddling: easing, mouse smoothing, sensible padding; Hosted playback with a share link, embeds and view analytics; Fast cloud rendering instead of pinning your own CPU for ten minutes; Template library and brand kits, so every demo looks like part of a set; Someone else keeping up with codec and browser capture quirks. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Rendemo?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.