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

Arete-27B vs Gemma 4 26B A4B IT

Gemma 4 26B A4B IT scores 72.2 (BB) on agent readiness against Arete-27B's 55.1 (C), and leads in every scored category. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons

Which one, for what

Arete-27B C

Best for Agents that want Qwen3.8-27B's coding and tool use without its handling of politically sensitive topics, on a 24 GB card or a 128 GB machine

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No quantised build from Nous Research, so the GGUF route depends on a third party

Gemma 4 26B A4B IT BB

Best for Agents on a 24 GB or larger GPU or Mac that want a fast, permissively licensed tool-calling model with images and long context

Ahead on

  • Reach, 90 against 50
  • Risk, 70 against 55
  • Agent interface, 85 against 60

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No safety evaluation figures published

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach Gemma 4 26B A4B IT +40

Arete-27B 50

Memory 10, the only build from Nous Research is the 54.7 GB BF16 release, which needs about 66 GB and fits the reference machine. Runtimes 15, vLLM, SGLang and Transformers run the base's architecture from those files, and llama.cpp isn't credited because Nous Research publishes no GGUF. Builds 0, no quantised build of its own. Terms 15, Apache 2.0. Download 10, not gated. Hosted 0, no provider. 10 + 15 + 0 + 15 + 10 + 0 = 50.

Gemma 4 26B A4B IT 90

Memory 25, Google's own 4-bit QAT GGUF is 14.4 GB, which with a fifth on top is 17.3 GB and lands in the 24 GB band, with the 1.2 GB vision projector extra for images. Runtimes 25, released support in vLLM, Transformers, llama.cpp, Ollama, SGLang and LM Studio, six of six. Builds 10, Google publishes one quantised precision (Q4_0 GGUF), since its unquantised QAT repository is BF16 and there's no FP8 build. Terms 15, plain Apache 2.0 with nothing added. Download 10, no account or gate. Hosted 5, the Gemini API serves it and four inference providers are live on Hugging Face.

Agent interface Gemma 4 26B A4B IT +25

Arete-27B 60

Chat template 20, a Jinja file in the repository. Tool-calling format 10, only the template says it. Trained tool calling 20, several calls a turn and agentic work as an intended use. Structured output 0 and reasoning control 0, neither is documented on the card. Context 10, 262,144 tokens native. 20 + 10 + 20 + 0 + 0 + 10 = 60.

Gemma 4 26B A4B IT 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Google documents how tools are declared and how calls come back, ships a response schema for Transformers' parser, and names the gemma4 parser in vLLM and SGLang. Trained tool calling 20, several calls in one turn. Structured output 0, nothing documents how to ask the weights for JSON or a schema. Reasoning control 10, thinking is off by default, turned on per request, and returned in a thought channel. Context 10, 262,144 tokens native.

Risk Gemma 4 26B A4B IT +15

Arete-27B 55

File safety 25, safetensors only and no remote code. Provenance 15, Nous Research's own organisation, linked from its blog, with a hash on every file. Safety evaluation 0 and agent guidance 0, nothing published on either. Licence risk 15, plain Apache 2.0. Security programme 0, no way to report a flaw found. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Gemma 4 26B A4B IT 70

File safety 25, safetensors and GGUF only, with nothing from the repository run on load. Provenance 15, the files sit in Google's own organisation and every file has a checksum. Safety evaluation 0, the card says testing showed minimal policy violations but gives no figures. Agent guidance 10, the card names the harm categories its safety training covers and asks for content-safety safeguards, and the tool guide says to validate calls, with no prompt-injection guidance. Licence risk 15, Apache 2.0 with no added policy, no threshold and a working link. Security programme 5, Google's security.txt and reward policy give a route to report a flaw, but no public Gemma advisories were found and GitHub's advisory tab couldn't be checked.

Score by category

CategoryWeight this runArete-27BGemma 4 26B A4B ITEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255090Gemma 4 26B A4B IT +40
Risk20%205570Gemma 4 26B A4B IT +15
Agent interface10%106085Gemma 4 26B A4B IT +25
Documentation and upkeep10%106365Gemma 4 26B A4B IT +2
Negative events≤1500
TotalC 55.1/100BB 72.2/100

Facts side by side

FactArete-27BGemma 4 26B A4B IT
KindOpen-weight modelOpen-weight model
VendorNous ResearchGoogle DeepMind
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-11-062026-07-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3.8/5 (4)

Verdicts

Arete-27B

Qwen3.8-27B with its answers on politically sensitive topics retrained, four days old when read. The training data is published, which is rare. Nous Research ships BF16 only, so a small machine runs it from bartowski's GGUF, and the card documents none of the tool or thinking controls it inherits.

Gemma 4 26B A4B IT

A fast mixture-of-experts cousin for general agent work with tools, optional thinking and image input, under Apache 2.0. Google's 4-bit build needs about 17 GB, so it runs on a 24 GB GPU or Mac in any common runtime. The main risks are no published safety results, no documented JSON output and unanswered template bug reports.

Before you call either

Arete-27B

  1. Start it with llama-server -hf bartowski/NousResearch_Arete-27B-GGUF:Q4_K_M --jinja, a third party's conversion, or serve the BF16 files with vLLM
  2. Use the base's parsers in vLLM, --reasoning-parser qwen3 --tool-call-parser qwen3_coder, and check tool calls first, since the template differs slightly from Qwen3.8-27B's
  3. Thinking switches with enable_thinking in the template. The card's own evaluation ran with it off
  4. Expect answers on politically sensitive topics to differ from Qwen3.8-27B's. That is what the fine-tune is for
  5. Validate JSON output yourself, since structured output isn't documented

Gemma 4 26B A4B IT

  1. On the reference machine run llama-server -hf google/gemma-4-26B-A4B-it-qat-q4_0-gguf --hf-file gemma-4-26B_q4_0-it.gguf --jinja -c 65536, and add the mmproj file for images
  2. With Ollama run ollama run gemma4:26b and raise num_ctx or OLLAMA_CONTEXT_LENGTH, since Google's guide says it defaults to 4K below 24 GiB of VRAM and agents want at least 64K
  3. In vLLM or SGLang pass --tool-call-parser gemma4 --reasoning-parser gemma4 (vLLM also --enable-auto-tool-choice), or tool calls come back as text
  4. Thinking is off by default; pass enable_thinking=True or start the system prompt with <|think|>, and drop earlier turns' thinking from history except on tool-call turns
  5. Validate tool names and arguments before running them, and check any JSON yourself

Questions

Which is better for AI agents, Arete-27B or Gemma 4 26B A4B IT?

Gemma 4 26B A4B IT scores 72.2 (BB) on agent readiness against Arete-27B's 55.1 (C), and leads in every scored category.

Other comparisons with Arete-27B or Gemma 4 26B A4B IT

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.