Run the work, not the machine.
Containers package a process. Virtual machines preserve a computer. Solu begins with a different durable object: the work itself.
How it works
A Solu is a durable environment for agentic work. Agents and subagents may join, leave, fail, or be replaced; the environment keeps the work and the resources made available to it, whether execution happens locally or elsewhere. No process moves between machines: one worker ends, and the next picks up the work.
What it holds and what it never does
- Keeps
- The work, under one identity that outlasts every worker attached to it.
- Holds
- Context, resources, and results: what has been learned, what the work may use, and what has come back. A new worker starts from there, not from nothing.
- Admits
- Agents and subagents, local or remote. They join, leave, fail, or are replaced; the work stays identifiable and usable.
- Uses
- Native processes, containers, or microVMs underneath, chosen when their properties are useful. None of them defines the world the agent works in.
- Never
- Moves a live process from one machine to another, replaces the isolation underneath, or fixes the steps in advance. A pipeline preserves a sequence; a Solu preserves what the next step is discovered from.
Selko sees. Vartio keeps the fleet. Taso owns the gate. Solu runs the work.
Today the work lives wherever the agent happened to run.
An agent session starts on one laptop. What it has learned sits in a transcript. What it changed sits in a working copy. The credentials it borrowed, the services it reached, the subagent it spawned — each lives somewhere else.
Close the laptop, lose the session, or hand the task to another agent, and the work has to be reassembled by hand, if it can be at all.
A lighter box or a stronger one.
Namespaces isolate what a process can see, while cgroups control what it can consume. Containers make those mechanisms remarkably convenient, but their processes still share the host kernel. Virtual machines and microVMs provide a stronger boundary, at the cost of creating and operating another computer.
Both remain useful. Neither makes the work itself the durable object.
The longer argument is in The past is not finished with infrastructure.
The work is early. The question is not.
If your agents work across laptops, CI runners, build machines, and cloud systems, talk to us.