Draft locally
Experiment with keyframes on your own machine before spending provider credits.
Generate keyframes locally, organize the shot like a director, then send only the winning frame to the cloud. Draft on your machine first; spend only when the shot is ready.
Advanced route. Public downloads are not open yet, and local generation requires capable hardware.
Continuous forward push. Road aligned. Hands steady.
HOLD · NO SPENDExperiment with keyframes on your own machine before spending provider credits.
Build shots around continuity anchors, start/end frames, prompt variants, and selected winners.
Promote the approved frame to cloud image or video only when it is worth animating.
Keep the expensive decision at the end of a tight directing loop.
Explore compositions locally on capable hardware.
Lock continuity, compare frames, and select the anchor.
Turn one motion intent into model-aware prompt variants.
Choose the cloud send, inspect the result, then close the loop.
Local drafting uses your hardware. Cloud hero frames and video use provider services—and only after you choose to send.
Block framing and explore quickly on your own machine, without a provider image charge.
Refine and approve the local frame that carries continuity into motion.
Escalate an approved frame or animate it deliberately. Video is never an automatic spend.
The deeper workflow stays close when you need it.
Keep the approved keyframe as the visual anchor while adapting motion language for Runway, Seedance, Veo, Kling, and Luma workflows.
Place the returned clip beside its keyframe, check continuity, and decide whether to accept, revise, or try another lane.
Break a duration into cinematic beats, then land those beats as editable shots instead of a sealed black box.
Keep framing, characters, props, prompt variants, and selected winners visible as the sequence develops.
There is no public installer today. The notes below describe the current evidence and intended paths—not a compatibility promise.
Cloud lanes use provider services and your own accounts or API keys. Provider charges apply when you choose to send.
Internal .deb and AppImage builds exist. They are not approved for public release and have no documented signing evidence.
No proven release packages are available. Platform support will be stated only after builds and release checks are complete.
Local keyframes rely on an existing ComfyUI setup and a capable GPU. Exact compatibility will be documented before preview approval.
BYOK note: supported cloud lanes require the relevant provider account and key. Local drafting and provider sends remain separate choices.
No public download yet. We'll notify you when the preview is approved and whether your machine is a fit.
One release-readiness note. No fake download button, no surprise installer.