Qwen3.8-27B vs DeepSeek V4 for agentic coding: what the numbers show
Updated 13 November 2026
Qwen and DeepSeek both publish agentic coding scores, so this looks easier than the Sonnet question. It isn't, and the reason is in the tables themselves: each vendor lists Opus 4.6 Max as a reference, and they give it different scores. Here's what each model card says and why the rows can't be merged into one ranking.
What each card reports
| Test | Qwen3.8-27B (Qwen's card) | Opus 4.6 Max (Qwen's card) | DeepSeek V4-Pro Max (DeepSeek's card) | Opus 4.6 Max (DeepSeek's card) |
|---|---|---|---|---|
| SWE-bench Pro | 61.7 | 53.4 | 55.4 | 57.3 |
| Terminal Bench | 73.0 (version 2.1) | 78.2 (version 2.1) | 67.9 (version 2.0) | 65.4 (version 2.0) |
| LiveCodeBench | 90.3 (v6) | 88.8 (v6) | 93.5 | 88.8 |
| SWE-bench Verified | Not reported | Not reported | 80.6 | 80.8 |
Why the rows don't line up
On SWE-bench Pro, Qwen's card puts Opus 4.6 Max at 53.4 and DeepSeek's card puts it at 57.3. It's the same model, so the 3.9-point gap comes from setup. Qwen says it corrected problem tasks in the benchmark and re-ran the other models, and used Opus's officially reported score for that row. DeepSeek's card gives no harness notes. Terminal Bench differs too: Qwen reports version 2.1 and DeepSeek version 2.0.
Read across the two cards and Qwen3.8-27B looks ahead on SWE-bench Pro (61.7 against 55.4). Read each card against its own Opus row and the picture is different: Qwen is 8.3 points above Opus on its card, and DeepSeek is 1.9 points below Opus on its own. Neither comparison is wrong, and neither tells you how the two models would do on the same tasks.
How the models differ
| Qwen3.8-27B | DeepSeek V4 | |
|---|---|---|
| Size | 27 billion parameters | V4-Flash has 284 billion in total, with 13 billion active per token |
| Licence | Apache 2.0 | MIT |
| Context window | 256K tokens natively | 1M tokens (V4-Flash) |
| Weights | Open | Open |
| Where you can run it | Hosted on NeverMetered, or on your own hardware | DeepSeek's API, other hosts, or your own much larger hardware |
What they cost to use
DeepSeek's API is a cheap per-token option. Off-peak, at the calculator's default workload, a typical day of about 8.5M tokens comes to roughly $8 a month on V4.1 Flash and $34 on V4 Pro, and a busy day of about 86.7M comes to $86 and $340. Peak hours cost double. Those are list-price estimates with an assumed cache hit rate. A flat plan only pays off when your usage is heavy enough: see flat rate versus cheap per-token APIs and the cost calculator.
How to choose
- If you need a 1M-token context window, or you want the model with the most published coding results, look at DeepSeek V4.
- If you want a flat monthly price and several agents running at once, Qwen3.8-27B on a plan priced by parallel streams is the fit. See how parallel streams work.
- If you can't decide, run the same five real tasks through both and compare. The test in the Sonnet comparison works for any pair of models.
Is Qwen3.8-27B better than DeepSeek V4 for coding?
Which is cheaper?
Do you offer DeepSeek?
- Qwen3.8-27B model card (Hugging Face) (checked 13 November 2026)
- DeepSeek-V4-Flash model card, with its V4-Pro comparison table (Hugging Face) (checked 13 November 2026)
- DeepSeek: API pricing (checked 10 November 2026)
- How NeverMetered runs (checked 13 November 2026)