MAKERS & DEVELOPERS
Open enough to take apart.
Software, hardware and interfaces meant to be understood, changed and built on — not only used.
The problem
Plenty of systems are extensible — as long as you stay inside their platform.
There is an API, a plugin system, maybe even a marketplace.
What is missing is the way out: running the system yourself, swapping a model, connecting a device nobody planned for.
What somsorium makes of that
Parts you can replace.
Local models, documented interfaces between the building blocks, and hardware meant as a kit.
The aim is that you can follow how the system works, run it yourself, and fit it to your own setup.
From a developer’s point of view
What the four building blocks are made of.
What follows is where things stand today — not a roadmap dressed up as a feature list.
smolit
Rust core without a UI; interfaces in React via Tauri 2, for desktop and Android. Coupled solely over loopback WebSocket IPC, not reachable from outside. Models local by preference, speech handled locally through whisper.cpp and Piper. AGPL-3.0, currently 1.0.0-rc.2 with a reproducible build.
mesorium
mesorium under MIT, the cockpit under AGPL-3.0. Private areas, groups and connections between areas are working; the connection outwards works for text. Signed program files for desktop and Android are the next block.
laborium
Runs locally and offline on a Raspberry Pi 4 or 5, and on x86_64, without a forced cloud. Brings a tool interface over MCP for smolit — the assistant helps, the person decides. Software under AGPL-3.0; the hardware documentation is set up to be free.
smolit node
Reference base Raspberry Pi OS Lite (64-bit) with a reproducible system image and signed updates. The first version is meant as a kit: repairable, modifiable, resellable.
Where to start
Four places where something of your own can attach.
- Your own tools
smolit calls tools only within the permissions you give it. laborium hooks in over MCP at exactly that point — the same route is open to tools of your own.
- Your own models
Models run locally by preference. Which class of task ends up on which model is a setting, not fixed wiring.
- Your own devices
laborium connects sensors and devices to the measurement series. The hardware documentation is set up to be free, so a setup of your own fits alongside.
- Running it yourself
The node’s system image is reproducible. Anyone who would rather set the stack up themselves should be able to follow how it is done.
Where we stand
Honest about the word open.
- The repositories are not public yet. The licences are settled and publication is planned — but as long as the code cannot be read, we do not link to it either. Everything below is therefore not something you can check, only something we are committing to.
- There is no documented public API yet, and no extension interface with a promise of stability. The MCP connection between laborium and smolit exists, but it is not specified as a platform API.
- Ready-made installation packages are missing; today the route runs through the source code.
- Parts list, build plan and hardware documentation for the node and the lab modules exist, but are not published yet.
The way there is set out under What counts next — reproducibility of the stack is the next goal there.
Waitlist
Be there when the repos open.
Our first test circle is meant to be up to 5 organisations and 500 individuals. Through the waitlist we let people know as soon as there is something to read and to build.
Non-binding, and not a guarantee of access.