Model Detail
granite-switch-4.1-30b-preview
—granite-switch-4.1-30b-preview is a large language model with 30B parameters released by ibm-granite. The model is registered under the text-generation pipeline tag on Hugging Face, distributed under the permissive apache-2.0 license.
granite-switch-4.1-30b-preview ships with 30B parameters. Total weight footprint is approximately 32.2 GB, which is the relevant figure when planning local-inference VRAM. The apache-2.0 license is permissive, allowing commercial deployment and derivative work without per-seat fees, though attribution requirements still apply.
granite-switch-4.1-30b-preview is best fit for general-purpose chat and instruction-following workloads. Treat this as a starting matrix rather than a benchmark verdict — the right deployment usually depends on the specific evaluation suite that mirrors your workload.
Granite Switch 4.1: Chat, Decisions, and Speech from One Endpoint
MCP-GRANITE Benchmark: GRANularity Interface TEsting for MCP-Based LLM Agents
arXiv:2609.24161v1 Announce Type: cross Abstract: As LLM agents increasingly interact with external tools through standardized protocols such as MCP, tool-interface design becomes a critical yet underexplored factor. How fun{\psi}tionality is decomposed into tools affects whether an agent can select
Design of the IBM Granite 5.0 TurboCTC ASR Model
arXiv:2609.20104v1 Announce Type: new Abstract: We describe the architecture, training methodology and inference speedups of Granite 5.0 Turbo CTC, a 470 million parameter encoder-only model with an excellent speed-accuracy tradeoff. The architecture uses pyramidal temporal subsampling within Confor
IBM releases SOTA Granite Time Series PatchTST-FM-r2 model with commercial-friendly license
Granite.Trust Policy Tools: Shareable, Actionable Policies for Generative AI Applications
arXiv:2608.23870v1 Announce Type: new Abstract: When it comes to safety policies for generative AI, one size does not fit all. Each organization and use case needs to mitigate different risks depending on the application context, regulatory environment, organizational values, and user personas. Yet,
