Open Source AI Has a Weight Problem — The Models Ship, the Infrastructure Doesn't

Open source has become the Swiss Army knife of AI arguments. Decentralize AI, and you get privacy and safety. Run a model locally, and the environmental critique evaporates. Ship a healthcare dataset with published code, and you're doing science instead of surveillance. Whatever the problem with AI turns out to be, someone in the conversation will reach for open source as the fix — which is, increasingly, how you know the term is doing too much work.

The clearest version of this tension comes from people who actually watch what gets released. Weights keep shipping. Infrastructure doesn't. As one observer put it in a widely circulated post, "everyone's shipping weights. Few are shipping scaffolding. The gap gets wider."[¹] The open source AI community has become practiced at releasing models and conspicuously quiet about releasing the tooling needed to make them useful in production. The Meta-backed Llama series is exhibit A: celebrated for pushing weights into the public, criticized for a "mixed track record on real production tasks" and for doing little to actually close the gap on reasoning.[²] Open in distribution is not the same as open in practice, and practitioners are starting to say so plainly.

Where open source does real lifting is in the ethics conversation, but it gets conscripted there in ways that flatten genuine complexity. There's a recurring argument — earnest and not entirely wrong — that the pathologies people associate with AI are pathologies of centralized, proprietary systems specifically.[³] Running an open source model locally, on this view, is more like running a demanding video game than feeding the surveillance economy. The logic holds, as far as it goes. But it tends to collapse the moment someone asks who trained the base model, on what, and under whose labor conditions. The AI ethics conversation keeps returning to open source as a solution to problems that open source cannot solve alone, which lets the harder questions go unasked.

In healthcare specifically, open source arrives wearing its most respectable clothes: peer-reviewed methodology, published datasets, reproducible code. An arXiv paper developing open data infrastructure for accelerometry-based activity classification in clinical settings[⁴] represents what open source looks like when it's doing genuine epistemic work — not branding, not political positioning, just auditable science. That version of open source barely registers in the louder discourse, which is worth noting. The word does the most convincing work when it's deployed quietly.

The trajectory here isn't toward resolution — it's toward fragmentation. "Open source" is already doing triple duty as an ethics position, a technical specification, and a political category, and the strain shows in every conversation where it appears. The infrastructure gap will force a reckoning that weight releases alone have deferred: at some point, open weights without open tooling is just a different kind of vendor lock-in, and the community will have to decide whether open source is a philosophy or a marketing badge. The people pushing the hardest for decentralization seem to sense this, which is why the frustration in their posts isn't directed at closed labs alone — it's directed at everyone who said "open source" and meant something different each time.