Open weights are getting a revenue share clause
Reuters reports Alibaba will ask heavy commercial users of its next open Qwen release to share revenue. Moonshot's Kimi K3 license already does exactly that.
Free to download is not the same as free to run. Two Chinese labs are proving the difference.
Reuters reported on August 7, 2026, citing two people familiar with the plan, that Alibaba intends to require heavy commercial users of its next open source Qwen model to share revenue. It would be a first for Qwen, whose previous open releases carried permissive terms. The percentage and the threshold are not settled, and Reuters does not name the model, describing the release as imminent.
Kimi K3 already wrote it into the license
The precedent is public and checkable. Moonshot's Kimi K3 license requires anyone offering the model as a service to negotiate a commercial agreement with Moonshot once that service passes $20 million in revenue over twelve months, and it carries a separate attribution and display clause that triggers at 100 million monthly active users or $20 million in monthly revenue. Reuters adds a figure the license text does not contain: that Moonshot can seek up to a 30 percent revenue share in some arrangements. That number comes from Reuters' sources, not from the published terms, and is worth holding as reporting rather than fact.
This is what open weights actually means now
Open weights and open source have never been the same thing, and this is the moment the gap becomes a line item. A license with a royalty trigger, or a field-of-use restriction, or a revenue threshold that forces you into a negotiation is not an open source license under the OSI definition, whatever the download page says. The business logic is easy to follow: Alibaba currently earns from Qwen through Alibaba Cloud hosting while self-hosted commercial deployment is free, and a revenue share converts the largest self-hosters from free riders into licensees. Freemium, arriving in model distribution.
Why a build studio cares
Because the license is a build decision, not a legal footnote, and it has to be read before the model goes anywhere near a client product. The question is no longer whether you can download the weights. It is what happens at the threshold: whether the product you are shipping counts as model-as-a-service, what the revenue trigger is measured against, and whether crossing it means a negotiation with a lab in another jurisdiction. That is a very different risk profile from an MIT release like DeepSeek's V4-Flash, and the two now sit side by side on the same download pages.
Next step: read the Reuters report and, if you are weighing Kimi K3, read the actual license terms rather than the launch post. If you want the licensing implications of a model choice checked before you build on it, write to us at hello@gattyworks.com.