What separates a closed hosted model from open weights for a team building an LLM feature?
answer
- who holds the weights
- an API versus a checkpoint file
- the provider decides when it changes
- one checkpoint, many possible hosts
basics
~20 sA closed hosted model is reached only through an API its provider or a licensed partner runs, and the provider can change it; open weights are a checkpoint the team holds, to tune, inspect and serve where it chooses.
solid answer
~40 sWith a **closed hosted model** you send requests to an API run by the provider or a partner it licenses: you never see the weights, you get only the outputs and controls the API exposes, and the provider decides when the model is updated or retired. With **open weights** you hold the checkpoint itself, so you can tune every parameter, read full log-probabilities and internal activations, and have any compatible host, or your own hardware, serve it. The usual trade is capability and convenience against control: closed frontier models often lead on the hardest tasks and need no infrastructure from you, while open weights give up some of that lead for inspection and portability. What the weights' licence allows and what running them costs are separate questions.
go deeper
Recall the one-line split: closed means an API onto weights you never see, open means you hold the checkpoint. Then name one thing each side gives you.
Explain what the API withholds, such as activations, full log-probabilities and the tuned weights from hosted fine-tuning, and what holding a checkpoint makes possible in return.
Tie the choice to a concrete requirement of the feature, like calibrated scores, a model that must not change, or a tiny team with weeks to ship, rather than to ideology.
Frame it as control against convenience and frontier capability, and keep licence, hosting and cost as separate decisions the team makes after this one.
## Two ways to get a model Every LLM feature rests on a sourcing call: where does the model come from? There are two broad answers. - A **closed hosted model** is a model whose trained parameters (its **weights**) are never released. You reach it through an API that the provider runs, or that a partner such as a cloud platform runs under the provider's licence. You send a request, you get a response, and everything between is the provider's. - **Open weights** means the trained parameters are published as a downloadable **checkpoint**: the files that hold every weight of the network, plus its tokenizer and configuration. Whoever holds those files can load them into a compatible serving stack and run the model. The distinction is about **who holds the weights**, not about quality, price or licence. An open checkpoint can carry a restrictive licence, and a closed model can be cheap. ## What a closed hosted model gives and withholds A closed model gives a team a working endpoint on day one: - **No infrastructure**: no accelerators to rent, no serving engine to tune, no on-call rota for the model itself. - **Often the strongest capability**: the best closed models usually lead the best open ones on the hardest reasoning, coding and long multi-step tasks, although the size of that lead varies by task and over time. - **Managed extras**: many providers add hosted fine-tuning, tool calling and structured output to the API. It also withholds things, because you only ever see the API: - You cannot read the model's **internal activations**, and many APIs return **log-probabilities** only for a few top tokens per position, or none at all. - **Hosted fine-tuning**, where offered, runs the provider's methods on the provider's servers; the tuned weights never leave. - The provider decides **when the model changes**: an update, a new default version or a retirement happens on its schedule, not yours. ## What open weights give and cost Holding the checkpoint changes what is possible: - **Full tuning**: you can update every parameter, or train adapters, with whatever method you choose, and keep the result. - **Full inspection**: you can read the probability of every token in the vocabulary and the hidden states at every layer. - **Portability**: the same checkpoint can be served by several unrelated hosts or on your own hardware, so the model does not disappear if one supplier does. - **A frozen reference**: the files you downloaded do not change unless you change them. The cost is that somebody has to **run it**. Even when a managed host serves it, the team now chooses the host, checks how the host serves the checkpoint, and owns more of the evaluation work. And the best open checkpoints have usually trailed the closed frontier on the hardest tasks. ## Side by side | Question | Closed hosted model | Open weights | |---|---|---| | Who holds the weights? | The provider | The team (and anyone else who downloads them) | | Who can serve it? | The provider and its licensed partners | Any compatible host, or your own hardware | | Tuning | The provider's hosted options, if any | Any method, every parameter, result kept | | Log-probabilities and activations | Limited or none | Full | | When does it change? | When the provider decides | When the team decides | | Capability at the frontier | Usually ahead | Usually somewhat behind | | Infrastructure work | None for the model itself | Some, depending on where it runs | ## What this choice does not settle Picking closed or open is the first call, not the only one. Each of these is its own question: 1. **The licence on open weights.** Downloadable does not mean free for any use; whether a team may ship what it plans is a matter of reading the licence. 2. **Where open weights run.** A shared managed endpoint, a dedicated one, rented accelerators and your own racks each hand back different responsibilities. 3. **What running them costs** against paying per token, which is a separate break-even calculation. 4. **Where data may go**, including what a provider retains, which belongs with data-handling policy. ## How interviewers probe it A screening question usually wants the core distinction stated cleanly: closed means you rent access to a model you cannot see or keep; open means you hold the model and take on running it. Strong answers add the consequence that matters for the feature at hand, such as "we need calibrated scores, so we need log-probabilities the API may not give us", or "we are three people shipping in a month, so we start with an API". Weak answers treat open weights as automatically free to use, assume a closed model never changes, or assume open weights require buying hardware.
- Can a team fine-tune a closed hosted model?Often, through the provider's hosted fine-tuning, but on the provider's terms: the team picks from the methods and settings the provider offers, never receives the tuned weights, and can serve the tuned model only where that provider serves it. With open weights the team chooses the method, tunes any parameter it likes and keeps the result.
- Why might a team pick a closed model even when an open checkpoint could do the task?Because there is nothing to run. A small team, a prototype with unproven demand or a task near the capability frontier can gain more from a working endpoint on day one, with no accelerators or serving work, than from control it does not yet need, provided it accepts that the provider sets the pace of change.
- Open weights mean the model is free to use for anything.
- A closed model behind an API never changes once you start using it.
- Open weights are far behind closed models on every task.
- Choosing open weights means you must buy and run your own GPUs.
- A closed model can never be fine-tuned.