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

Gemma 4 31B IT vs Kolibri-1

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Kolibri-1's 61 (C), and leads in 2 of 4 scored categories. Kolibri-1 leads on agent interface 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 2870 open weights comparisons

Which one, for what

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 60
  • Risk, 70 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 3.3 out of 5

Watch for

No safety evaluation results published

Kolibri-1 C

Best for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters.

Ahead on

  • Agent interface, 90 against 85
  • Documentation and upkeep, 70 against 65

Watch for

The smallest publisher build is FP8 at 78.8 GB, so it needs about 95 GB and won't fit a 64 GB machine

Score by category

CategoryWeight this runGemma 4 31B ITKolibri-1Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259560Gemma 4 31B IT +35
Risk20%207065Gemma 4 31B IT +5
Agent interface10%108590Kolibri-1 +5
Documentation and upkeep10%106570Kolibri-1 +5
Negative events≤1500
TotalBB 74.1/100C 61/100

Facts side by side

FactGemma 4 31B ITKolibri-1
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindAleph Alpha
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-07-202026-10-19
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.8/5 (4)3.3/5 (4)

Verdicts

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

Kolibri-1

Kolibri-1 is a German and English reasoning model with a documented tool-call format, switchable thinking and a 262,144-token context, under Apache 2.0. Aleph Alpha's FP8 build needs about 95 GB and runs on vLLM through its plugin, Transformers 5.20 or recent llama.cpp. The main risk is no published safety results or security contact, and few repository answers.

Before you call either

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

Kolibri-1

  1. Start it with pip install 'aleph-alpha-inference>=1' then vllm serve Aleph-Alpha/Kolibri-1 --kv-cache-dtype fp8 --reasoning-parser kolibri1 --tool-call-parser kolibri1 --enable-auto-tool-choice
  2. Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
  3. The plugin supports one vLLM minor version, 0.29, so don't upgrade vLLM while it's installed
  4. Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
  5. Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
  6. Past 262,144 tokens, add --max-model-len 1048576 and the max_position_embeddings override in --hf-overrides, though Aleph Alpha recommends staying at or below 262,144
  7. With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
  8. On the reference machine the FP8 build fits by size, but no document confirms vLLM runs FP8 on gfx1151, and Aleph Alpha ships no GGUF for llama.cpp
  9. Validate tool results in your own code, as the card asks

Questions

Which is better for AI agents, Gemma 4 31B IT or Kolibri-1?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Kolibri-1's 61 (C), and leads in 2 of 4 scored categories. Kolibri-1 leads on agent interface and documentation and upkeep.

Other comparisons with Gemma 4 31B IT or Kolibri-1

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.