SovereignAI

Blog · Guide · August 25, 2026

Liquid AI's device-native LFM models in SovereignAI

Liquid AI builds models for the edge — 230 million to 8 billion parameters, unusually fast on CPU for their quality. In SovereignAI they are not the model you chat with about everything; they are the model that does the jobs where small and fast is the point, starting with the most important one: deciding what to remember about you.

What "device-native" means here, and what it does not

Liquid describes its Liquid Foundation Models as device-native: designed to run on phones, laptops, and small boards, and shipped with a mobile SDK (LEAP) for building them into iOS and Android apps. SovereignAI is a different shape — a server that runs on a machine you own and that your phone reaches over your LAN or tailnet. So the device-native path for SovereignAI is not the mobile SDK; it is Liquid's official GGUF builds, which Ollama pulls straight from Hugging Face and runs on the same laptop or box SovereignAI runs on. The models are on-device in the sense that matters for sovereignty: your machine, your process, nothing leaves.

The lineup that applies

Liquid also publishes task-specific "Nanos" — extraction, retrieval-augmented answering, translation — which are interesting for a memory engine, but SovereignAI's extractor expects a general instruction-following model, so the recipes below use the instruct-tuned LFM2.5 models.

Read the license first

The LFM2.5 GGUF repositories carry the LFM Open License v1.0. It is not Apache or MIT: the license file limits commercial use to entities under a revenue threshold (US$10 million a year, at the time of writing). SovereignAI prints the license on the starter shelf next to every entry for exactly this reason — open weights are not automatically an open license — and shows a repository's declared license in the Hugging Face browser before you pick a file. Read it once; if your organization is above the line, this guide is not for you.

Step 1 — pull the models through Ollama

Ollama runs GGUF repositories directly by their Hugging Face path, quantization included. Liquid's own model cards give the commands:

ollama run hf.co/LiquidAI/LFM2.5-2.6B-GGUF:Q4_K_M
ollama run hf.co/LiquidAI/LFM2.5-8B-A1B-GGUF:Q4_K_M

Type a question, confirm it answers, and /bye. Ollama keeps the weights; SovereignAI will see them in its model list under those same names.

Step 2 — give a Liquid model the cognition role

This is the use we designed the shelf around. SovereignAI can learn about you automatically — after an exchange, a model reads it and writes durable facts into memory, each fact naming the model that wrote it. That model does not have to be the one you chat with. The cognition role (memory.extractionModel) lets a small, local model own memory-writing while chat uses anything, including a frontier model with your API key.

A 2.6B Liquid model is close to ideal for that job: it follows the extraction format reliably, costs nothing per exchange, and finishes in a second on CPU. Two ways to set it:

  1. The shelf. Model Studio → starter shelf → Memory & cognition → LFM2.5 → use for memory & cognition. That writes the model into the cognition role in one click.
  2. Settings. Settings → Memory → extraction modelhf.co/LiquidAI/LFM2.5-2.6B-GGUF:Q4_K_M, with automatic extraction switched on.

Then turn on cognition stays home (memory.extractLocalOnly). With it on, a remote model may chat but may not write memory; with a Liquid model in the cognition role, memory-writing stays on your machine regardless of what answers the chat. The Mind view shows the policy, and every machine-written memory shows its author model — so you can see, later, that it was Liquid that decided a fact about you was worth keeping.

This is the honest division of labor: rent the frontier for the hard answer if you choose to, keep the reading of your life local.

Step 3 — a persona that runs entirely on Liquid

For everyday questions, drafts, and anything that should be instant, LFM2.5-8B-A1B makes a good persona of its own. Model Studio saves a recipe — base model, system prompt, sampling, template, seed messages — as data you own, and can build it into a named artifact on your Ollama endpoint:

Build it as, say, quick:latest, assign it to a persona, and give that persona memory and knowledge access. Because everything about it is local, the chat shows the local path, the answer carries the exact weight digest that replied, and the outgoing-preview dialog never appears — nothing is leaving.

Where it fits, where it does not

Measuring instead of guessing

Liquid also publishes Pipette, a benchmark suite that measures speed, latency and peak memory on your own device — phones included — with quality scored separately. SovereignAI's sizing is a rule of thumb; if you want measured numbers for a Liquid model on your exact hardware, that is the tool, and the shelf links to it. We have no relationship with Liquid AI.

Vision variants are not used by SovereignAI's text chat. The LFM Open License's commercial threshold is a real restriction — check it. And a model that writes your memory is a lens on your life: the cognition role makes that lens local and named, it does not make the model infallible. Every machine-written memory can be struck from the ledger, and the deletion zeroes the bytes.

Small model, big job.

Let a Liquid model decide what to remember, on your machine, with its name on every fact. The ledger explains the cognition layer in full.

Run it now

Sources