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

Apertus v1.5 8B vs DeepSeek V4.1 Flash

Apertus v1.5 8B scores 61 (C) on agent readiness against DeepSeek V4.1 Flash's 59 (C), and leads in 3 of 4 scored categories. DeepSeek V4.1 Flash leads on reach. 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

Apertus v1.5 8B C

Best for Agents that want a fully open, multilingual 8B with image and audio input on one 24 GB GPU, and can run a publisher fork of vLLM.

Ahead on

  • Risk, 75 against 50
  • Agent interface, 85 against 75
  • Documentation and upkeep, 84 against 48

Watch for

No released runtime supports it, only Swiss AI's forks of vLLM and Transformers

DeepSeek V4.1 Flash C

Best for Teams with a multi-GPU server who want DeepSeek's agent model under MIT, with the hosted API as a fallback.

Ahead on

  • Reach, 50 against 40

Watch for

510.3 GB of files and no smaller build anywhere, so it won't fit the 107.4 GB reference machine

Score by category

CategoryWeight this runApertus v1.5 8BDeepSeek V4.1 FlashEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254050DeepSeek V4.1 Flash +10
Risk20%207550Apertus v1.5 8B +25
Agent interface10%108575Apertus v1.5 8B +10
Documentation and upkeep10%108448Apertus v1.5 8B +36
Negative events≤1500
TotalC 61/100C 59/100

Facts side by side

FactApertus v1.5 8BDeepSeek V4.1 Flash
KindOpen-weight modelOpen-weight model
VendorSwiss AI Initiative (EPFL and ETH Zurich)DeepSeek
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0, with the Apertus Acceptable Use Policy (v1.5, 14 July 2026) accepted at the download gateMIT
Read-only variant documentednono
llms.txtnono
Last release2026-10-142026-10-17
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.8/5 (4)2.8/5 (4)

Verdicts

Apertus v1.5 8B

A fully open 8B cousin, training data included, for multilingual chat and tool calls with images and audio in. It needs about 22 GB in BF16 and Swiss AI's own vLLM or Transformers fork, since no released runtime supports it. The main risks are a gated download with a policy to pass on and tools that fail with thinking on.

DeepSeek V4.1 Flash

A large multimodal agent model with a 1M-token context, documented tool calls, JSON Schema output and a reasoning budget, under MIT. It needs about 612 GB of memory across several GPUs in vLLM or SGLang. The main risks are prompts built from DeepSeek's code rather than a template, no published safety results and no answers in its repositories.

Before you call either

Apertus v1.5 8B

  1. Accept the terms on the card and set HF_TOKEN before downloading
  2. Use Swiss AI's Docker image ghcr.io/swiss-ai/vllm_apertus_1.5_release, since stock vLLM and Transformers don't load Apertus1p5ForConditionalGeneration yet
  3. Serve with --chat-template-content-format string --enable-auto-tool-choice --tool-call-parser apertus for tools, and leave thinking off when you need tools
  4. For thinking, set --reasoning-parser apertus and --default-chat-template-kwargs.enable_thinking true, and budget max tokens generously
  5. Audio is resampled to 24 kHz and costs 40 tokens a second, and video must be passed as frames
  6. Don't cast the loaded model with .half(), the image and audio tokenizers must stay in F32
  7. If you redistribute the weights, the policy says you must pass it on and get the recipient's express assent

DeepSeek V4.1 Flash

  1. DeepSeek's reference run is its inference folder, convert.py with --model-parallel 8 --expert-dtype fp4, then torchrun --nproc-per-node 8 generate.py --ckpt-path "$SAVE_PATH" --config config.json --interactive
  2. In vLLM 0.32.0 the parsers are named deepseek_v41 for both --tool-call-parser and --reasoning-parser. That's vLLM's naming, DeepSeek doesn't document a vLLM command
  3. Build prompts with encoding.py or pip install deepseek-recipe, not the September repository's chat_template.jinja, which an open pull request says trails the 16 October encoding
  4. Tool calls come back in a DSML calls block with a space before calls, invoke and parameter, unlike V4
  5. Set reasoning_effort to 1 to 100, or low, high or max (50, 75, 100), in thinking mode only. Default is 75
  6. Sample at temperature 1.0 and top_p 1.0 and allow 256K or more output tokens, as the card recommends
  7. Without the hardware, call DeepSeek's API as deepseek-flash, which serves this exact update

Questions

Which is better for AI agents, Apertus v1.5 8B or DeepSeek V4.1 Flash?

Apertus v1.5 8B scores 61 (C) on agent readiness against DeepSeek V4.1 Flash's 59 (C), and leads in 3 of 4 scored categories. DeepSeek V4.1 Flash leads on reach.

Other comparisons with Apertus v1.5 8B or DeepSeek V4.1 Flash

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.