Hunyuan 1.5 when the file cannot leave the machine
Open cinematic motion under Tencent's community licence. Self-host when the brief forbids a hosted API.
HunyuanVideo 1.5 is Tencent's open cinematic-motion model, released with weights and code, under the Tencent Hunyuan Community License — not Apache 2.0. Self-host it when the brief forbids a hosted API. Most Versely users should not self-host.
Versely is a hosted catalog. Prompts, stills and plates go to providers. That is the product. The without pages route around missing inputs — no camera, no face, no product sample. They cannot route around a rule that says the plate must never leave the box. When that rule is real, you are off this catalog on purpose. Hunyuan 1.5 is one of the weights you can run locally for that constraint. It is not a Versely row, and pretending it is one would be a lie about where your file goes.
The constraint, stated plainly
"The file cannot leave the machine" means the still, the reference, the prompt if it contains client material, and the output stay on hardware you control. No hosted inference. No "the vendor says they delete it after." No Comfy install that still syncs the output folder to a consumer cloud drive.
That constraint is rare, and it is expensive, and it is not the same sentence as "we would rather not think about credits." Credits are a bill. Off-box is a legal or security requirement: unreleased product photography, a face you do not have rights to send to a US or Chinese API, a classified-adjacent workplace, a client MSA that names subprocessors and does not name this one.
If the MSA does not actually say that, you do not have this constraint. You have a feeling. Feelings are how teams stand up a GPU for a problem a DPA would have closed. Hosted Wan 2.7 is the volume and ops fork for the same family you could self-host. This page is the fork where even a reputable host is disallowed.
What Hunyuan 1.5 is, for this job
Tencent released HunyuanVideo 1.5 as a lighter open video model (the 8.3B backbone in the technical report) with text-to-video and image-to-video, aimed at cinematic motion you can run without a lab cluster. Community write-ups treat it as a motion-quality pick among local checkpoints. That is the reason it shows up in Comfy graphs next to Wan.
It is the right local reach if:
- The brief is off-box, and
- You want open cinematic motion rather than a tiny distilled toy, and
- Someone on the team already runs local video graphs.
It is the wrong reach if you wanted Apache-simple commercial terms. Read the Tencent Hunyuan Community License yourself before you ship. It is not Apache 2.0. Third-party summaries flag territory limits (EU / UK / South Korea in commonly cited copies) and commercial thresholds. Those summaries go stale; the LICENSE file does not. If counsel cannot bless the license for your use and your territory, Hunyuan is not your off-box answer. Another local model might be. "Open weights" is not "do whatever you want."
Versely will not indemnify a local Hunyuan install. We do not run it.
Most people should stay hosted
Stay on Versely (or any host you have actually contracted) if the plate is allowed to leave the building. That is almost every brand, creator, and agency brief. You get a roster, a bill, no on-call CUDA, and a fail-over when Hunyuan-shaped motion is the wrong job anyway — because locally you do not have Veo, Avatar X, or Flux first-last unless you installed those too.
Self-host Hunyuan only when all of these are true:
- The brief forbids hosted APIs, in writing.
- Counsel has read this license, for this territory, for this use.
- A named person operates the box, including updates and the output folder's actual destination.
- You accept a one-family local slate. Off-box Hunyuan does not grow a studio around it.
If you are self-hosting to save money, you are in the Wan hosted versus self-hosting article. Wrong page. If you are self-hosting because Arena liked a Tencent row, you are shopping. Wrong constraint.
How this interacts with Versely
Use Versely for every shot the MSA allows off-box. Use the local Hunyuan node for the shots it does not. Split the slate on the constraint, not on taste. A campaign with one embargoed pack shot and nine social cuts should generate the nine on a host and the one on the box — not the whole campaign on the box because one still is sensitive.
Do not wash an embargoed still through a hosted image model "just to get a cleaner plate" and then run Hunyuan locally on the result. The still already left.
The without hub remains the right map for missing cameras and missing faces. Missing permission to transmit is not an input class we can satisfy. Hunyuan 1.5 is what people reach for when that permission is the thing they do not have.
FAQ
Is Hunyuan 1.5 in the Versely catalog?
No. This page exists because the constraint excludes a hosted catalog. If you can send the plate to a provider, you should be picking a hosted row, not installing Tencent weights as a hobby.
Why not self-host Wan instead?
You can, and Wan's Apache 2.0 terms are often the easier license conversation. Pick the local family counsel and the operator can actually run. Hunyuan shows up when the brief wants that cinematic-motion checkpoint and the file cannot leave. It is not automatically the better model, and it is not the cheaper one.
Does "community licence" mean I can use it in client ads?
Only if the license, your territory, and the client's use all fit. That is a legal read, not a blog claim. Do not treat "open" as a commercial-safety sticker. Firefly-style indemnity is a different product; this is weights on a disk.
Can Versely offer an air-gapped mode instead?
Not as this product is built. Hosted inference is the architecture. When the architecture is the problem, the honest answer is a local checkpoint, not a setting we do not have. Use Hunyuan 1.5 (or Wan, or another local model) on the box, and come back for every shot that is allowed to travel.