Two Stories That Define This Year's Open-Weight Divide

Two stories that illustrate this year's open-weight divide

Two news items this week each tell a different side of the same story: the battle over who owns the open models — and what "open" actually costs.

Part 1: Kimi K3 — the world's largest open-weight model turns heads

Since the launch of Moonshot AI's Kimi K3 on July 16, interest has exploded, and the weights were released on July 26–27 under a Modified-MIT-like license (the "Kimi K3 License") on Hugging Face.

It's the largest open-weight model ever released — a leap that had both Reddit and Hacker News saying the model "stuns the world." What's notable isn't just the size, but the timing: the full weights followed only ~10 days after the API launch — a pace no closed vendor can match.

Why it matters

Open weights aren't just API access:

• Self-hosting & modification — teams can fine-tune, quantize, or run fully air-gapped.
• Independent inspection — researchers can finally examine the MoE routing and tokenizer.
• No vendor lock-in — once weights are public, price competition shifts to whoever hosts best.
• An auditable commercial license.

What does the "Kimi K3 License" actually contain?

Here's where it gets interesting — because the license behind K3 is not pure MIT, nor is it called "modified MIT" anymore. It's an entirely bespoke document (the "Kimi K3 License," tagged license:other on Hugging Face) that Moonshot wrote line by line — and unlike many other labs, they consistently call it open weight, never open source. That's precisely what the license text is about: very open in practice for most users — but with commercial thresholds that grow as you do.

What the license itself covers

The license first defines what "Software" includes: not just the model weights (weights), but also the parameters (parameters), configuration files (configuration files), both inference and training code (inference and training code), and all associated documentation, grouped under a single term ("the Software").

It then grants broad rights entirely in MIT style:

The rights to use, copy, modify, merge, publish, distribute, sublicense and/or sell copies; as well as to run, deploy or fine-tune the model and create derivative works from it.

So essentially everything you'd normally be able to do under MIT — but only until you hit two specific commercial thresholds, which we go through below:

Threshold 1: Model-as-a-Service + the $20M rule

The license introduces its own definition of "Model as a Service" (MaaS):

Giving a third party access to language model inference or fine-tuning (e.g. via API) in a way that gives the third party meaningful control over inputs, parameters, or training data.

An important nuance from the license text:

• (a) End-user products where the model's capability is simply embedded in specific features/harnesses do not count as MaaS.
• (b) Pure relaying of requests to models hosted by others also doesn't count as MaaS.

But if you run a MaaS business AND your aggregate group revenue exceeds $20M, the following applies:

You must enter into a separate agreement with Moonshot AI before using the Software or its derivative works commercially.

Note the wording "aggregate revenue of the Licensee and its affiliates exceeds … in total over any consecutive 12 months" — that is, the entire group's combined revenue measured on a rolling basis over any twelve-month period, not just revenue from the Kimi model itself.

Threshold 2: Interface attribution

If you use the Software or its derivative works in a commercial product/service that either has

• more than 100 million monthly active users (MAU), or
• more than $20 million in monthly revenue,

you must prominently display the name "Kimi K3" in the product's user interface (UI). This structurally echoes the attribution clause Kimi had in K2's modified-MIT license from July 2025 — but where K2 required attribution display at the same kind of large traffic thresholds, K3 goes further by also requiring a separate agreement above the MaaS revenue threshold mentioned above.

The exceptions (§4)

The two requirements above (§2 and §3) do NOT apply if:

1. (a) Internal use: You use the Software internally such that the Software, its output, or its underlying capabilities are never made available to third parties.
2. (b) Official channels: You use the Software through Moonshot's own official products or certified inference partners.

In concrete terms, this means most European companies' typical scenarios fall outside both commercial restrictions:

• Internal RAG, support, analytics, or coding solutions = internal use → no separate agreement required.
• Use via Together AI/Modal/Moonshot's own endpoints = certified partners → no separate agreement required.
• Only if you build a large public MaaS business on top of the model AND exceed the $20M group threshold do you need to contact Moonshot directly (license@moonshot.ai).

The disclaimer (§5)

Finally, the license contains a standard "AS IS" disclaimer entirely in line with the Warranty Disclaimer section found in many open-source licenses: the software is provided WITHOUT warranty of any kind (including merchantability/fitness/non-infringement), and Moonshot AI is not liable for claims/damages of any legal basis arising from the software or its use.

Summary table

The other side of the coin

The same week, Anthropic CEO Dario Amodei warned against exactly this type of release — not with a ban on open weights ("a public good"), but by pushing for chip export controls and mandatory safety testing of open models from China.

The contrast: Is the US keeping its open-weight promises?

While China delivers weights fast and openly, parts of the community are questioning American companies' promises:

"OpenAI released gpt-oss 350 days ago… will we ever get an update?" — r/LocalLLaMA

The debate isn't just about one model, but about the pattern: the US dominates the frontier models but keeps them proprietary; China wins on volume and openness in the open-weight segment — a strategic shift with consequences for who can build on these models locally in the EU.

💸 Part 2: DeepSeek turns the price war on its head

The second big story landed on Thursday, August 6: DeepSeek signals "significant" price increases on its API services — a marked break from the ultra-low-price strategy that has otherwise defined the entire Chinese AI price war.

Current prices (before the change):

The company has not yet disclosed either the size of the increase or an effective date — so the change has been announced, not yet in effect.

Why now?

Several forces are pulling in the same direction:

• Economic pressure — ultra-low prices are hard to sustain under intense competition.
• Record demand — V4 Flash topped OpenRouter's weekly leaderboard with over 7 trillion tokens; rising inference volume is squeezing margins.
• A strategic shift — signaling that even the low-price vendors now need to make money rather than just win market share.

For developers, this means higher operating costs — but also an acknowledgment that "infinitely cheap AI" was never a sustainable state; something had to give sooner or later.

The bigger picture

Two seemingly opposite movements illustrate the same trend:

1. Openness is accelerating eastward (Kimi K3 = the largest ever) while Western companies keep their frontier models closed.
2. The price war is winding down (DeepSeek raising prices) after months of destructive low-price competition.

Together, they point to a maturing market: open weights are getting cheaper to access but more expensive to scale in production — and the question of who can actually build on tomorrow's models is becoming more geopolitical than ever.