# 开源 vs 闭源模型之争：托管与自建基础设施的类比

- 来源：Lee Robinson (@leerob)
- 发布时间：2026-07-24 23:16
- AIHOT 分数：56
- AIHOT 链接：https://aihot.virxact.com/items/cmrz3etk301knroeyst8vzg5g
- 原文链接：https://x.com/leerob/status/2080673380336886212

## AI 摘要

Lee Robinson 认为，开源与闭源模型的争论更应类比为托管与自建基础设施。企业选择开源权重模型可能出于在自有数据上额外训练的需求，这需要 Tinker 等训练软件和 SGLang 等推理服务软件，且并非全部开源。最终决策回归到标准商业考量：人才、硬件成本与维护、以及可靠性的重要性，市场需要两种选择并存。

## 正文

There's something missing from the open vs. closed models debate that has been bothering me.

The better analogy， to me， is managed vs. self-hosted infrastructure for AI.

Maybe a company wants to use an open weight model because they want to do additional training on top， bringing their data and domain knowledge.

This requires software and services to do additional training （e.g. Tinker and friends） as well as to serve the model （e.g. SGLang）. Not all of this software is open source today！

Once you have successfully trained a model with your enterprise data and expertise， you now need to deploy and serve it for customers. You can partner with an inference company to run the software and hardware. But if ownership was your primary concern， you still want to control the hardware and storage， and you now also need to run infra and secure GPU capacity.

There are other valid reasons to be open. In particular， the entire industry benefits when companies training models release data or research about their work. It also allows capitalism and free markets to do their thing， increasing competition and ultimately providing better options for customers. So we should all encourage openness.

The reason I prefer the managed vs. self-hosted infra framing is that we can learn from the past decade of cloud infrastructure. It's important and healthy to have both， and a great self-hosted alternative ultimately pushes the managed versions to innovate.

The decision to run infra then comes down to more standard business reasons： attracting talent， the cost and maintenance of the hardware， and the importance of uptime and reliability to the business.

Many businesses will say， actually， I don't want to staff and run a training and inference team， and I'm happy to pay API pricing for intelligence. And others will do the opposite and invest heavily here. We need both！

As an aside， the capability of open models will reach a point where we need to be very intentional about how they are deployed. But I think this problem is solvable， whether it is sharing research early and weights later， or also open sourcing the safety stack to properly serve the model. I don't have a perfect answer here but I think the ecosystem should figure it out together.

Full disclaimer， I work at a company which has released both open and closed models. There are probably people more knowledgable than myself of the open weights ecosystem. If that's you， curious if you disagree with any of this.