Qwen
Qwen is Alibaba's model line, and the part this guide recommends is the open-weight family: the models you download and serve on your own hardware. One clarification matters up front: the current flagship Qwen 3.7 models are closed-weight and API-only, so the open-weight line is what you self-host, and it is what this page describes.
A paid hosted API also exists, running on Alibaba Cloud, and for some organisations that carries a jurisdiction question. Self-hosting the open weights removes it entirely, because data governance stays in your hands rather than with any provider.
The ceiling is worth naming plainly. On ambiguous specs and sustained multi-agent work the closed frontier models still win, so the working pattern is not Qwen instead of a frontier model but Qwen as the daily driver, with a retained frontier seat for the hardest problems. No tool is best for everyone; this one is best when you want to own the model layer.
- Cost
- Free tier + paid plans
- Ease
- Intermediate
- Model
- Runs privately (self-hostable)
- Checked
- July 2026
Prices, plans and model versions change fast: this is a mid-2026 snapshot; check the tool's official site for the latest.
Best for
- The current default for new self-hosted coding work
- Apache-2.0 open weights, free to download and run
- Coding agents on infrastructure you control
- Local prototyping with Ollama, production with vLLM
- An actively maintained open-weight coding line
Less suited to
Anyone who wants coding AI without owning infrastructure is better served elsewhere. GitHub Copilot is the broadest and cheapest entry, working in-editor with a free tier; Claude Code goes deeper when the specification is ambiguous and the work genuinely hard; and Kimi Code offers an open-source coding agent you adopt whole, with no serving stack to build first.
The standing obligation is operational. The weights cost nothing to download, but the spend shifts to GPUs and the engineering time to serve them, and that commitment runs for as long as the deployment does. Treat the decision as buying infrastructure rather than software: capacity to plan, a serving stack to operate, and a team that owns it when it breaks.
Costs & data, in short
The Apache-2.0 open-weight line is free to download and self-host, with spend shifting to GPUs and the engineering time to serve them; a paid hosted API exists alongside, and the current flagship Qwen 3.7 models are closed-weight and API-only.
Qwen's hosted API runs on Alibaba Cloud, which carries a jurisdiction question for some organisations. Self-hosting the open weights removes it: the model runs on your own infrastructure, so data governance stays entirely in your hands.
In practice
How Qwen is used, area by area.
Software development
Qwen earns its place in a development team's stack by being the open-weight line built for exactly this work: agentic coding, under an Apache-2.0 licence, kept current rather than frozen at an old release. The path from experiment to production is well worn, Ollama on a developer's laptop and vLLM once the whole team depends on it, so adopting it is an engineering project with known shapes rather than a research effort. It is built to carry the everyday volume, with the retained frontier seat picking up whatever exceeds it. Development teams that want their everyday coding model under their own control gain the most.
Example tasks
- Run an agentic coding model on infrastructure you control
- Generate and refactor code without source leaving the building
- Power an internal coding assistant behind the firewall
- Prototype coding workflows locally through Ollama
- Serve the whole team's coding traffic through vLLM
Limits
On ambiguous specs and sustained multi-agent work the closed frontier models still do better, so keep a frontier seat for the hardest problems. If nobody on the team wants to own model infrastructure, a hosted coding tool is the simpler choice.
Compares
| vs | Pick Qwen when | Pick the other when |
|---|---|---|
| Claude Code | Qwen gives you open weights to run and govern yourself where Claude Code is a token-metered frontier agent | the work is ambiguous and genuinely hard, the territory where the closed frontier models still win |
Operations
For operations, Qwen changes the shape of the AI estate. Inference runs on hardware you govern, so the data-residency answer is structural rather than contractual: nothing leaves your infrastructure because nothing needs to. The hosted API on Alibaba Cloud exists for teams that want it, but the question it raises for some organisations simply does not arise when you serve the weights yourself. Cost becomes an infrastructure line, GPUs and the engineering time to run them, instead of a dependency on an external provider, and the same vLLM stack will serve DeepSeek as a second open-weight option if model diversity matters. Operations leaders who need a defensible data-governance story alongside predictable infrastructure planning gain the most.
Example tasks
- Serve an internal model with no data leaving your estate
- Meet data-residency requirements with in-house inference
- Standardise one vLLM serving stack across teams
- Plan AI spend as GPU capacity and engineering time
- Add or swap open models without changing the stack
Limits
Without GPU capacity or serving expertise, the operational load lands squarely on your team. If the organisation is satisfied with a hosted provider's data posture, running your own inference is effort you do not need to spend.
Compares
| vs | Pick Qwen when | Pick the other when |
|---|---|---|
| DeepSeek | Qwen is the current default for a new self-hosted deployment, with DeepSeek the natural second open-weight option on the same serving stack | its free hosted chat and low-cost API fit your governance requirements and you would rather not run infrastructure at all |
Private, local & self-hosted
This category is Qwen's home ground. The open-weight line is Apache-2.0, free to download and run, and actively maintained, which matters because a self-hosted deployment is a long-term commitment and an unmaintained line ages badly. That freshness is the substance behind its position as the current default for new self-hosted coding work. The tooling path is well established: Ollama on a laptop to prove the idea, vLLM when it becomes infrastructure, and DeepSeek available as the second open-weight option on the same stack, so choosing Qwen never locks you into a single model. Teams standardising on self-hosted open weights, and wanting the line most likely to stay current, gain the most.
Example tasks
- Self-host current open weights for coding work
- Keep prompts, code and outputs entirely on your hardware
- Prove the idea on a laptop before buying GPUs
- Serve concurrent users at production throughput with vLLM
- Keep DeepSeek as a second option on the same stack
Limits
The flagship Qwen 3.7 models are closed-weight and API-only, so the very top of the range cannot be self-hosted. Production serving is also real infrastructure work; at personal scale, stay on Ollama and defer the rest.
Compares
| vs | Pick Qwen when | Pick the other when |
|---|---|---|
| LlamaFull comparison → | Qwen is the actively maintained line, while Meta has shipped no major new open-weight family since April 2025 | an existing deployment and its wide tooling support outweigh having the freshest weights |
Coding & software development
Within coding AI, Qwen represents a distinct posture: the model is the product, not an app or a plan. You take the Apache-2.0 weights, serve them, and connect them to whatever agentic workflow you run, which suits organisations that treat coding tooling as owned infrastructure rather than a per-seat purchase. The line is tuned for agentic coding, and heavy everyday workloads run without per-token metering because the weights themselves are free; the spend is GPUs and the engineers who serve them. Qwen therefore slots in as the daily driver beside a retained frontier seat rather than as a replacement for one. Engineering organisations running high-volume agentic coding on owned infrastructure gain the most.
Example tasks
- Anchor a coding stack you own end to end
- Run heavy agentic workloads without per-token charges
- Pair a self-hosted daily driver with a frontier seat
- Wire open weights into your existing coding agents
- Scale from solo Ollama use to team-wide vLLM serving
Limits
Developers who want completions working in minutes are better served by an in-editor product than by weights to deploy. And the hardest, most ambiguous engineering problems still belong to the closed frontier models.
Compares
| vs | Pick Qwen when | Pick the other when |
|---|---|---|
| Kimi Code | Qwen is a model line you serve through your own stack, whereas Kimi Code is Moonshot's own open-source client that you adopt as a whole | you want a working coding agent from about $19 a month rather than infrastructure to build |
Where to start
Not sure what to adopt first?
Five quick questions about your job, task and constraints. We'll suggest your top three tools, plus the one to try first.
Alternatives
Same category, different strengths.
Where it fits
Explore this tool in context.
For your job
Common questions
What is Qwen best at?
Qwen is strongest for the current default for new self-hosted coding work; apache-2.0 open weights, free to download and run; coding agents on infrastructure you control; local prototyping with Ollama, production with vLLM; an actively maintained open-weight coding line.
What is Qwen not good for?
Anyone who wants coding AI without owning infrastructure is better served elsewhere. GitHub Copilot is the broadest and cheapest entry, working in-editor with a free tier; Claude Code goes deeper when the specification is ambiguous and the work genuinely hard; and Kimi Code offers an open-source coding agent you adopt whole, with no serving stack to build first. The standing obligation is operational. The weights cost nothing to download, but the spend shifts to GPUs and the engineering time to serve them, and that commitment runs for as long as the deployment does. Treat the decision as buying infrastructure rather than software: capacity to plan, a serving stack to operate, and a team that owns it when it breaks.
Is Qwen free?
There's a free tier to start; paid plans add capacity and features.
Where does Qwen fit best?
Qwen fits best in Software development and Operations; see its practice notes for how.
Before sharing confidential or personal data, check this tool's data-governance and training policies. They differ between providers and can change.
Last checked: July 2026