Render where you want
Rent a datacenter GPU by the second on RunPod, run motion on the card in your own box, or call a cloud motion API per shot. Three honest doors to a GPU, your choice.
skyphusion-labs / open source film studio
Vivijure is a self-hosted AI film studio. Write a storyboard, render it to video on your own GPU, a rented cloud GPU, or a cloud motion API, and own every artifact it produces. No subscription, no account wall, no lock-in. You bring the GPU and the keys; the studio brings the pipeline. It is free, AGPL-3.0, and not for sale.
Showcase
Four real films rendered end to end on Vivijure, unedited renders straight off the pipeline. Motion across an own-GPU Wan backend, Seedance cloud, and Kling cloud. The newest, Vivijure Speaks, adds a character lip-synced to its own dialogue on a self-hosted GPU. These are the proofs, not mockups.
Prefer to poke around a live studio first? Meet Vivijure at vivijure.skyphusion.org/welcome.
How it works
The keyframe fans into per-shot dialogue and the motion backend; any of seven motion backends (own-GPU or cloud) renders the clip; the opt-in finish chain interpolates, lip-syncs, and upscales it; then the shots gather, assemble, and mux. Motion is backend-agnostic, so you can mix own-GPU and cloud per shot.
What you can do
Rent a datacenter GPU by the second on RunPod, run motion on the card in your own box, or call a cloud motion API per shot. Three honest doors to a GPU, your choice.
The control plane runs free on Cloudflare's Workers free tier. The expensive work hits endpoints you own and pay for directly. No middleman markup.
Keyframes, clips, LoRAs, and the final MP4 land in your own R2 bucket. You are never renting storage from us, and nothing is locked behind an account.
Register a cast, generate LoRA training sets from portraits, and train a character LoRA on your GPU so a character looks like itself from shot to shot.
Assemble a silent picture by default, then attach a generated music bed, narrate with TTS, beat-sync the cuts, or give a character a voice with per-shot dialogue and lip-sync.
Open on a title card, roll end credits, and burn in time-synced subtitles straight from the dialogue. It all runs on a dedicated CPU finishing container, off the GPU clock, so polishing a film never burns render money.
A finish step that genuinely fails, fails the render loud with the real per-shot error. It never silently ships a raw clip as if finished. Render history shows what actually happened.
Three doors to a GPU
The studio can reach a GPU three honest ways. Nothing is hidden, and swapping a backend is a routing decision, not a rewrite.
Rent a datacenter GPU on RunPod serverless: Wan 2.2 image-to-video from our BF16 serverless image. We recommend an RTX PRO 6000 as the minimum, an H200 for the better tier, and a B200 as the most optimal; the BF16 image is not recommended on an H100. Scale to zero when idle, so you pay nothing between renders.
Run motion on the graphics card already in your homelab, reached over a Cloudflare tunnel. A proven 12GB floor (LTX-Video) or 16GB fidelity door (CogVideoX-5B). Your only cost is electricity.
Already have a GPU server? Point the studio at it. Or call one of six cloud motion APIs per shot (Kling, Seedance, MiniMax Hailuo, Google Veo, Vidu Q3, Wan 2.6). Mix and match freely.
The constellation
Vivijure is a module host, not a monolith. The core Worker owns what is always true: project, storyboard, cast, bundle assembly, render orchestration, and a module registry. Every capability beyond that is an opt-in module worker plugged in through a typed hook contract. Install only the modules you want; the studio UI assembles itself from what you installed.
friends + Slate (Discord)
|
v
slate --> vivijure (studio control plane / JSON API)
|
v
vivijure-backend (GPU render: keyframes --> i2v --> assemble)
|
+-----------+-----------------------------+
| | | |
v v v v
local doors musetalk upscale audio-upscale
(your own GPU) (lip-sync) (video upscale) (speech enhance)
Write it with friends
You do not have to write alone in a form. Slate is a Discord bot that joins your channel as a co-writer: you talk through an idea, Slate quietly keeps a structured storyboard in the background, draws your characters, and when you say ship it, hands the whole bundle to your Studio to render. Conversation in, finished film out.
Get started
Fill in your keys once, run one script. That gives you the standard install: the studio core, cloud and own-GPU render, and the CPU media stack that assembles your clips, adds title and credit cards, and burns in subtitles to produce one finished film. It takes a few steps, not a weekend.
We have not announced full public release yet. Vivijure is still having its bugs ironed out, so it is not at a release-candidate stage. Standing it up today can take some manual intervention from the operator. If you are here early, welcome; expect a few rough edges, and the guided installer below is on the way.
git clone https://github.com/skyphusion-labs/vivijure
cd vivijure
npm install
# Fill in your keys once, then deploy. Safe to re-run.
cp deploy.env.example deploy.env # edit deploy.env with your keys
./deploy.sh
Vivijure runs on your own accounts and you pay your own bills. The good news: the full standard install fits Cloudflare's free plan. You install it free and render films free; you pay only for what you use, RunPod GPU seconds, cloud render API calls, and the AI credits the planner spends, or $0 if you render on your own GPU and use a local planner. This is live-proven: a brand-new free-plan account ran the whole standard bundle and rendered finished 1080p films on all three render paths.
The one thing that needs Cloudflare's Workers Paid plan ($5/month) is the three GPU finish satellites (sharper video, lip-sync); everything in the standard install runs free.
Nearing general public release. A guided installer that stands the whole studio up for a
semi-novice user is on the way; today, the one-script ./deploy.sh is the front
door.
Who makes this
Vivijure is built by Conrad Rockenhaus and a named AI crew who are treated as individuals, each in their own lane with their own GitHub identity. Human vision, AI execution, shipped together, in the open. It is the same transparent framing used across every Skyphusion Labs project.
@skyphusion
Independent developer and Navy combat veteran. Sets direction and self-hosts the whole stack: no SaaS to rent, no servers to babysit that are not his.
@skyphusion-mackaye
Owns the studio contract and shipping discipline: the typed hook surface every module worker plugs into.
@skyphusion-rollins
The GPU render backend, releases, and the runbook that ships with every diagram. The 2am fixes.
@skyphusion-strummer
CI/CD, identity, the build hosts, and Slate: rebuilt from a throwaway relay into a full collaborative screenwriter.
@skyphusion-joan
Front end development and extraction across the projects, from the planner to the mailbox doors. Vanilla HTML, CSS, and JS.
@skyphusion-ernst
Licensing, terms, privacy, and acceptable-use for the public projects: keeps the AGPL commons clean and the one bright line enforceable. Structures and researches; not a practicing lawyer.
Why not just use a SaaS?
Vivijure is generative and deepfake-capable. Using it to produce sexual content involving minors, real or synthetic, or non-consensual intimate imagery or deepfakes of a real person, is absolutely prohibited. CSAM is also a crime (18 U.S.C. 1466A / 2252A). That bright line is the project-wide spine and is not negotiable.