Hy-Memory-30B-A3B vs Laguna M.1

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.

Laguna M.1 36

Model card 11 of 20, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 5, the report describes sources and filtering but gives no cut-off. Last change 10, 14 July 2026, 113 days ago. Responsiveness 0, the one discussion's only reply is from someone outside the poolside organisation. Version policy 5, a first open release with nothing replaced. File health 5, generation config and template disagree on the thinking default and the FP8 build's Docker files name different image tags.

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.

Laguna M.1 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card shows how tools go in and calls come back and names the poolside_v1 parser. Trained tool calling 20, several calls a turn. Structured output 0, not documented. Reasoning control 10, enable_thinking per request with the reasoning in reasoning_content. Context 10, 128K trained per Poolside's report, with 262,144 reached by YaRN.

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.

Laguna M.1 70

Memory 5 of 30, the smallest 4-bit build is Poolside's 139.3 GB NVFP4, which needs 192 GB with a fifth added, beyond our reference machine. Runtimes 25, released llama.cpp, Ollama (through the llama.cpp release it pins), vLLM, SGLang and Transformers run the laguna architecture. Builds 15, FP8 and NVFP4 from Poolside. Terms 15, Apache 2.0 with nothing binding added. Download 10, nothing is gated. Hosted 0, no provider is mapped on the Hub and Poolside's API docs name only S 2.1.

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.

Laguna M.1 55

File safety 15 of 25, safetensors only, but the repository ships model code behind auto_map and the card's SGLang and TensorRT-LLM instructions use trust_remote_code. Provenance 15, the verified poolside organisation, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 5, general cautions only. Licence risk 15, plain Apache 2.0. Security programme 5, a signed security.txt and a security contact on the card, with no public advisories found.