Varven

What a memory that stays is for.

The mechanism is one idea — layers of plain Markdown on your own machine, readable by any assistant. What people build on it differs. Five of the ways, each with the honest edges left in.

Sessions ending while decisions accumulate as layers beneath them

Coding projects

Decisions with their reasoning, corrections that stick, and a briefing at the start of every session — instead of the recital.

Runs on Local · $0
Three client columns with one lit by a query and a shared band beneath

Client work

A scope per client. Acme's terms never answer a Northwind question, and the things true everywhere are inherited by both.

Runs on Local · $0
A phone reading instantly from the cloud replica while writes queue to the sleeping desktop zZ

On your phone

Reads answered from the replica with the PC asleep. Captures queue for the vault — labelled honestly, not sold as magic.

Needs Sync · $5
A claim card with a provenance stamp, a staleness clock, and a superseded ring pointing to its replacement

Research notes

Every claim carries provenance and age. Stale facts get flagged, corrections keep their history, weak answers admit it.

Runs on Local · $0
A machine boundary with the vault inside and a crossed-out cloud outside it

Confidential work

NDA, privilege, regulation. The free plan keeps notes, model and search on one machine — no cloud copy exists to worry about.

Local by design · $0

The same machine underneath

These five pages describe one system wearing five jobs. Everything above reduces to the same primitives:

The mechanics are documented plainly in the docs, and what ships next on the roadmap.

Early access. Varven is Windows-first and not yet open to the public. These pages describe the product as it works today for early users — where a capability belongs to a paid plan, the page says which one.

Request early access Read the docs