Gemma 4 E4B IT vs Hy-Memory-30B-A3B

Gemma 4 E4B 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, and ships a response schema for Transformers' parser. 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, 131,072 tokens native, which meets the 128K line.

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

Gemma 4 E4B IT 95

Memory 30, Google's own 4-bit QAT GGUF with its projector is 6.15 GB, which with a fifth on top is 7.4 GB and fits in 16 GB or less. Runtimes 25, released support in Transformers, vLLM, SGLang, llama.cpp, Ollama and LM Studio, six of six. Builds 15, Google publishes a Q4_0 GGUF and a w4a16 build and two mobile builds, read as two kinds as for the 31B. Terms 15, plain Apache 2.0 with nothing added. Download 10, no account or gate. Hosted 0, the Gemini API serves only the two largest sizes and no inference provider lists this one.

Hy-Memory-30B-A3B 85

Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB. Its Q3_K_M file and the two files with experts at 1 or 2 bits are below 4-bit precision and don't count. Runtimes 20, hy_v3 model code in released vLLM (HYV3ForCausalLM in the v0.33.0 registry), SGLang v0.5.23 (hunyuan_v3.py), Transformers v5.22.2 and llama.cpp b12242, 5 each. Builds 15, Tencent publishes an FP8 repository and a GGUF repository with Q4_K_M, Q6_K and Q8_0 files in its own organisation, so quantised builds at two precisions or more. Terms 15, Apache 2.0, with only a preamble naming Tencent as copyright holder above the licence text. Download 10, gated is false for the main, FP8 and GGUF repositories on 10 November 2026, so the files download with no account or terms to accept. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and the card names no API. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Gemma 4 E4B 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 programme give a route to report a flaw, but no public Gemma advisories were found.

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Gemma 4 E4B IT 75

Model card 20, all seven items are there. Training data 10, a general description by type with a January 2025 cut-off and the filtering, but no sources, mix or sizes. Last change 20, Google's JAX library fixed the Gemma 4 audio embedding that this size runs on 5 October 2026, 28 days before this check, while the Hugging Face files last changed on 20 July. The line drops to 15 after 4 November unless the files or reference code change. Responsiveness 10, Google replied to 12 of 26 questions and reports, the last on 2026-07-17, with the five opened from 21 September to 1 November unanswered. Version policy 10, earlier Gemma generations keep their own repositories and gemma.ai has a dated releases page. File health 5, the files agree with the card but reports about them wait without a reply. 20 + 10 + 20 + 10 + 10 + 5 = 75.

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.