Kimi K3 Adds 20 Million Dollar Revenue Gate as Open Weights Split on Licensing
Moonshot's Kimi K3 license has grown substantially compared with Kimi K2, reflecting tighter commercial guardrails for large Model-as-a-Service operators. The K3 terms now span 3,065 bytes versus K2's 1,463 bytes and require operators whose 12-month group revenue exceeds twenty million dollars to sign a separate Moonshot agreement before offering the model as a service. Coverage also links Alibaba to planned revenue-sharing terms on the upcoming Qwen3.8-Max open-weight release, indicating open weights are diverging into differentiated licensing regimes instead of one permissive baseline. For builders evaluating open-weight stacks, scale can flip usage from assumed free deployment to negotiated commercial terms. Details on Qwen remain forward-looking rather than final published license text, so terms may still change before release.
Kimi K3 Adds 20 Million Dollar Revenue Gate as Open Weights Split on Licensing
Moonshot's Kimi K3 license grew to 3,065 bytes from K2's 1,463 bytes, adding a clause that Model-as-a-Service operators above $20 million in 12-month group revenue must sign a separate Moonshot agreement. Reuters also reported Alibaba plans revenue-sharing terms on the upcoming Qwen3.8-Max open-weight release.
Key takeaway
Open weights at commercial scale are shifting from assumed free deployment to revenue-triggered licensing gates that require separate vendor agreements.
What happened
According to Towards AI reporting, Moonshot's Kimi K3 license expanded to 3,065 bytes from Kimi K2's 1,463 bytes, adding new commercial conditions for operators hosting the model as a service.
The added clause states that Model-as-a-Service operators with more than $20 million in 12-month group revenue must sign a separate Moonshot agreement; Reuters reporting cited in the same coverage also says Alibaba plans revenue-sharing terms on the upcoming Qwen3.8-Max open-weight release.
Evidence
Kimi K3 license text is more than twice the size of Kimi K2 license text.
Towards AI · attributed
Moonshot's Kimi K3 license grew to 3,065 bytes from K2's 1,463 bytes
Kimi K3 adds a revenue threshold that triggers a separate Moonshot agreement for MaaS operators.
Towards AI · attributed
Model-as-a-Service operators above $20 million in 12-month group revenue must sign a separate Moonshot agreement
Alibaba is reported to plan revenue-sharing terms on Qwen3.8-Max open-weight release.
Towards AI · attributed
Reuters also reported Alibaba plans revenue-sharing terms on the upcoming Qwen3.8-Max open-weight release
Why it matters
MaaS operators and product teams must read license deltas before scaling, because crossing revenue thresholds can force renegotiation, pricing changes, or architecture pivots away from open-weight serving.
Limits and uncertainties
Reuters reporting on Alibaba Qwen3.8-Max revenue-sharing is cited secondhand in Towards AI coverage, not as final published license text.
The packet references DeepSeek V4 in the headline but provides limited concrete licensing detail on that model in the excerpts.
Practical implications
Compare LICENSE file size and clause changes across model generations before selecting an open-weight stack for production serving.
Run legal review on MaaS offerings as 12-month group revenue approaches the $20 million Moonshot threshold.
What to watch
Publication of final Qwen3.8-Max license language and any Alibaba revenue-sharing terms.
Whether additional open-weight releases adopt similar MaaS revenue gates above defined thresholds.
