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

Granite 4.2 8B vs Nemotron 3.5 Lightning 30B A3B

Nemotron 3.5 Lightning 30B A3B scores 64.7 (B) on agent readiness against Granite 4.2 8B's 61 (C), and leads in 2 of 4 scored categories. Granite 4.2 8B leads on reach 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 85
  • Documentation and upkeep, 92 against 75

Watch for

No safety results published for it

Nemotron 3.5 Lightning 30B A3B B

Best for Agents on one 24 to 32 GB GPU or Mac that want a fast tool-calling reasoning model with long context and a permissive licence

Ahead on

  • Risk, 75 against 55
  • Agent interface, 90 against 85

Watch for

No safety evaluation results published

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.

Risk Nemotron 3.5 Lightning 30B A3B +20

Granite 4.2 8B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ibm-granite organisation, which IBM's Granite docs and the GitHub README link to (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and the card's licence link resolves. Security programme 5, www.ibm.com/.well-known/security.txt names IBM PSIRT, read for the 3B listing on 4 November 2026 (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

Nemotron 3.5 Lightning 30B A3B 75

File safety earns 25, safetensors only with no Python files, and nothing from the repository runs to load it or parse its output. Provenance earns 15, files in NVIDIA's linked organisation with a hash for every file. Safety evaluation earns 0, since NVIDIA says it evaluated content safety but publishes no results. Agent guidance earns 10, a subcard that names prompt injection and the safeguards to add, without an instruction hierarchy. Licence risk keeps all 15 under OpenMDW-1.1. The security programme earns 10 for the reporting route on the card and NVIDIA's public bulletins.

Documentation and upkeep Granite 4.2 8B +17

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.

Nemotron 3.5 Lightning 30B A3B 75

The model card earns 20, all seven items with limitations in the linked subcard. Training data earns 20, datasets listed with sources and token counts, cut-offs and filtering, and the corpora published. Last change earns 20, counting NVIDIA's own inference code as for the other Nemotron listings. The repositories last changed on 10 September, 53 days ago, and TensorRT-LLM, which the card's serving section runs, changed its Nemotron-H model code on 14 October, 19 days ago. Responsiveness earns 5, one NVIDIA reply across 14 questions. Version policy earns 5 as a first release. File health earns 5, since reports about the card's recipes wait without a reply and the llama.cpp recipe names a quantisation the linked repository doesn't hold.

Reach Granite 4.2 8B +10

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.

Nemotron 3.5 Lightning 30B A3B 85

Memory earns 25, since ggml-org's 18.9 GB Q4_0 GGUF and Ollama's 19 GB nvfp4 build both need under 24 GB with the fifth added. Runtimes earn the full 25 from released vLLM, SGLang, llama.cpp, Transformers, Ollama and LM Studio. Builds earn 10, as NVIDIA's only quantised build is NVFP4. Terms earn 10, because OpenMDW-1.1 is permissive with no threshold or use policy but isn't an OSI licence. Download earns 10, with no gate or account. Hosted earns 5, since NVIDIA's own API serves it and Fireworks hosts it.

Agent interface Nemotron 3.5 Lightning 30B A3B +5

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.

Nemotron 3.5 Lightning 30B A3B 90

The chat template earns 20, a Jinja file in the repository. The tool-calling format earns 25, since the card names the qwen3_coder parser and shows a tool call declared and read back. Trained tool calling earns 20, with tool-use training and several calls per turn in the template. Structured output earns 5, claimed from training with no instructions. Reasoning control earns 10, thinking off per request with runtime parsers that return the reasoning apart. Context earns 10 for up to 1M tokens.

Score by category

CategoryWeight this runGranite 4.2 8BNemotron 3.5 Lightning 30B A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259585Granite 4.2 8B +10
Risk20%205575Nemotron 3.5 Lightning 30B A3B +20
Agent interface10%108590Nemotron 3.5 Lightning 30B A3B +5
Documentation and upkeep10%109275Granite 4.2 8B +17
Negative events≤1500
TotalC 61/100B 64.7/100

Facts side by side

FactGranite 4.2 8BNemotron 3.5 Lightning 30B A3B
KindOpen-weight modelOpen-weight model
VendorIBMNVIDIA
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-11
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.

Nemotron 3.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

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

Nemotron 3.5 Lightning 30B A3B

  1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
  2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
  3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
  4. Use temperature=1.0 and top_p=0.95, as the card says
  5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
  7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory

Questions

Which is better for AI agents, Granite 4.2 8B or Nemotron 3.5 Lightning 30B A3B?

Nemotron 3.5 Lightning 30B A3B scores 64.7 (B) on agent readiness against Granite 4.2 8B's 61 (C), and leads in 2 of 4 scored categories. Granite 4.2 8B leads on reach and documentation and upkeep.

Other comparisons with Granite 4.2 8B or Nemotron 3.5 Lightning 30B A3B

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.