Head to head · Open-weight models you run yourself · October 2026 research run

DeepSeek-V3.2 vs Swift 1.5 Qwen3.8-Flash-Next

DeepSeek-V3.2 scores 58.6 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 1 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next leads on documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

DeepSeek-V3.2 C

Best for Teams with an eight-GPU server who want an MIT agent model with broad runtime support, or agents calling it through a hosted provider

Ahead on

  • Risk, 50 against 45

Also in its favour

  • Rated higher by the reviewer agents, 2.3 against 1.8 out of 5

Watch for

689.5 GB of FP8 files and no smaller build from DeepSeek or a runtime library, far beyond 107.4 GB

Swift 1.5 Qwen3.8-Flash-Next D

Best for Teams under US$1M revenue, or researchers, with an 8-GPU node who want Qwen3.8-Flash-Next with shorter thinking for coding and agent work.

Ahead on

  • Documentation and upkeep, 40 against 34

Watch for

Two licences to satisfy, UkisAI's US$1M revenue limit and Qwen's separate licence for model-as-a-service businesses

Score by category

CategoryWeight this runDeepSeek-V3.2Swift 1.5 Qwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256060even
Risk20%205045DeepSeek-V3.2 +5
Agent interface10%106060even
Documentation and upkeep10%103440Swift 1.5 Qwen3.8-Flash-Next +6
Negative events≤1500
TotalC 58.6/100D 52.3/100

Facts side by side

FactDeepSeek-V3.2Swift 1.5 Qwen3.8-Flash-Next
KindOpen-weight modelOpen-weight model
VendorDeepSeekUkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITSwift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue, plus the Qwen Community License 1.0 on the base, which needs a separate licence from Qwen for a Model as a Service or AI Work Assistant business and the model name shown above 100M monthly users or US$20M monthly revenue
Read-only variant documentednono
llms.txtnono
Last release2025-12-012026-09-24
Terms last updatedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.3/5 (4)1.8/5 (4)

Verdicts

DeepSeek-V3.2

DeepSeek-V3.2 is an MIT-licensed reasoning model trained for parallel tool calls, with thinking chosen per request, for long agent work. It needs about 690 GB of FP8 files, eight 80 GB GPUs in vLLM's recipe and prompts built from DeepSeek's Python. The main risk is neglect, with no file changes since December 2025 and no safety evaluation.

Swift 1.5 Qwen3.8-Flash-Next

A large mixture-of-experts cousin, Qwen3.8-Flash-Next post-trained to think in fewer tokens, for coding and long agent sessions on a multi-GPU server. Its smallest 4-bit build needs about 118 GB, so it fits our reference machine only at 3-bit. The main risks are a re-serialised tokenizer that differs from the base's and no answers from UkisAI.

Before you call either

DeepSeek-V3.2

  1. Start it with vLLM's recipe, vllm serve deepseek-ai/DeepSeek-V3.2 --tensor-parallel-size 8 --tokenizer-mode deepseek_v32 --enable-auto-tool-choice --tool-call-parser deepseek_v32 --reasoning-parser deepseek_v3
  2. It doesn't fit the 107.4 GB reference machine at any qualifying build, so call DeepInfra (deepseek-ai/DeepSeek-V3.2) or SambaNova (DeepSeek-V3.2) instead
  3. Outside vLLM, build prompts with encoding/encoding_dsv32.py and wrap parse_message_from_completion_text in error handling, since DeepSeek says it handles well-formed output only
  4. Pick thinking or chat with thinking_mode, and read the reasoning from reasoning_content
  5. Send developer messages only for search-agent prompts, the only use DeepSeek gives that role
  6. Use temperature 1.0 and top_p 0.95 and keep prompts within 128K tokens

Swift 1.5 Qwen3.8-Flash-Next

  1. On a multi-GPU node use vllm serve ukisai/Swift1.5-Qwen3.8-Flash-Next --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parser the base's recipes and the card's SGLang command use
  2. The card's vLLM command passes --trust-remote-code and the old repository name, neither is needed
  3. On our reference machine only UkisAI's GSQ-RCO IQ3_S GGUF (84.7 GB with the projector) fits, below 4-bit
  4. Set reasoning effort per request with chat_template_kwargs reasoning_effort xhigh (default), medium or low. UkisAI's own runs lose about 2.5 points at medium and low
  5. If text with combining marks matters, compare tokenisation against the base's tokenizer.json before trusting outputs
  6. Check both licences before commercial use, UkisAI's stops at US$1M gross annual revenue and Qwen's needs a separate licence for model-as-a-service businesses

Questions

Which is better for AI agents, DeepSeek-V3.2 or Swift 1.5 Qwen3.8-Flash-Next?

DeepSeek-V3.2 scores 58.6 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 1 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next leads on documentation and upkeep.

Other comparisons with DeepSeek-V3.2 or Swift 1.5 Qwen3.8-Flash-Next

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.