# Granite 4.2 30B vs Laguna M.1 (slim)

> Granite 4.2 30B scores 61 (C) to Laguna M.1's 56.7 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/granite-4-2-30b-vs-laguna-m-1.md (~8,800 tokens) · this version ~680 tokens · JSON https://www.anchorterminal.com/compare/granite-4-2-30b-vs-laguna-m-1.json · canonical https://www.anchorterminal.com/compare/granite-4-2-30b-vs-laguna-m-1
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Granite 4.2 30B scores 61 (C) on agent readiness against Laguna M.1's 56.7 (C), and leads in 2 of 4 scored categories. Both do open-weight models you run yourself.

- Granite 4.2 30B: C 61, rank #65 of 160 open-weight models · https://www.anchorterminal.com/tools/granite-4-2-30b.min.md
- Laguna M.1: C 56.7, rank #112 of 160 open-weight models · https://www.anchorterminal.com/tools/laguna-m-1.min.md
- Granite 4.2 30B, good for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card Ahead on Reach, 90 against 70; Documentation and upkeep, 87 against 36.
- Laguna M.1, good for Teams with a multi-GPU Blackwell or Hopper server that want a large coding agent model under Apache 2.0.

| Category | Granite 4.2 30B | Laguna M.1 |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 90 | 70 |
| Risk (20%) | 55 | 55 |
| Agent interface (10%) | 85 | 85 |
| Documentation and upkeep (10%) | 87 | 36 |

| Fact (where they differ) | Granite 4.2 30B | Laguna M.1 |
| --- | --- | --- |
| Vendor | IBM | Poolside |
| Last release | 2026-09-04 | 2026-07-14 |
| Terms last updated | no document linked | 2026-07-21 |
| Privacy policy last updated | no document linked | 2026-07-21 |
| Customer content may train models | not read yet | yes, with an opt-out |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Documentation and upkeep, Granite 4.2 30B +51: Granite 4.2 30B 87 (Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 1…); Laguna M.1 36 (Model card 11 of 20, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't.)
- Reach, Granite 4.2 30B +20: Granite 4.2 30B 90 (Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 GB, which fits 24 GB but not 16 GB.); Laguna M.1 70 (Memory 5 of 30, the smallest 4-bit build is Poolside's 139.3 GB NVFP4, which needs 192 GB with a fifth added, beyond our reference machine.)