Kino: a one-box studio for open video models
Tools like Higgsfield and Runway hide great models behind credits; ComfyUI exposes them as graphs only experts can drive. Kino puts 2026's best open image and video models behind one text box, on GPUs you rent by the second, and adds an Ad Studio that writes, checks and edits short video ads.
The problem
The open models caught up in 2026: MiniMax H3 makes video with native sound, Qwen Image 2.1 sets legible Chinese and English text, Z-Image-Turbo is photoreal in eight steps. Using them still means wiring ComfyUI graphs, finding the right model files and renting a GPU.
HerbalBath, the brand I co-founded, needs a steady stream of short Mandarin video ads for a 55+ audience, and every one has to get past Meta's and TikTok's health-ad review. Kino is built for both jobs: an easy studio, and an ad line on top of it.
One box, many models
Six tools (image, video, edit, cut out, talking photo, enhance) each offer a couple of apps. An app is an official ComfyUI template plus the handful of knobs a person should ever touch: a start frame, a camera move, a look, a sound, a length.
One preset feeds three places so they never drift apart. A camera move is a phrase for the video models, a CSS animation for its picker card, and an exact ffmpeg move for the free instant mode. Prompts are translated into each model's dialect, such as H3's shot lists with picture references and an audio line.
Workflows are generated, not hand-written
A script reads every core node definition out of ComfyUI's Python source without importing torch: 647 nodes, including dynamic option trees. A converter then turns the editor's workflow format into the API format a GPU runs, handling subgraphs, promoted widgets, primitives and bypassed nodes, and validates every graph before a second of GPU time is billed.
The same build lists every model file each workflow loads, which drives a downloader that fetches only what your chosen apps need. Bring-your-own works the same way: drop a workflow from Civitai or OpenArt and Kino finds its prompt, inputs, size and seed and turns it into a one-box app.
The Ad Studio
Pick a brand, a platform, a language and up to three angles. Claude writes storyboards against a strict JSON schema from the brand profile and the product photo; without a key, templates built only from the brand's approved wording do it.
Product shots animate the real product photo; generated scenes never show the product, so a model can't invent a different bottle. The editor cuts shots to length, burns in large captions inside each platform's safe zone, breaks Chinese lines without splitting a price, composes an end card from the product cut-out, adds a music bed and normalises loudness to -14 LUFS.
- Every script is checked before anything is made: banned words in both languages, effect claims that aren't approved word for word, Meta's personal-attributes policy, before-and-after, superlatives and medical settings.
- Blocking issues need an explicit “make it anyway”: the checker advises, the brand owner decides.
- The same shots re-cut for another platform in one click; the player shades where each app's buttons and captions sit.
Backends that fail in plain language
Demo mode needs no GPU and still makes real files, so the whole studio can be tried and tested first. On a ComfyUI server Kino chooses its own prompt id, listens on the WebSocket for step-by-step progress and falls back to polling. On RunPod Serverless it sends inputs inline and explains cold starts while it waits.
A missing model file comes back as the file's name and the command that fetches it, not a stack trace. Settings tests the connection and lists which apps have all their models.
Limits, stated honestly
- The GPU paths are tested against faithful fakes of ComfyUI and RunPod; a first paid run is the next step.
- Model licences vary and some restrict commercial use; each must be checked before running ads.
- Serverless takes 10 MB of inputs per job, so long video jobs belong on a pod.
- The checker reads words, not pixels: a product label's own claims still need a human eye.
The product call underneath
Keep the parts that must be right deterministic (validation, compliance, editing, file handling) and use models where they are strong: writing and pixels. Show one box by default, keep every result inspectable and remixable, and make the expensive step, the GPU, the last thing to plug in.
