An open source AI modelis a machine-learning model whose weights, architecture and training code are released under a license that lets you download, inspect, modify and redistribute the system. That distinguishes them from closed frontier models — which you can only reach through a vendor's API — and lets you run them on your own hardware, fine-tune them on your own data, and ship them inside your product without sending every request to a third party.
People often conflate open source with open weight, but they are not the same thing. An open-source release publishes the model weights plus everything you would need to reproduce them: training data, training scripts, the evaluation harness and a license. An open-weight release shares the weights but keeps some of those pieces private. Both let you self-host; only the former lets you fully reproduce the result.
Are open source AI models free for commercial use?
Not always — “free to download” and “free for commercial use” are different questions. Permissive licenses such as Apache 2.0 and MIT let you use the model in a commercial product, modify it and redistribute it with very few conditions. Others, like some community or research licenses, restrict commercial use above a revenue threshold or forbid using outputs to train competing models. Before you ship, check the License and Commercial use filters on each model card and read the original model card — that is the only source that is legally binding.
How to run open source AI models locally
You do not need a data centre to start. For laptops and single-GPU desktops, Ollama and llama.cpp run quantised models (4-bit and 8-bit builds) with a one-line install, trading a little accuracy for a much smaller memory footprint. For production serving and high throughput, vLLM and Text Generation Inference batch requests across a GPU efficiently. As a rough guide: a 7B model needs roughly 4–6 GB of VRAM when quantised, a 13B model around 8–10 GB, and 70B-class models realistically want multiple GPUs or aggressive quantisation. Use the Parameters and Context window filters above to find a model that fits your hardware.
Open source vs API models — which should you choose?
Hosted API models are fastest to integrate and need zero infrastructure, but you pay per token, your data leaves your network, and you cannot pin a specific version forever. Self-hosted open models flip every one of those trade-offs: fixed infrastructure cost instead of per-request billing, full data privacy, complete version control and the freedom to fine-tune. A common pattern is to prototype against a hosted API, then move the steady, high-volume workloads to an open model you host yourself once the economics make sense. Many open models are also available through hosted providers (Together AI, Groq, Fireworks, Hugging Face), so you can get both without rewriting your code.