DeepSeek-R1 or QwQ: which reasoning model to pick

Both reason step by step before answering, both are in Ollama, and both licenses are permissive: MIT for R1 and Apache 2.0 for QwQ. R1 offers sizes from 1.5B to 671B, distilled versions included, and runs on a CPU, so you can start small and scale as load grows. QwQ exists in a single 32B size and needs a GPU, but it is a ready reasoning model for calculations, formula checks and working through problems. The catalog marks QwQ as not supporting Russian and makes no claim for R1, so for Russian text you should test both on your own data.

Comparison based on catalog data

ParameterDeepSeek-R1QwQ
CategoryTextMath and reasoning, Text
DeveloperDeepSeek, ChinaQwen (Alibaba), China
ReleasesJan 2025 – May 2025Nov 2024 – Mar 2025
Sizes1,5B – 671B32B
HardwareLaptop, 1 GPU, Cluster1 GPU
Commercial useCommercial use allowedCommercial use allowed
LicenseMITApache 2.0
RussianNot statedNot supported
OllamaYesYes
Without GPUYesNo
Tasks
  • Complex calculations and logic checks
  • Analysis of contracts and internal policies
  • Help for developers
  • Step-by-step review of disputed cases
  • Calculations and formula checks
  • Complex analytics with step-by-step breakdowns
  • Checking the logic of contracts and internal policies
  • Training and working through problems

Choose DeepSeek-R1 if

  • You want a size range: from 1.5B on a CPU up to 671B on a cluster
  • The MIT license matters to you
  • Legal and finance work: contracts and disputed cases broken down step by step
DeepSeek-R1

Choose QwQ if

  • A single 32B size on a GPU is fine for you
  • You specifically need Apache 2.0
  • Maths, engineering and training tasks with step-by-step breakdowns
QwQ

Other comparisons

Need a model for your task?

An open model can run on your own server: data stays in-house, there is no per-request fee, and the model can be fine-tuned on your documents.

  1. SelectThe model and size for your task and hardware budget
  2. DeployOn your server or in a closed network, with an API
  3. Fine-tuneOn your data, or connect a knowledge base
  4. IntegrateInto your CRM, ERP, bot, website or team chat
Discuss deployment