Correction · October 13, 2026
Downloadable weights can be fine-tuned or otherwise modified. They do not update themselves, while a full training recipe enables reproducing and changing the training process.

What he said

Nathan Lambert questions whether open-weight models will follow Linux’s growth path. Open-weight models provide downloadable trained files; Linux is an operating system developed through shared code contributions. In a recent post on Interconnects AI, he draws a sharper distinction. “The open-source language model,” meaning a model released with its full training recipe, the raw data and code needed to rebuild it from scratch, “is a closer analogue to the open-source operating system” like Linux, he writes, than the open-weight models most builders actually download and use, which provide trained weights without necessarily providing the complete training recipe. Developers can still fine-tune those weights for specialized tasks.

That distinction matters because of how each one ages. Linux kept improving because a community could keep contributing code back into the same living project. A downloaded model’s weights, Lambert argues, are more like “a specific version of software that you install in a project,” a fixed snapshot that does not improve automatically, even as companies keep building on or modifying it. His read on where that leaves the category: “open models are still incredibly useful, but fill a long-tail ecosystem relative to the closed counterparts.” In plain terms, he expects most open models to end up serving smaller, specific niches rather than closing the gap with the biggest closed, paid models.

Who he is

Lambert writes Interconnects AI, an independent newsletter on AI models, training methods, and research policy. He previously led post-training work, shaping models after their initial training, at the Allen Institute for AI (Ai2). He worked on Tülu, a downloadable language-model project, before his June 2026 farewell. He has also examined AI agent security transparency and AI’s stalled long-form writing ability.

What he gets right, and where it’s speculative

A training recipe lets developers reproduce and change training. Released weights provide a trained starting point. As an example, he points out that companies are still building on Meta’s Llama 3 model years after its release, even as newer, more capable models have shipped since. That matches a pattern builders will recognize elsewhere in software: a team keeps using an older version of a tool it depends on because its product was built and tested against that specific version, not because it’s still the best option available.

Where he moves into forecasting is his claim about where the money goes next. Lambert cites a report that NVIDIA, a supplier of chips used to train and run models, is spending $26 billion supporting the open-model ecosystem. He frames that spending as a wager that enough people training their own models will eventually justify the cost, against the alternative that open models simply settle into a smaller, specialized market. Lambert is making an economic forecast using the reported $26 billion figure. He writes, “It’s not clear if this will work,” before discussing whether training costs will push more companies out.

Why it’s notable

Model routing tools, services that let a team switch between many AI models without rewriting their app, and open-weight models like DeepSeek and Qwen have both been getting louder attention this year, most recently around Stripe’s agreement to acquire the model router OpenRouter. Lambert’s post is a useful check on that enthusiasm: it argues that popularity and long-term viability are different questions, and that an open model being widely used today doesn’t guarantee the ecosystem producing it stays healthy enough to keep producing better ones.

What it means for builders

If your product depends on a specific open-weight model, treat that dependency as a fixed component you chose to lock in, not a service that automatically keeps improving underneath you. Track new releases and support for the chosen model line. Plan how you would validate a replacement if development stops. Lambert’s argument is that some open models will keep getting better, but plenty of others will simply freeze in place while the ecosystem moves on.


End of article