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

Apertus v1.5 8B vs Laguna S 2.1

Apertus v1.5 8B and Laguna S 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Laguna S 2.1 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 55
  • Documentation and upkeep, 84 against 41

Also in its favour

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

Watch for

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

Laguna S 2.1 C

Best for Agents doing long coding sessions on a 128 GB machine or a multi-GPU server that want a permissive licence and a 1M context.

Ahead on

  • Reach, 75 against 40

Watch for

No reply from Poolside to any of 34 discussions, many of them reports about thinking and tool calls

Score by category

CategoryWeight this runApertus v1.5 8BLaguna S 2.1Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254075Laguna S 2.1 +35
Risk20%207555Apertus v1.5 8B +20
Agent interface10%108585even
Documentation and upkeep10%108441Apertus v1.5 8B +43
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApertus v1.5 8BLaguna S 2.1
KindOpen-weight modelOpen-weight model
VendorSwiss AI Initiative (EPFL and ETH Zurich)Poolside
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 gateOpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-10-142026-08-19
Terms last updated
Privacy policy last updatedno 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.3/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.

Laguna S 2.1

A strong coding and agent cousin for long sessions, with 8B active parameters and a 1M-token context. At 4-bit it needs a 96 to 128 GB machine, tight on a 128 GB one. The main risks are that nobody at Poolside answers its many reports, there are no safety results, and a build card misdescribes its file.

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

Laguna S 2.1

  1. Quickest start is ollama run laguna-s-2.1, 96 GB for the default Q4_K_M, or the 66 GB nvfp4 tag on Apple Silicon
  2. On our reference machine try llama-server -hf poolside/Laguna-S-2.1-GGUF:Q4_K_M --jinja -c 65536, from a llama.cpp release with the laguna architecture (b11772 has it). The 96 GB file leaves little room for context in 107.4 GB
  3. With vLLM or SGLang use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1, and with TensorRT-LLM --tool_parser poolside_v1 --reasoning_parser laguna
  4. Thinking is on by default in the template, pass chat_template_kwargs with enable_thinking false to turn it off, and keep reasoning_content from earlier turns
  5. The GGUFs ship set to 262,144 tokens. For 1M with llama.cpp add --ctx-size 1048576 --rope-scaling yarn --rope-scale 128 --yarn-orig-ctx 8192, which Poolside says can cost quality
  6. Sampling per the generation config is temperature 1.0 and top_k 20, and Poolside suggests temperature 0.7 and top_p 0.95 at 1M
  7. Expect occasional tool-schema slips in harnesses unlike Poolside's own, and validate JSON arguments, which Poolside lists as known limitations

Questions

Which is better for AI agents, Apertus v1.5 8B or Laguna S 2.1?

Apertus v1.5 8B and Laguna S 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Laguna S 2.1 leads on reach.

Other comparisons with Apertus v1.5 8B or Laguna S 2.1

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.