Loading the catalogue…
Loading the catalogue…
Google DeepMind's open-weight, multimodal Mixture-of-Experts model with a 262K-token context window, tuned for interactive-latency, moderate-complexity tasks.
Overview. Gemma 4 26B A4B IT is Google DeepMind's instruction-tuned, sparse Mixture-of-Experts model, released in April 2026 under an open Apache 2.0 licence. It totals 25.2B parameters but activates only 3.8B per token across 8 of 128+1 experts, pairing MoE efficiency with a 262,144-token context window and text, image, and video input. Developers who want an open-weights, multimodal model they can self-host for interactive-latency chat and moderate-complexity tasks would reach for this variant.
Key strengths. Domain scoring from Artificial Analysis puts this model at roughly a 39.3 coding index, meaningfully ahead of its 11 agentic index — real capability on coding tasks that doesn't yet extend to complex multi-step tool orchestration. It ships with native function-calling, a system role, structured-output support, and a configurable thinking mode via the model's <|think|> control token, so teams can opt into deeper reasoning only when a task calls for it. The sparse MoE design lets it deliver this feature set while touching just 3.8B active parameters per token, keeping inference lighter than a dense model of similar total size.
When to use it. Use this model for interactive chat, coding assistance, or multimodal (image and video) understanding where moderate complexity and quick turnaround matter more than frontier reasoning depth. Enable its optional thinking mode when a request needs extra deliberation, and lean on its native tool-calling and structured-output support for lightweight agentic workflows rather than long autonomous chains. It also suits teams that specifically want open weights they can deploy on their own infrastructure.
Limitations. Its coding and agentic index scores trail the family's larger 31B IT sibling, so it isn't the strongest choice for heavy code generation or complex multi-step agentic tasks. Reported max output length has varied across sources (most recently 16,384 tokens) even though the context window itself is a fixed 262,144 tokens, so single-turn generations shouldn't be assumed to run that long. Training data has a January 2025 cutoff.
Sovereignty note. Google is a United States-based creator with confirmed CLOUD Act exposure, a factor to weigh even though this model's weights are openly licensed under Apache 2.0. Because the weights are open, Gemma 4 26B A4B IT can be deployed on Sovereign infrastructure of your choosing, giving teams control over data residency independent of Google's own hosting.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L3 | €0.25 / 0.50 | Online | |||
| L1 | €0.08 / 0.27 | Online | |||
| L0 | Free / Free | Online | |||
| L0 | €0.06 / 0.31 | Online |
50 use cases classified by the curator. The note says why.
Long-context RAG-style answer generation benefits directly from the 262K window and open-weight self-hosting option.
Native vision capability directly supports chart interpretation and explanation tasks; 262K context allows chart analysis within larger report contexts.
MoE architecture with only 3.8B active params out of 25.2B total is tuned for interactive latency — well suited to high-throughput conversational chatbot deployments.
262K context window is well-suited to long-document question answering without chunking.
Native vision capability combined with a 262K-token context window supports multimodal Q&A over images and accompanying long text.
262K context window comfortably handles full meeting transcripts even for long sessions; instruction-tuned summarisation quality is well-suited to this task.
Sufficient context window and instruction-following quality support audit workflows; open-weights deployment addresses data residency requirements common in regulated sectors.
Vision + tool-calling combination supports screenshot-driven browser automation workflows; 3.8B active params keeps inference latency viable for interactive loops.
Extended-thinking mode and long context support multi-file bug tracing; instruction-tuned model handles debugging prompts competently without code-specialist tuning.
Vision support enables chart parsing, but as the smaller, lower-active-param variant it likely trails the 31B IT sibling on complex extraction accuracy.
Small active parameter count (3.8B) suited to fast, moderate-complexity classification tasks with low latency overhead.
262K context supports explaining large codebases; instruction-tuned quality produces clear natural-language explanations of code.
Tool-calling exists but no coding benchmark evidence is available, and the lightweight active-parameter MoE design is unlikely to match dedicated coding-agent models.
Family guidance singles out the larger 31B IT variant for coding quality; this smaller, latency-optimized MoE variant is not the recommended coding pick.
No published coding benchmarks for this variant, and the family explicitly recommends the 31B IT sibling when code quality matters.
Explicitly tuned for moderate-complexity, interactive-latency tasks — the family description points to the larger 31B IT variant for quality-sensitive planning workloads.
No text-to-speech capability documented; speech synthesis requires dedicated audio generation models.
No audio input capability documented; transcription requires dedicated speech-to-text models.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, ifbench, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "google/gemma-4-26b-a4b-it",
"reasoning_effort": "high",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at