Features

Local-first sync — no cloud, no leaks

Each of your devices stores memory, embeddings and history itself. Changes merge conflict-free via CRDT end-to-end encrypted — the network is only a transport.

No central cloudCRDT conflict-freeOffline OK

Local-first means an architecture where the device is the source of truth — not the cloud. This matters especially for AI memory: we don't want our conversations, documents or client data sitting on a third-party server.

The 2026 stack

SQLite + sqlite-vec (local vector search) + SQLite-Sync (CRDT) is the most common combo. Alternatives: PowerSync (strongest on mobile), Turso embedded replicas (microsecond SQLite reads), and ElectricSQL / Zero / Replicache for web-centric apps.

E2EE: what's actually encrypted

Each device has its own key pair. Messages are encrypted on the sender, decrypted on the receiver. Any server (if used for transport) only sees encrypted blobs. No one can read your data, even in theory.

What happens offline?

You keep writing as normal. When devices reconnect, changes merge automatically with no conflicts. The CRDT algorithm guarantees the same final state regardless of the order devices sync in.

Frequently asked

Do I need a server?
Not necessarily. In the simplest case, devices sync directly over LAN. Remote sync benefits from a lightweight relay server that only sees encrypted blobs — we can host it in Finland or run it on your home server.

Updated 2026-04-21

Want your own local AI assistant?

Tell us about your work and hardware — we'll map the right model, the right hardware tier and the right sync configuration.

Get in Touch