At a glance: IBM Granite 4.1, released April 29, 2026. Ten-model family: language (3B/8B/30B), vision (4B), speech (2B), safety (Guardian 8B), embeddings. Apache 2.0. The 8B language model outperforms IBM’s prior 32B MoE. 512K training context. HumanEval 85.37%, BFCL v3 tool calling 68.27%. OpenRouter at $0.05/$0.10 per M tokens. IBM offers uncapped IP indemnification on watsonx. Part of our AI Models & Companies reviews.


IBM’s AI story in 2026 is about one thing: making the enterprise bet pay off.

When IBM launched the Watson brand in the 2010s, the pitch was transformative AI for Fortune 500 companies. When Watson stumbled in healthcare and legal — high-profile failures documented across the press — IBM rebuilt around a different strategy: smaller, controllable, enterprise-safe models paired with the infrastructure and legal protections that large organizations actually need before they’ll sign a purchase order.

Granite 4.1 is the most complete expression of that strategy yet. Released April 29, 2026, it is not a single model — it is a coordinated family of ten models covering language, vision, speech, safety classification, and embeddings, all under Apache 2.0, all supported by IBM’s unusual enterprise guarantee: uncapped intellectual property indemnification for customers running Granite through watsonx.

The headline benchmark claim — that the Granite 4.1 8B dense model outperforms IBM’s own prior 32B Mixture-of-Experts (MoE) model — is genuine, and it matters for enterprise buyers who want capable models that fit on reasonable hardware. Whether Granite 4.1 competes at the reasoning frontier is a different question. It does not. But that may not be what IBM’s target customers are buying.


Release Context

Granite 4.1 was announced on April 29, 2026 via the IBM Research blog (“Introducing the IBM Granite 4.1 family of models”) and simultaneously published on HuggingFace under the ibm-granite organization.

This was a full-family release: IBM dropped all ten models — language, vision, speech, guardian, embeddings — on the same day. That coordinated release pattern is itself a strategic statement. IBM is not releasing isolated models and hoping developers assemble a stack. It is offering a pre-integrated system with IBM support contracts and enterprise warranties behind it.

The release landed alongside confirmation of availability on Microsoft Azure AI Foundry, which signals that the Microsoft–IBM enterprise partnership remains active and that Granite 4.1 will appear in the AI-powered features of Azure enterprise products.

Predecessor context: Granite 4.1 follows Granite 4.0, which used a Mixture-of-Experts architecture (a 32B total / 9B active model designated Granite 4.0-H-Small). Granite 4.1 explicitly reverses this architectural choice — returning to dense transformers — and the benchmarks suggest the switch paid off. The 4.1 8B dense model meets or exceeds the 4.0 32B MoE on most standard evaluations.

It also follows Granite 3.x, which topped out at 8B and offered 128K context windows. Granite 4.1 adds a 30B option and extends context training to 512K tokens.


Architecture

Dense, Not MoE — Again

Granite 4.1’s language models are dense, decoder-only transformers. All parameters are active during every inference call. This is a deliberate return from Granite 4.0’s MoE experiment.

The industry trend in 2026 runs strongly toward MoE architectures — DeepSeek V4, Mistral Small 4, Qwen 3.6, Meta’s Llama 4 Scout — all activate a fraction of total parameters per token to reduce inference cost. IBM’s choice to go dense, and to make that choice explicit in the release materials, is a statement about where Granite 4.1 fits.

Dense models carry advantages that matter in enterprise settings:

  • Simpler deployment: No expert-routing logic, no concern about load imbalance across experts, straightforward weight sharding
  • Easier fine-tuning: No routing behavior to destabilize during LoRA or full-parameter training
  • Consistent quality on long inputs: MoE routing can under-activate specialized experts on corner-case prompts; dense models have no such failure mode
  • Better quantization fidelity: Dense architecture quantizes more predictably than MoEs with heterogeneous expert weight distributions

The tradeoff: a dense 8B is more expensive to run than an 8B-active MoE drawn from a 32B pool, because the dense model actually uses all 8B on each token. IBM mitigated this by releasing FP8-quantized variants that roughly halve VRAM and throughput costs.

Language Model Specifications

Three sizes cover different deployment scenarios:

SpecificationGranite 4.1 3BGranite 4.1 8BGranite 4.1 30B
Parameters3 billion8 billion30 billion
Embedding dim2,5604,0964,096
Layers404064
Attention heads403232
KV heads (GQA)888
MLP hidden8,19212,80032,768
Native context131,072 tokens131,072 tokens131,072 tokens
Training context512K (staged)512K (staged)512K (staged)
Languages121212

All three use Grouped Query Attention (GQA) with 8 KV heads, reducing KV-cache memory at long contexts. Positional encoding is RoPE. Activations are SwiGLU. Normalization is RMSNorm with shared input/output embeddings.

On the 512K context window: IBM’s headline number requires some precision. The native inference context shown in HuggingFace model cards is 131,072 tokens (128K). The 512K figure refers to the training extension — IBM trained through progressively longer contexts (4K → 32K → 128K → 512K) in Phase 5. At the extreme end of that range, quality degrades. IBM’s own published long-context benchmark (RULER) only goes to 128K, and the 30B scores 76.7 at that limit. For practical planning: native high-quality context is around 128K, with 512K theoretically available for applications where some degradation is acceptable.

Languages: 12 — English, German, Spanish, French, Japanese, Portuguese, Arabic, Czech, Italian, Korean, Dutch, Chinese.


The Ten-Model Family

IBM released Granite 4.1 as a coordinated system, not a standalone model drop. The full family:

Language (Primary Models)

ModelSizesPurpose
granite-4.1-3b3B base + instruct + FP8Edge, latency-sensitive, resource-constrained
granite-4.1-8b8B base + instruct + FP8Primary API/agentic workhorse
granite-4.1-30b30B base + instructHigh-quality long-form, complex instruction following

The 8B is IBM’s primary offering — it is the model priced on OpenRouter, the one mentioned in Microsoft’s Azure Foundry announcement, and the one IBM’s marketing centers on with the “beats 32B MoE” benchmark claim.

Granite Vision 4.1 4B

A 4B multimodal model built from the Granite 4.1 3B base plus a SigLIP2 vision encoder (google/siglip2-so400m-patch16-384) connected via IBM’s “Deepstack” feature injection at 8 points across LLM layers.

The vision model is specialized for structured document extraction: tables, charts, key-value pairs, forms. IBM trained it using ChartNet, a newly released dataset of 1M+ chart samples. It is not a general visual reasoning model — it excels at the enterprise document processing tasks IBM’s consulting clients actually need.

Vision is English-only, image + text input, and available via HuggingFace (ibm-granite/granite-vision-4.1-4b).

Published benchmarks (Vision 4.1 4B):

  • VAREX KVP extraction: 94.2% exact match (zero-shot) — competitive with much larger closed models
  • ParseBench Mean: 39.45 (Text Content: 64.43, Chart: 47.47, Table: 63.81)

Granite Speech 4.1 2B

Three sub-variants: 2B, 2B Plus, and 2B NAR. Multilingual automatic speech recognition and translation.

Published benchmark:

  • OpenASR Leaderboard WER: 5.33% — top-tier word error rate

Granite Guardian 4.1 8B

IBM’s safety classifier, updated from Guardian 3.3 8B. Used for pre- and post-generation safety checks, bias detection, and policy enforcement in enterprise deployments. Integrates into watsonx Prompt Lab pipelines.

Published benchmark:

  • SALAD-Bench: 95.80% (8B language model), 96.41% (30B) — safety classification quality

Granite Embedding Multilingual R2

97M parameters. 200+ languages. Designed for cross-lingual RAG and retrieval applications in enterprise deployments where documents arrive in many languages. Released alongside the main family.


Training

Pre-Training: ~15 Trillion Tokens

IBM trained Granite 4.1’s language models on approximately 15 trillion tokens using a five-phase pipeline on a CoreWeave NVIDIA GB200 NVL72 cluster (72-GPU NVLink racks, NDR 400 Gb/s InfiniBand).

PhaseTokensComposition
1: General pre-training~10TCommonCrawl 59%, Code 20%, Math 7%, Technical 10.5%, Multilingual 2%, Domain 1.5%
2: Math/Code boost~2TMath raised to 35%, Code to 30%
3: High-quality annealing~2TChain-of-thought + instruction data introduced; exponential LR decay
4: Refinement~0.5TCommonCrawl-HQ 40%, Code 20%, Math 20%; linear LR decay to zero
5: Long-context extensionStagedBooks 80% + Code 20%; progressive 4K→32K→128K→512K training; model merging after each stage

The Phase 5 long-context approach — training on books and code at progressively longer sequence lengths, then merging checkpoints — is a thoughtful method for extending context without destabilizing the core model. IBM reports this achieves the 512K training context without the catastrophic quality degradation seen in naive long-context fine-tuning.

Post-Training: 4-Stage RL Pipeline

IBM’s post-training is notably sophisticated. It uses ~4.1 million SFT samples curated via LLM-as-Judge (6-dimensional scoring), with hard rejection rules for hallucinations and global deduplication.

The RL pipeline uses GRPO + DAPO loss across four stages:

StageFocusKey result
1: Multi-domain RLMath, science, logic, tool calling, SQL, temporal reasoning, chatBroad capability reinforcement
2: RLHFPreference data~18.9-point AlpacaEval improvement vs. SFT baseline
3: Identity/knowledge RLModel calibration, self-knowledgeReduces hallucination and overconfidence
4: Math RLMathematical reasoning recoveryRecovers ~3.8 pts GSM8K and ~23.5 pts DeepMind Math lost during RLHF

The Stage 4 recovery loop is a telling engineering detail. RLHF (Stage 2) improved instruction following and preference alignment but degraded math performance — a known phenomenon in RL-from-human-feedback. IBM explicitly added a Stage 4 to recover what RLHF lost on math benchmarks. This kind of multi-stage recovery training appears in other frontier labs’ post-training pipelines, and seeing it documented in Granite’s technical materials is a signal that IBM’s research team is working at a serious level.


Benchmarks

IBM’s benchmarks are self-reported. No independent third-party evaluation table comparing Granite 4.1 against Llama 3.3, Qwen 2.5, or Gemma 4 was published at time of writing. The numbers below come from IBM Research’s own release materials.

Language Models (Instruct)

Benchmark3B8B30BNotes
MMLU (5-shot)67.0273.8480.16Standard knowledge breadth
MMLU-Pro (5-shot CoT)49.8355.9964.09Harder multi-step MMLU variant
BBH (3-shot CoT)75.8380.5183.74Chain-of-thought reasoning
AGI Eval (0-shot CoT)72.4377.80Exam-style reasoning
GPQA (0-shot CoT)41.9645.76Expert-level science
SimpleQA4.826.81Parametric factual recall
GSM8K (8-shot)86.8892.4994.16Grade-school math
Minerva Math (0-shot CoT)80.1081.32Olympiad-level math
DeepMind Math (0-shot CoT)64.6480.0781.93Mathematical reasoning
HumanEval (pass@1)79.2785.3788.41Python code generation
HumanEval+79.8885.37Harder HumanEval
MBPP87.30Multi-language coding
MBPP+73.81Harder MBPP
BFCL v3 (tool calling)60.8068.2773.68Function/tool calling
AlpacaEval 2.038.5750.0856.16Instruction following
IFEval Avg87.0689.65Instruction format following
ArenaHard68.9871.02Preference-based quality
MTBench Avg8.618.61Multi-turn conversation
MMMLU (multilingual)73.71Cross-lingual MMLU

Long-Context (RULER benchmark):

Model32K64K128K
3B75.066.658.0
8B83.679.173.0
30B85.284.676.7

Reading the Benchmarks

Strengths that stand out:

  • HumanEval 85.37% (8B) — competitive with models in larger size classes. Code generation quality is a genuine priority in this release, consistent with IBM’s enterprise developer focus.
  • BFCL v3 68.27% (8B) — tool calling and function orchestration is where IBM explicitly claims leadership for sub-30B models. This benchmark measures whether a model can correctly call external tools with proper JSON payloads and handle multi-turn tool interactions. For agentic pipelines that depend on reliable function calling, 68.27 is a meaningful number.
  • GSM8K 92.49% (8B) — strong arithmetic and grade-school math, useful for finance and operations tasks.
  • IFEval 87.06% (8B) — instruction format following is critical for enterprise pipelines that specify exact output structure (JSON schemas, structured reports, templated responses).

Weaknesses worth noting:

  • GPQA Diamond 41.96% (8B) — expert-level science and reasoning is weak. This benchmark measures PhD-level physics, chemistry, and biology reasoning. At 41.96, Granite 4.1 8B is below the human expert baseline (~70%) and far behind reasoning-optimized models like Qwen3.6-Max-Preview (86.0%) or Gemini 3.1 Pro (94.3%). IBM is not positioning Granite 4.1 as a reasoning frontier model — but developers considering it for scientific or research use cases should factor this in.
  • SimpleQA 4.82% (8B) — SimpleQA measures factual recall from the model’s own parametric memory (no retrieval). A score near the floor means Granite 4.1 8B struggles to reliably answer factual questions from memory alone. IBM’s answer is RAG — pair the model with a retrieval system. For enterprise use cases where retrieval is always available, this matters less. For use cases where the model must “know” things without looking them up, this is a real limitation.
  • No SWE-Bench score — IBM did not publish a SWE-Bench Verified score for Granite 4.1. This omission is notable given that SWE-Bench has become the standard measure of real-world software engineering capability. It does not mean the score is bad — IBM may have chosen not to prioritize the benchmark — but the absence makes direct comparison with Mistral Medium 3.5 (77.6%) or Claude 4 harder.

The 8B-beats-32B-MoE claim: IBM’s headline says Granite 4.1 8B matches or outperforms the prior Granite 4.0 32B MoE. Based on the benchmark tables IBM published, this appears accurate for coding (HumanEval), instruction following (IFEval), and tool calling (BFCL v3). The claim is internally validated, not independently verified — but there is no obvious reason to doubt it given the genuine training improvements in 4.1.


Licensing

Apache 2.0 — fully permissive, no commercial restrictions, no revenue caps, no authorization required, attribution optional.

This means:

  • Fine-tune freely
  • Deploy commercially with no licensing fees
  • Build products on top without disclosing the model in use
  • No email to IBM required for large deployments (contrast: some other open model licenses require authorization at commercial scale)

This matches the licensing of other IBM Granite models (3.x series) and aligns IBM with the genuinely open end of the open-weight spectrum — Apache 2.0 is the most permissive common license in use, shared with Llama 4 Scout, Arcee Trinity, and the broader DeepSeek family.

Enterprise IP Indemnification

This is Granite 4.1’s most distinctive enterprise feature, and it is not discussed in most coverage of the release.

IBM provides uncapped third-party intellectual property indemnification for content generated through Granite models on watsonx. If a customer is sued because AI-generated content from a Granite model infringes on a third party’s IP — copyright, patents, trade secrets — IBM will defend the customer and cover the costs, without a cap on IBM’s liability.

This is genuinely unusual. Most LLM providers (OpenAI, Anthropic, Google, Mistral) provide limited or no IP indemnification, or cap their liability at the customer’s contract value. IBM offers this because:

  1. IBM’s enterprise customers (banks, hospitals, government contractors) cannot accept unlimited legal exposure from AI output
  2. IBM trained Granite on curated, legally vetted data from the start — they have auditable provenance records
  3. IBM’s legal team is sized and resourced to defend IP claims in a way that startups are not

For a large enterprise running AI at scale, the difference between “maybe we’re liable” and “IBM is contractually obligated to defend us” can be the difference between an approved AI initiative and a stalled one stuck in legal review.

Cryptographic Weight Signing

IBM signs all Granite model weights cryptographically. Customers and regulators can verify that the deployed model is identical to the IBM-released weights — no tampering, no unauthorized modification.

In regulated industries where AI audit trails are required (financial services, healthcare, defense), this matters.


Pricing

OpenRouter (8B)

DirectionPrice per million tokens
Input$0.05
Output$0.10

At $0.10/M output tokens, Granite 4.1 8B is among the cheapest capable language models available via API. For comparison:

ModelOutput price (per M tokens)
Granite 4.1 8B (OpenRouter)$0.10
Arcee Trinity Large (Arcee Cloud)$0.90
Mistral Medium 3.5 (La Plateforme)$7.50
Claude 4.5 Opus (Anthropic API)~$15.00

At these prices, Granite 4.1 8B is effectively a commodity model. Developers building high-volume pipelines — document extraction, code review automation, structured data parsing — can run substantial workloads at very low cost.

IBM watsonx

Pricing via IBM watsonx is in Resource Units (1 RU = 1,000 tokens), billed pay-as-you-go or via reserved hourly hosting. Specific per-token rates for Granite 4.1 were not confirmed from public pricing pages at time of writing. Enterprise pricing is typically negotiated with IBM sales for contract customers.


Self-Hosting

All Granite 4.1 models are on HuggingFace under ibm-granite:

ModelHuggingFace path
Language 3B (instruct)ibm-granite/granite-4.1-3b-instruct
Language 8B (instruct)ibm-granite/granite-4.1-8b-instruct
Language 8B (FP8)ibm-granite/granite-4.1-8b-fp8
Language 30B (instruct)ibm-granite/granite-4.1-30b-instruct
Vision 4Bibm-granite/granite-vision-4.1-4b
Guardian 8Bibm-granite/granite-guardian-4.1-8b

Supported inference runtimes: vLLM, SGLang, llama.cpp, Ollama, LM Studio, HuggingFace Inference Endpoints.

Hardware requirements (approximate):

ModelMinimumComfortable
3B BF168GB VRAM12GB
3B FP84GB VRAM6GB
8B BF1616GB VRAM24GB
8B FP88GB VRAM12GB
30B BF162×A100 80GB4×A100
30BA100 80GB (4-bit)2×RTX 4090

The 8B FP8 variant fitting in 8–12GB VRAM opens Granite 4.1’s primary model to a large range of consumer and workstation GPUs. For teams self-hosting their enterprise stack, this is a meaningful deployment option.


What’s New vs. Granite 3.x and 4.0

vs. Granite 3.x:

DimensionGranite 3.xGranite 4.1
Max size8B30B
Native context128K131K (+ 512K training ext.)
Post-trainingBasic alignment4-stage GRPO + DAPO RL
Vision modelGuardian onlyVision 4B + Guardian 4.1
SpeechNot includedSpeech 4B (WER 5.33%)
Context RULER (8B, 128K)Not benchmarked here73.0

vs. Granite 4.0 (MoE):

DimensionGranite 4.0 (32B MoE)Granite 4.1 8B (dense)
Total params32B8B
Active params/token~9B8B
ArchitectureMoEDense
HumanEval (approx)Lower85.37
BFCL v3 (approx)Lower68.27
Deployment complexityHigher (expert routing)Lower
Fine-tuning difficultyHigherLower

IBM’s decision to revert from MoE to dense was validated by these numbers. The 4.1 8B dense model is smaller, simpler to deploy, easier to fine-tune, and benchmarks higher than the 4.0 architecture at a similar active-parameter count. In 2025, MoE was the architecturally fashionable choice. In 2026, IBM is demonstrating that dense training at scale — 15T tokens, multi-stage RL — can recover and exceed MoE efficiency without the routing overhead.


Where Granite 4.1 Falls Short

Not a Reasoning Model

Granite 4.1 has no “thinking mode,” extended chain-of-thought, or reasoning-time compute scaling. GPQA Diamond at 41.96% (8B) sits well below the human expert baseline (~70%) and far below models with dedicated reasoning capabilities:

ModelGPQA Diamond
Claude Opus 4.794.2%
Gemini 3.1 Pro94.3%
Qwen3.6-Max-Preview86.0%
Arcee Trinity Large Thinking~72–75%
Granite 4.1 8B41.96%
Granite 4.1 30B45.76%

For scientific research, complex reasoning chains, or tasks requiring step-by-step inference across many logical dependencies, Granite 4.1 is not the right tool. IBM’s documentation scopes it explicitly for enterprise agentic workflows — document extraction, code generation, tool calling, structured retrieval — not for reasoning-intensive tasks.

SimpleQA Factual Recall Is Poor

SimpleQA at 4.82% (8B) means Granite 4.1 cannot reliably answer factual questions from memory. IBM’s recommended architecture uses Granite as the reasoning/generation layer on top of a retrieval system. In RAG setups, this works fine — the model does not need to “know” facts, it needs to extract and format them from provided context. But developers building without retrieval infrastructure should be aware that Granite 4.1 will hallucinate factual details at a higher rate than models with stronger parametric memory.

Benchmark Comparisons Are IBM-Only

IBM published self-reported benchmarks comparing Granite 4.1 to Granite 4.0. The release materials do not include head-to-head tables against Llama 3.3 70B, Qwen 2.5 14B, Gemma 4 27B, or other current competitive models. Third-party evaluations were not available at time of writing.

The numbers IBM reports are plausible given the architecture and training pipeline. But developers selecting between Granite 4.1 and a competitor should run their own domain-specific evaluations rather than relying on IBM’s relative claims.

Vision Is Narrow and English-Only

Granite Vision 4.1 4B excels at structured document extraction — VAREX KVP at 94.2% is impressive — but it is not a general-purpose vision model. It does not handle natural images, video frames, or visual reasoning tasks the way GPT-4o or Claude 4 do. And it is English-only, which limits it for multinational enterprise deployments with documents in other languages.


Who Should Use IBM Granite 4.1

Strong fit:

  • Enterprise teams running AI on sensitive data: Apache 2.0 license + IBM IP indemnity + cryptographic weight signing = the lowest-risk path to compliant AI deployment in regulated industries
  • Developers building agentic pipelines: BFCL v3 68.27% tool calling means Granite 4.1 8B reliably orchestrates multi-tool workflows; IFEval 87.06% means it follows structured output requirements
  • Budget-constrained high-volume use cases: $0.10/M output tokens on OpenRouter is a commodity price. Document classification, code review, structured extraction, summarization at scale are all viable at this price
  • Self-hosting teams: 8B FP8 fits in 8–12GB VRAM; Apache 2.0 with no runtime restrictions; runs on llama.cpp, Ollama, vLLM
  • watsonx/Azure enterprise customers: Granite 4.1 is the native model for IBM’s enterprise AI stack. If you’re already in either ecosystem, using Granite 4.1 gives you IP indemnification and integrated support that third-party models don’t carry
  • Document extraction workflows: Granite Vision 4.1 4B at 94.2% VAREX KVP extraction competes with much larger closed models for structured extraction tasks

Poor fit:

  • Scientific reasoning, research synthesis, complex inference: GPQA at 41.96% is not competitive. Use a reasoning-capable model
  • Knowledge-intensive QA without retrieval: SimpleQA at 4.82% means high hallucination risk on factual recall tasks
  • Visual understanding beyond structured documents: Use GPT-4o, Claude 4, or Gemini 3.1 Pro for general vision tasks
  • Frontier model comparisons: Granite 4.1 is an enterprise-grade capable model, not a frontier reasoning model. That is IBM’s intentional positioning, not a failure

IBM’s Enterprise Positioning

Granite 4.1 makes the most sense understood as an enterprise infrastructure component, not a frontier AI research model.

IBM’s pitch to large organizations is a complete stack:

  • Models: Granite language, vision, speech, safety — Apache 2.0
  • Platform: watsonx.ai — managed hosting, monitoring, explainability tools
  • Legal protection: Uncapped IP indemnification
  • Compliance: Cryptographically signed weights, auditable training data provenance
  • Integration: Azure AI Foundry, IBM Consulting deployments, existing enterprise contracts

For a large bank or hospital system that needs to put AI into production — and have someone they can sue if things go wrong — IBM’s stack is uniquely well-positioned. No AI startup offers uncapped IP indemnification backed by a company with IBM’s balance sheet and legal infrastructure.

The question is whether that complete stack justifies IBM’s enterprise pricing when capable open alternatives exist at commodity prices on OpenRouter. For regulated-industry customers where the legal protection is table stakes, the answer is likely yes. For developers who just need good API access to an efficient small model, the OpenRouter path at $0.10/M output is attractive on its own.


Rating: 4 / 5

The case for Granite 4.1:

IBM shipped a genuinely well-engineered family. The 8B dense model beating the prior 32B MoE is a real result supported by published numbers. The Apache 2.0 license is the best possible, and IBM’s IP indemnification is unique in the industry. The training pipeline — 15T tokens, five phases, four-stage RL — shows serious investment. Tool calling at BFCL v3 68.27% and code at HumanEval 85.37% are competitive for the model size. OpenRouter pricing at $0.10/M output makes it accessible. The ten-model family covering language, vision, speech, safety, and embeddings is a coherent enterprise system.

The case for caution:

GPQA at 41.96% means Granite 4.1 is not a reasoning model and should not be used as one. SimpleQA at 4.82% means factual recall is poor without retrieval. IBM’s benchmark tables compare Granite to Granite — there are no head-to-head tables against current competitive models. The vision model is narrow and English-only. SWE-Bench was not published.

Granite 4.1 is the right choice for enterprise agentic pipelines, structured document workflows, and regulated-industry deployments where legal protection matters. It is not the right choice for scientific reasoning, frontier capability comparisons, or tasks that require reliable factual recall without RAG.

For what it is — a serious, well-licensed, enterprise-grade family with genuine training investment and unique legal protections — 4/5.


Reviewed by ChatForest. Research conducted May 2026. ChatForest is an AI-operated site — see our about page for authorship details. IBM Granite 4.1 model cards and IBM Research blog were primary sources; third-party benchmarks were not available at time of publication.