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

Granite 4.2 8B vs Laguna XS 2.1

Granite 4.2 8B and Laguna XS 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C). Both do open-weight models you run yourself.

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

Which one, for what

Granite 4.2 8B C

Best for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 16 GB machine

Ahead on

  • Reach, 95 against 80
  • Documentation and upkeep, 92 against 46

Watch for

No safety results published for it

Laguna XS 2.1 C

Best for Agents that want a fast local coding model on a 32 GB GPU or Mac, with tool calling and a permissive licence.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No reply from Poolside to any discussion, including reports about the tokenizer and remote code

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep Granite 4.2 8B +46

Granite 4.2 8B 92

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (8B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 8B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 20, the last commit, on 20 October 2026, replaced model.safetensors.index.json (titled "granite-4.2 index file fix"), 21 days before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (13 September to 5 November 2026), 4 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 8B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 20 + 20 + 5 + 10 = 92.

Laguna XS 2.1 46

Model card 11 of 20, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 10, the linked report describes sources and filtering and Poolside's S 2.1 post gives the shared November 2025 cut-off. Last change 15, 19 August 2026, 76 days back. Responsiveness 0, Poolside answered none of the 6 discussions. Version policy 5, XS.2 is kept and release notes are dated, but GGUF files were replaced in place without a card note. File health 5, generation config and template disagree on the thinking default and two file reports wait without a reply.

Reach Granite 4.2 8B +15

Granite 4.2 8B 95

Memory 30, IBM's own 4-bit MLX build granite-4.2-8b-q4-mlx is 4.95 GB, and 4.95 GB × 1.2 = 5.9 GB, within 8 GB. Its Q4_0 GGUF is 5.06 GB and Ollama's library build granite4.2:8b (5.3 GB) fits 8 GB too. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 8b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 30 + 25 + 15 + 15 + 10 + 0 = 95.

Laguna XS 2.1 80

Memory 20 of 30, the smallest 4-bit build with an exact size is Poolside's Q4_K_M GGUF at 20.27 GB, the same file as Ollama's default, which needs 32 GB with a fifth added. Runtimes 25, released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the laguna architecture. Builds 15, Poolside publishes FP8, INT4, NVFP4, MLX and GGUF builds. Terms 10, OpenMDW-1.1 is permissive but not OSI-approved. Download 10, nothing is gated. Hosted 0, Poolside's OpenRouter endpoints expired on 31 October 2026 and no other host was found.

Score by category

CategoryWeight this runGranite 4.2 8BLaguna XS 2.1Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259580Granite 4.2 8B +15
Risk20%205555even
Agent interface10%108585even
Documentation and upkeep10%109246Granite 4.2 8B +46
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactGranite 4.2 8BLaguna XS 2.1
KindOpen-weight modelOpen-weight model
VendorIBMPoolside
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-10-202026-08-19
Terms last updatedno document linked2026-07-21
Privacy policy last updatedno document linked2026-07-21
Customer content may train modelsnot read yetyes, with an opt-out
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

Granite 4.2 8B

IBM's mid-size reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 16 GB machine, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.

Laguna XS 2.1

A small coding and agent cousin with 3B active parameters, so it's quick on modest hardware. Poolside's 4-bit GGUF, also Ollama's default, needs about 24 GB, and every major runtime runs it. The main risks are that nobody at Poolside answers its discussions, there are no safety results, and the SGLang route runs repository code.

Before you call either

Granite 4.2 8B

  1. Start it with ollama run granite4.2:8b, or llama-server -hf ibm-granite/granite-4.2-8b-GGUF:Q4_K_M --jinja
  2. With vLLM 0.32.0 or later leave out --reasoning-parser-plugin, since the parser is built in, and use --tool-call-parser qwen3_coder
  3. Thinking is on by default. Pass enable_thinking false to turn it off or low_effort true for short reasoning
  4. The context is 131,072 tokens. The card's 512K extension isn't documented
  5. Validate JSON output yourself, since structured output isn't documented
  6. IBM recommends Granite Guardian beside it to flag risky inputs and outputs

Laguna XS 2.1

  1. Quickest start is ollama run laguna-xs-2.1, 20 GB of files, the same Q4_K_M as Poolside's GGUF
  2. On our reference machine use llama-server -hf poolside/Laguna-XS-2.1-GGUF:Q4_K_M --jinja -c 131072, from a llama.cpp release with the laguna architecture (b11772 has it), or BF16 with vLLM (66.9 GB)
  3. With vLLM use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on a build with vllm-project/vllm#47311, or --tool-call-parser glm47 on older builds
  4. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
  5. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
  6. Sampling per the card is temperature 1.0 and top_k 20
  7. The card warns that Ollama on Apple Silicon may return empty output until llama.cpp#25389 ships
  8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

Which is better for AI agents, Granite 4.2 8B or Laguna XS 2.1?

Granite 4.2 8B and Laguna XS 2.1 score within a point of each other on agent readiness, 61 (C) and 61 (C).

Other comparisons with Granite 4.2 8B or Laguna XS 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.