OpenAI returns to open weights

OpenAI has released gpt-oss-120b and gpt-oss-20b, and the launch is bigger than the name suggests. This is OpenAI's first genuinely heavyweight open-weight release since the GPT-2 era, and the models ship under Apache 2.0.

That does not mean OpenAI has suddenly become a pure open-source company. GPT-5, ChatGPT, and the most advanced production models remain closed services. But gpt-oss does something strategically significant: it gives developers, universities, and enterprises an OpenAI model they can download, inspect, fine-tune, and run in their own environments.

120B
largest model
20B
smaller model
Apache 2.0
license

Why this lands now

Open-source AI has grown considerably stronger since 2024. DeepSeek, Qwen, Mistral, Gemma, Granite, and Llama have pushed the market toward open weights, local deployment, and cheaper inference. OpenAI could no longer afford to be the company that simply tells everyone to use its API.

gpt-oss is therefore both a technical product and a political signal. OpenAI is saying, in effect: we want to be part of the open-weight ecosystem too.

The most important news is not that OpenAI has built yet another model. It is that the model does not live exclusively at OpenAI.
OpenAI reopens the weights: gpt-oss brings local reasoning into the mainstream - Bilde 1

What the models are built for

OpenAI describes gpt-oss as reasoning models designed for local use, data centers, and customization. The larger model targets high-end GPU environments, while the 20B variant is built for more accessible hardware.

Both use mixture-of-experts, where only a fraction of the model is activated per token. This makes large models more practical to run, even though they still demand serious infrastructure.

Relevance for enterprises

For organizations, this is particularly interesting in three scenarios. First: where data must not leave the organization. Second: where cost per call matters. Third: where teams want to fine-tune a model on their own documents, domain-specific language, or internal workflows.

A municipality, bank, health-tech company, or industrial supplier now faces a new kind of question: should we buy OpenAI as an API, run OpenAI weights ourselves, or use other open models?

Do not confuse open with easy

Running a model yourself means you also own operations, security, logging, patching, and evaluation. That may well be the right choice, but it is not free magic.

Teams should start with small pilots: document analysis, internal RAG, language benchmarking, and cost measurement against the current solution. Anyone who jumps straight to production without evaluation is simply trading vendor risk for operational risk.

Open weights give you control. They do not automatically give you expertise, security, or lower total cost.

Conclusion

gpt-oss is a clear signal that open models have become strategically necessary — even for OpenAI. For developers and technology leaders, it means more genuine choices: API, self-hosted, hybrid, or fine-tuned.

That is exactly what a mature AI market should look like: fewer religious platform debates, more measurement, more control, and more local autonomy.