DeepSeek R1

Specs not independently verified

Verdict

A Mixture-of-Experts reasoning model that reset price expectations for frontier-class performance.

Where it wins, where it doesn't

Pros

Exceptional mathematical and code reasoning
MoE architecture cuts inference cost against dense equivalents
Open weights with no dependency on US-hosted inference

Cons

Enterprise procurement often blocks it on provenance grounds
Large MoE models are harder to deploy locally than the parameter count suggests
Memory footprint is the full parameter count despite lower compute

Ideal forSoftware engineering and mathematical workloadsCost-sensitive reasoning at scaleTeams needing inference independent of US providers

Editorial note

R1 mattered less for any single benchmark than for what it demonstrated: frontier reasoning did not require frontier budgets, and the assumption that capability tracks capital was wrong. The MoE architecture is the mechanism — only a fraction of parameters activate per token, so inference cost falls sharply relative to a dense model of equivalent capability. It is genuinely strong on mathematics and code, which are the domains where reasoning either works or visibly does not. Two caveats that decide adoption rather than capability: many enterprises have procurement positions on model provenance that no benchmark overcomes, and deploying a large MoE locally is materially harder than a dense model of the same nominal size, because the memory footprint is the full parameter count even though the compute is not.

In-Depth Review

Where it is strong

Mathematics and code — the domains where reasoning either works or visibly does not. Open weights mean no dependency on US-hosted inference.

The caveats that decide adoption

Enterprise procurement often blocks it on provenance grounds — a position no benchmark overcomes.
Deploying a large MoE locally is materially harder than the parameter count suggests: the memory footprint is the full parameter count even though the compute is not.

Who should use it

Software-engineering and mathematical workloads, cost-sensitive reasoning at scale, and teams needing inference independent of US providers. If your organisation has a provenance policy, or you lack the memory to host a large MoE, this is not the path.

Frequently Asked Questions

Who is DeepSeek R1 for?↓

DeepSeek R1 is a fit for software engineering and mathematical workloads, Cost-sensitive reasoning at scale and Teams needing inference independent of US providers.

What are the drawbacks of DeepSeek R1?↓

The trade-offs we record are: Enterprise procurement often blocks it on provenance grounds, Large MoE models are harder to deploy locally than the parameter count suggests and Memory footprint is the full parameter count despite lower compute.

What does DeepSeek R1 do well?↓

Exceptional mathematical and code reasoning, MoE architecture cuts inference cost against dense equivalents and Open weights with no dependency on US-hosted inference.

Alternatives to consider

See all alternatives →