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

Apertus v1.5 8B vs DeepSeek-V4-Flash-0731

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

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 43

Watch for

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

DeepSeek-V4-Flash-0731 B

Best for Agents or teams with a multi-GPU server, or a provider account, who want DeepSeek's V4 agent model under MIT with a 1M context

Ahead on

  • Reach, 70 against 40

Watch for

The smallest 4-bit build is 156.4 GB, so it needs about 188 GB and doesn't fit a 128 GB machine

Score by category

CategoryWeight this runApertus v1.5 8BDeepSeek-V4-Flash-0731Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254070DeepSeek-V4-Flash-0731 +30
Risk20%207550Apertus v1.5 8B +25
Agent interface10%108575Apertus v1.5 8B +10
Documentation and upkeep10%108443Apertus v1.5 8B +41
Negative events≤1500
TotalC 61/100B 62.4/100

Facts side by side

FactApertus v1.5 8BDeepSeek-V4-Flash-0731
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-07-31
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.5/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-Flash-0731

A long-context agent cousin under MIT with documented tool calls, three reasoning effort levels and support in every major runtime but Ollama. It needs about 190 to 200 GB of memory, though six inference providers serve it. The main risks are prompts built from DeepSeek's Python, no published safety results and no answers in its repository.

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-Flash-0731

  1. vllm serve deepseek-ai/DeepSeek-V4-Flash-0731 --trust-remote-code --kv-cache-dtype fp8 --block-size 256 --data-parallel-size 4 --enable-expert-parallel --moe-backend deep_gemm_mega_moe --attention-config '{"use_fp4_indexer_cache": true}' --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"greedy"}' --tokenizer-mode deepseek_v4 --tool-call-parser deepseek_v4 --enable-auto-tool-choice --reasoning-parser deepseek_v4 (the card's 4x GB300 example plus the parser flags from vLLM's recipe)
  2. Build prompts with encoding_dsv4.py, deepseek-recipe's V4 encoder or vLLM's --tokenizer-mode deepseek_v4, since the repository has no Jinja template
  3. Tool calls come back in a DSML tool_calls block with invoke elements, string parameters carry string="true" and JSON values string="false"
  4. Set temperature 1.0 and top_p 0.95 for agent work, and allow up to 384K output tokens at reasoning effort high or max
  5. Without the hardware, call it through a Hugging Face inference provider (Together, DeepInfra, Novita, Baseten, Scaleway, Featherless), not DeepSeek's API, where deepseek-v4-flash now means V4.1 Flash
  6. LM Studio's library build is a 156.4 GB MXFP4 GGUF and LM Studio states 156 GB minimum system memory

Questions

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

DeepSeek-V4-Flash-0731 scores 62.4 (B) on agent readiness against Apertus v1.5 8B's 61 (C), and leads in 1 of 4 scored categories. Apertus v1.5 8B leads on risk, agent interface and documentation and upkeep.

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

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.