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

Granite 4.2 8B vs Qwen3.8-27B

Qwen3.8-27B scores 68.6 (B) on agent readiness against Granite 4.2 8B's 61 (C), and leads in 0 of 4 scored categories. Granite 4.2 8B leads on reach, 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 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 90
  • Agent interface, 85 against 70
  • Documentation and upkeep, 92 against 36

Watch for

No safety results published for it

Qwen3.8-27B B

Best for Agents that want a capable open model with vision on one 24 to 32 GB GPU or Mac, with the widest runtime support and a plain licence.

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

Watch for

No safety results, prompt-injection guidance or security contact

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 +56

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.

Qwen3.8-27B 36

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 0, not described. Last change 15, the files last changed on 14 August 2026, 79 days before this check, and Qwen's GitHub repository for the model holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports, recounted on 1 November. Version policy 5, earlier 27B models stay in their own repositories without dated notes. File health 5, the files agree with the card but reports about the template and structured output wait without a reply.

Agent interface Granite 4.2 8B +15

Granite 4.2 8B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Qwen3.8-27B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the format lives only in the template and the parser name only in serving commands, Alibaba doesn't describe how tools are declared or returned. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking turns off per request, reasoning_effort budgets it and the card shows the reasoning coming back in reasoning_content. Context 10, 262,144 tokens native.

Reach Granite 4.2 8B +5

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.

Qwen3.8-27B 90

Memory 25 of 30, Ollama's smallest 4-bit build is 18 GB, or 21.6 GB with a fifth added, which fits 24 GB. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang and Transformers all run the qwen3_5 architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, seven inference providers are live for it on Hugging Face on 1 November, though Qwen Cloud's own version is still described as coming soon.

Score by category

CategoryWeight this runGranite 4.2 8BQwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259590Granite 4.2 8B +5
Risk20%205555even
Agent interface10%108570Granite 4.2 8B +15
Documentation and upkeep10%109236Granite 4.2 8B +56
Negative events≤1500
TotalC 61/100B 68.6/100

Facts side by side

FactGranite 4.2 8BQwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorIBMAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-202026-08-14
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/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.

Qwen3.8-27B

A dense cousin for coding and agent work with image and video input that runs almost anywhere. Ollama's 4-bit build needs about 22 GB, and seven providers host it for agents without the hardware. The main risk is that nobody at Alibaba answers, there are no safety results or agent guidance, and the tool format is only in the template.

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

Qwen3.8-27B

  1. Quickest start is ollama run qwen3.8, about 18 GB of files
  2. On our reference machine use BF16 with vllm serve Qwen/Qwen3.8-27B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, since FP8 on gfx1151 isn't documented
  3. Use the qwen3_coder tool parser, SGLang's cookbook says the Hermes parser leaves its calls unparsed
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, and read the reasoning from reasoning_content
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
  7. Preserved thinking keeps earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  8. Turn on YaRN only beyond 262,144 tokens, the card warns static YaRN can cost quality on short texts
  9. 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 Qwen3.8-27B?

Qwen3.8-27B scores 68.6 (B) on agent readiness against Granite 4.2 8B's 61 (C), and leads in 0 of 4 scored categories. Granite 4.2 8B leads on reach, agent interface and documentation and upkeep.

Other comparisons with Granite 4.2 8B or Qwen3.8-27B

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.