Generate a structured scene plan, not an uneditable video. Build the studio in Lovable and send approved compositions to an external Remotion renderer.
Remotion represents video as React compositions. Its official Agent Skills teach coding agents how to work in those projects; they are not a built-in Lovable video generator. This guide combines a Lovable brief editor with a controlled rendering service. Start with one 9:16 template for product tips: a hook, three scenes and a final call to action. Change the text or timing without regenerating every shot.
- Lovable studio: brief, scene editor and preview
- Tables: video_jobs, scenes, assets, render_attempts
- External Remotion composition and rendering worker
- Signed asset URLs, authenticated callbacks and spending cap
Offer a fixed-format video package to one niche. Price only after measuring rendering, voice and asset costs; check Remotion licensing for your use case. A template prototype is not a production service.
Scope-dependent: template prototype first
- Create a brief form with audience, offer, tone, language and one action for the viewer. Save the brief before model calls.
- Use a strict scene schema: scene_id, duration_frames, narration, caption, asset_id and transition. Reject unknown asset IDs and invalid durations.
- Implement one trusted Remotion template outside Lovable. Pass validated props to it; never execute arbitrary code returned by the model.
- Build a scene editor and preview. Require approval of the text, rights to assets and render estimate before queueing.
- Call the external renderer from a server function. Store its job ID, keep keys in secrets and verify callbacks before updating status.
- Reuse the same request ID on retry. Show queued, rendering, failed and ready states, and let users retry only a failed render.
- Export an MP4 and thumbnail to private storage with expiring download URLs. Keep public publishing a separate manual step.
- Test overflowing captions, missing media, duplicate callbacks and interrupted rendering before accepting customer jobs.
Build a Lovable video studio, not a native rendering engine. Save briefs and generate strictly validated scene JSON for a single trusted 9:16 Remotion template. Add scene text and timing editing, asset ownership checks, preview, cost estimate and explicit render approval. Use a server function to call an external authenticated rendering worker; keep keys server-side. Never execute model-generated code. Track queued/rendering/failed/ready states, authenticate callbacks and deduplicate retries by request ID. Store MP4 and thumbnails privately with expiring links. No automatic social publishing. Include tests for long captions, missing assets, duplicate callbacks and cancelled jobs.