A desktop agent, a runtime, the models and the tools to run AI on hardware you own.
We publish the measurements — including where it is not enough yet.
We build for one question: how much can you do — and how much can you
own — without the cloud? More than most people expect. An agent that works for you,
models you can hold, your data staying yours. Small steps toward a future that is more utopian
than dystopian.
Build · Measure · Publish · Explain · Repeat
One lab, five layers.
Rijoda Labs is not a single product. It is a stack that moves intelligence from
a server to your machine — and keeps every layer inspectable. Read it from the metal up.
01
MachineRijo Box
A disposable, isolated computer for the agent. Own Rust VMM, a Rust-first Linux guest, Servo — so the agent can run wild without touching your host.
02
RuntimeRijo Run
A pure-Rust inference runtime for ordinary laptops. Own kernels, GGUF first, agent-aware scheduling. Working title; M0 is measured.
03
IntelligenceModels & quantisations
Open models we rebuild for a specific machine and measure against stock — and, next, small models trained here with published checkpoints and provenance.
04
Agent appRijo Code
The desktop app (coming) that does the work: projects, sessions, 34 native tools, MCP, browser. The engine underneath is Rijo Core — public and inspectable.
05
OutputRijo Stack + Rijo Vector
What the agent builds with: web and desktop from one Rust codebase, and vector graphics it can write and edit as deterministic SVG.
The software.
Five products, one stack. Some run today; some are early. Each card says which —
no roadmap theatre.
The desktop appApp coming · CLI v0.1.0
Rijo Code
The finished desktop app, still coming: a workbench where the agent does real work on
your machine — projects, sessions, approvals, 34 native tools, MCP, browser. The CLI is
the headless entry point today.
Runs on the open engine Rijo Core — the app is the product, the engine is public.
A disposable, isolated computer for your agent. Own Rust VMM on KVM/WHPX, a Rust-first
Linux guest, Servo for the screen. A vCPU and a kernel already boot; a full Linux guest
is the next gate.
The runtimeM0 · working title
Rijo Run
A pure-Rust inference runtime for ordinary laptops: own CPU kernels, GGUF first,
agent-aware scheduling. M0 is measured on a local Qwen2.5-1.5B; G0 is not decided.
The builderPrototype · CI green
Rijo Stack
Web and desktop from one Rust codebase and one binary, with SQLite embedded. Verified
end to end — auth, jobs, mail, migrations, MCP and deploy. No public release yet.
The generatorCore runs
Rijo Vector
A JSON language for vector scenes that compiles deterministically to SVG — built so a
model can create and surgically edit graphics. 365 tests, 202 error codes, an MCP server.
Models you can hold.
We publish two kinds of artifacts. Quantisations are open
models we rebuild for a specific machine and measure against the stock release.
Own models are trained here — still ahead. Every release ships with its
method, its numbers and its limits.
Published · Quantisationv1.0.0 · live on Hugging Face
LFM Open License v1.0
LFM3-Omni-2B Q4_K_S · mixed imatrix
A quantised derivative of Liquid AI's omni-modal 2B model, tuned for laptops
without a discrete GPU. Smaller, measurably better and faster than the stock Q4_K_M — on the
reference machine. No retraining, no fine-tuning.
Measured on Intel Core Ultra 7 255U, Intel iGPU, Vulkan, llama.cpp b12110.
Speed: interleaved, 5 rounds, first 2 discarded, control model in the loop. This quant won
decode in all 10 pairwise comparisons.
Not a trained model: a derivative of LiquidAI/LFM3-Omni-2B. The multimodal
projector is not redistributed — pull the unmodified file from the base repository. “Liquid”,
“Liquid AI” and “LFM” are trademarks of Liquid AI, Inc.; this release is not endorsed by or
affiliated with Liquid AI. Full licence and NOTICE ship with the weights; commercial use is
conditioned on annual revenue below USD 10M (LFM Open License §5).
1
Profile the machine
Decode reads every weight once per token, so bytes are speed — but kernel format beats
file size. On this iGPU, a smaller Q4_0 file was 18–25% slower. Profile first.
2
Calibrate on the job
An importance matrix over mixed prose + code. A code-only matrix improved perplexity and
broke arithmetic — so we measure tasks, not just one scalar.
3
Measure, then publish
Quality first, speed last. Cooled, interleaved runs, a control model, raw eval files and a
SHA256 manifest shipped with the weights. The method transfers; the numbers do not.
NextIn progress · no weights yet
Own models, trained here.
Small, purpose-built models with published checkpoints and data provenance — the Pythia
pattern. RijoBench, our agentic benchmark for tool use, safety and latency on the
reference machine, is built and baselining. No model release yet; we name that plainly.
The catalogGrowing
What every release carries.
A version, a SHA256 manifest, a model card, raw evaluation files, the exact method and a
licence/NOTICE. More quantisations follow as we tune them for the reference laptop — and
each one will be comparable, not just downloadable.
Rijo Code is the app. Rijo Core is the engine.
Rijo Code — the finished desktop app, still coming — is the product you use.
Rijo Core — its engine — is the backend that executes tools, enforces the guard, manages
sessions and talks to models. We publish the engine; the app stays the product.
Product · comingDesktop app
Rijo Code
The workbench you will use once it ships: projects, session tabs, approvals, activity
inspector and the window model. The app is the product surface; its source stays private
while it matures.
commandsevents
Open engine · public nowApache-2.0
Rijo Core
The backend functions underneath: executor, 34 native tools, guard, sessions, transcript
model, inspect, LLM adapter, brain, config and MCP. The CLI and rijo mcp serve
are headless entry points to the same engine.
Open enginePublic since 2026-11-08
rijo-core
The engine as a library: executor, 34 native tools, guard, sessions, transcript model,
UI event contract, inspect, LLM adapter, brain and
config. Rust. Apache-2.0.
The finished desktop app, still coming: a workbench with projects, session tabs, approvals
and an activity inspector. The CLI is the headless entry point today; MCP reaches the same
engine. The app source stays private — the app is the product, not the crate.
Rijo Core is Apache-2.0. The CLI and MCP ship with the public engine; the
desktop app source stays private. This website's code is MIT OR Apache-2.0; documentation
licensing is being finalised. The trademark search for the name is still open.
Where we are, right now.
No roadmap theatre. This is the state of each part today — running, in progress,
or still only researched.