Skip to content
Skip to content

Independent e-magazine

the OUTSPOKEN digest

Alibaba's Open Models Passed Three Billion Downloads. Distribution Is the Whole Story

Qwen has overtaken Meta and Google on cumulative downloads. In open weights, the number that decides the winner is not benchmark performance, it is how many things get built on top.

Outspoken Digest Technology Desk

Monday, August 17, 2026/3 min read

Rows of servers in a data centre
Editorial illustration generated for Outspoken Digest

Alibaba's open-weight model family has passed three billion cumulative downloads, moving ahead of Meta and Google on that measure. Download counts are a crude metric and this one is worth taking seriously anyway, because in open weights distribution is close to the entire competitive question.

Why downloads matter more here than elsewhere

For a closed model behind an API, the meaningful numbers are revenue and usage, and the vendor controls both the product and the relationship.

An open-weight model has no relationship. Once the weights are published, the publisher cannot see who is using them, cannot bill for them and cannot deprecate them. What the publisher gets instead is everything built on top: the fine-tunes, the quantised versions that run on cheaper hardware, the tooling, the tutorials, the deployment recipes and the accumulated knowledge in engineers' heads about how this particular family behaves.

That accumulation compounds. A team that has already shipped one product on a model family will reach for it again, because the integration work is done and the failure modes are known. Downloads are a proxy for how deep that stack has become, and the stack is the moat.

The second effect: it sets the default

When a family becomes the most downloaded, it becomes the one that examples are written against, the one hardware vendors optimise for, and the one a hosting provider supports first.

That is a self-reinforcing position and it is worth more than a benchmark lead, because benchmark leads change every few months while defaults change every few years. A model that is slightly behind on evaluations but runs on the inference stack a company already operates will win the deployment decision most of the time.

It is also why the release cadence has become so aggressive across the field. We described the pattern in open-weight models shipping like patches: frequent, incremental, and aimed at keeping an ecosystem attached rather than at winning a headline.

What this does to the sovereign AI conversation

A great deal, and it is the part most relevant to this region.

A government or enterprise that wants models running inside its own borders, on its own hardware, under its own rules, cannot achieve that with an API. It needs weights it can host. The strength of a given open family therefore determines what is practically achievable for anyone pursuing that policy, and the strongest options are increasingly not American.

That is a strategic fact with a long tail. National platforms built on a particular family inherit its licence terms, its language coverage, its tokeniser and its assumptions, and those are difficult to unwind three years later. Our piece on open weights, chips and sovereign AI traces where that leads.

What a download count does not tell you

Enough that the number should not be used alone.

  • It counts pulls, not deployments. Continuous integration systems, mirrors, benchmarks and curious engineers all generate downloads that never become products.
  • It aggregates a family. A count spanning many model sizes and variants is not comparable to one spanning few, and small models download far more often because they are cheap to try.
  • It says nothing about the value of the work built on it. A million hobby projects and a hundred production systems can produce similar figures with entirely different economic weight.
  • It is publisher reported. The definitions are not standardised across platforms, and nobody audits them.

Does this mean open models have won?

No. It means the open segment has a clear leader, which is a different claim.

The frontier of capability remains closed, the largest revenues remain closed, and the most demanding workloads still mostly run against hosted APIs. What has changed is that the floor has risen far enough that a very large share of real commercial tasks, classification, extraction, summarisation, routing, drafting, no longer needs a frontier model at all.

That is the actual competitive pressure. Not that open models will beat closed ones at the hardest problems, but that they are now good enough at the ordinary ones, and ordinary problems are where nearly all the volume is.

Published in The Outspoken Digest

Editorial desk

Outspoken Digest Technology Desk

Software, hardware, artificial intelligence and what they change for everyone else.

Newsletter

The Digest, in your inbox

One edition, sent when it is ready. No noise, and your address is never passed on.

We send a confirmation first. One click to leave, always.

Share this story

the OUTSPOKEN digest

Beyond boundaries. Independent stories on technology, culture, and the trends shaping how we live.