Memory that doesn't disappear between sessions.

What it is

A control plane, and a watcher that actually runs on the machine.

The web app is a simulator you can explore. The real program is the installed sidecar: it watches memory continuously and locks a snapshot on a schedule, so state survives a crash, a reboot, or a long idle stretch.

What it does

Protects the work, and keeps it going.

A resource meter watches the machine's memory in real time. A project locker locks a project so work in progress isn't overwritten, and fleet checkpoints capture the state of a whole fleet of sessions, not just one. A Dream state engine handles offline processing and consolidation between sessions, and a full audit trail records what changed and when. Separate screens cover memory, notes, and a lab-style workspace view for looking at it all directly.

Where it stands

In development, invite-only.

Somnus is in active internal use today and being refined before a wider release. It is not yet a self-serve product.

What it replaces

A new problem, so there is nothing yet to compare it to.

Somnus exists because AI forgets. A session ends, a machine reboots, a long job stalls, and the work in progress and everything the assistant had learned goes with it. That problem is only a few years old, so there is no established product you would weigh this against.

What Somnus does is keep the state: it watches the machine's memory as it runs, locks a snapshot on a schedule, locks a project so work in progress is not overwritten, and keeps an audit trail of what changed and when. It is the thing that is running underneath when an assistant picks up tomorrow where it left off tonight.