Wan 3.0 Apache-2.0: repo license line vs hosted API on Sume

Is Wan 3.0 open source? The Wan 3.0 repository shows an "Apache-2.0 license" line, but its page does not say that model weights are released. It points readers to Wan Explore and QwenCloud for access. A license on a documentation repo is not proof that you can download and run the model, so read it as unconfirmed. On Sume, wan-3.0 is a hosted id.

What the page says and does not say

The README lists seamless 30 second generation and up to 20 reference assets, and I found no resolution figure on the page.

Hosted on Sume

Sume's video models docs list wan-3.0 at 2 to 30 seconds and 480p, 720p and 1080p, with 1080p as the default, and references of up to 10 images, 5 videos and 5 audio clips. I found no document or web-page reference fields in Sume's request schema, so do not assume the document and webpage inputs the repo describes are available there.

List rates in the catalog are $0.05, $0.10 and $0.20 per second for 480p, 720p and 1080p. Billed on Sume that is list times 1.25 rounded up to cents.

Practical read

If you need weights on your own machine, wait for a page that says where they are and under which license, and do not assume the repo footer covers them. If you need a 30 second render by API today, request wan-3.0 and use image, video and audio references; leave documents and web pages out of the request unless the live descriptor lists them.

A checklist for open-source claims

When a launch says open source, look for three things on the vendor's own page: a link to downloadable weights, a license file that names the weights, and a model card that states what the license covers. The Wan 3.0 repo page I read shows none of these, only a license line. Ask whether the license covers code, weights or both. Until the vendor says, plan with the hosted route, and recheck the repo when a release is announced.

Wan 3.0 is described by Alibaba as supporting instruction-based editing and automatic scene splitting. Those are model features on the vendor page; they are not separate Sume endpoints, so for editing on Sume the route is the request fields the catalog exposes.