Laguna M.1 vs LFM3-Omni-2B

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.

LFM3-Omni-2B 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.

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.

LFM3-Omni-2B 70

Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.

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.

LFM3-Omni-2B 49

Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.

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.

LFM3-Omni-2B 80

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.