Get This Tool
Screenshots 5
Vivijure
Pricing
- Model
- Free
- Free Tier
- Cloudflare Workers free tier limits apply
Summary
Most AI video pipelines hand you a subscription wall the moment you try to attach your own GPU or swap out a model mid-project — Vivijure Studio exists precisely to remove that wall.
Vivijure is a self-hosted module host for AI film production, built on a thin Cloudflare Workers core that runs on the free tier and routes tasks to whatever GPU backend you wire up — your own box, RunPod, or a cloud motion API. The typed hook contract between modules is what keeps the pipeline from becoming a tangle of bash scripts: each step — storyboard rendering, TTS narration, lip-sync, music bed — is a discrete worker you attach or replace without touching the rest. The AGPL-3.0 license means the source is auditable and forkable, but it also means any hosted derivative you ship has to stay open. The repo shows 31 open issues and 8 open pull requests against 278 commits — active, but not mature.
Bottom line: Vivijure earns its place in a solo filmmaker's or indie studio's GPU-backed pipeline where avoiding vendor lock-in is non-negotiable — but teams expecting production-hardened reliability on a deadline will be integrating around open issues before they ship.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Pros
Sign in to edit- Runs on Cloudflare Workers free tier as the coordination core, so the pipeline host itself carries no infrastructure cost — you pay only for the GPU time your modules actually consume.
- Backend-agnostic GPU attachment (RunPod, personal hardware, cloud motion API), which means a cost spike from one provider does not strand your project — you redirect the worker and render continues.
- Typed hook contract between module workers, so replacing a lip-sync model or swapping a TTS engine is a single-worker change rather than a full pipeline rewrite.
- AGPL-3.0 license with full self-hosting, which means every rendered artifact belongs to you and there is no account wall between your storyboard and your output.
- API available alongside self-hosting, so integrating Vivijure into a larger automated production pipeline — CI rendering, batch export — does not require bolting on a separate trigger layer.
Cons
Sign in to edit- The open issue count (31) against current commits signals that core pipeline stages have known breakage points. A team trying to run a storyboard-to-locked-picture workflow end-to-end will spend non-trivial time triaging before the pipeline closes cleanly.
- No managed fallback exists when a GPU backend drops mid-render. If RunPod throttles or your local box goes offline, the module worker fails and there is no queuing or retry layer documented in the repo — teams running overnight batch jobs add their own retry logic or accept partial renders.
- The AGPL-3.0 license is a hard stop for any studio that needs to embed Vivijure inside a proprietary commercial product without open-sourcing that product. Those teams evaluate a permissively licensed or commercially licensed alternative the moment legal reviews the dependency.
About
- Platforms
- Cloudflare Workers
- API Available
- Yes
- Self-Hosted
- Yes
- Last Updated
- 2026-06-23T09:01:26.662Z
Best For
Who it's for
- Independent filmmakers using custom GPU setups
- Self-hosted AI video workflows without vendor lock-in
- Modular extension of film production pipelines
What it does well
- End-to-end AI film rendering on personal or cloud GPUs
- Storyboard-to-video pipeline assembly
- Adding generated music beds and TTS narration to locked picture
- Lip-synced character dialogue on self-hosted hardware
Integrations
Add notes, reviews, and benchmarks so the next visitor gets a clearer picture.
Compare Vivijure
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeFrequently Asked Questions
- Is Vivijure free?
- Yes — Vivijure is fully free to use. There is no paid tier.
- Is Vivijure open source?
- Yes. Vivijure is open source.
- Does Vivijure have an API?
- Yes. Vivijure exposes a developer API. See the official documentation at https://github.com/skyphusion-labs/vivijure for details.
- Can I self-host Vivijure?
- Yes. Vivijure supports self-hosting on your own infrastructure.
- What platforms does Vivijure support?
- Vivijure is available on: Cloudflare Workers.
Curated lists that include this category
Vivijure Studio is a pipeline host for AI film production: you write a storyboard, attach your GPU backend, and the tool coordinates rendering, narration, lip-sync, and music assembly through a chain of module workers. The core is a Cloudflare Worker — free-tier compatible — that acts as a typed relay between discrete module workers, each responsible for one stage of the film pipeline. You supply the GPU access (via RunPod, your own hardware, or a cloud motion API) and the API keys; Vivijure supplies the routing contract that keeps those stages from coupling to each other.
The architectural differentiator is the typed hook contract. Rather than a monolithic canvas or a locked vendor pipeline, each production stage — storyboard-to-video rendering, TTS narration, lip-sync dialogue, generated music beds — is an opt-in module worker. Swapping out a model or replacing a stage means replacing one worker, not refactoring the whole project. That modularity is what makes it genuinely backend-agnostic rather than just claiming to be.
Vivijure fits independent filmmakers and small teams who already operate their own GPU infrastructure and want a structured way to compose AI film tools without handing ownership of their artifacts to a SaaS vendor. The AGPL-3.0 license enforces that: every artifact stays yours, and any hosted fork stays open. Where it breaks is at the maturity line — 31 open issues against a repo that has not yet published a stable release means you are building on moving ground. Teams with a locked picture and a delivery date will hit rough edges that a paid platform has already smoothed.