Rift

Rift vs Supermemory

Supermemory turns conversations and documents into searchable memory on its servers. Rift syncs files between machines without reading them.

Supermemory

Youlaptop
work
api
billing
runs
.env
Supermemory
It can read your files.

Facts and passages extracted from what you send. Its SMFS tool also keeps mounted files here.

one namespace
OpenClawOpenClawanother company's agent
holds an API key for one namespace

Rift

Youlaptop
work
api
billing
runs
.env
Rift Cloud
It cannot read your files. It holds only ciphertext.
Fv+a8LdicjU6ce
efFPD/W3GEGTbB
FFu91EY6OfuOIc
j3iz+iV3W5kvab
1hZDb7nJAxjHmy
one folder, read
OpenClawOpenClawanother company's agent
holds its own key
apiread

What Supermemory is

Supermemory is a memory and retrieval service for agents and apps. You send it text, files, chats or connected sources such as Drive and Notion, and it extracts facts into a graph, keeps the source passages for search and maintains a profile for each user. One API returns all three. It can also mount a namespace as a directory through an open-source tool called SMFS, so an agent can run ls, cat and grep on its memory. It is a hosted platform, and a single-machine server that you run yourself is free within a licence limit.

How they differ

Supermemory processes what you send so it can extract facts, build embeddings and answer searches by meaning, and on the hosted platform that work happens on Supermemory's servers. Its SMFS tool syncs a mounted directory through those servers, which index it. Rift does not index or interpret anything. It moves files between the machines whose keys were given access.

SupermemoryRift
IdentitySupermemoryA Supermemory API key for one organization, or a key limited to one namespace.RiftA key that each machine and agent makes for itself. No account.
Smallest shareSupermemoryOne namespace, through an API key limited to it.RiftA folder, a subfolder or one file, as read or write.
Who checks accessSupermemorySupermemory's servers, or your own server when you host it.RiftEach machine that receives a file checks the grant itself.
Who can read your filesSupermemorySupermemory, on the hosted platform, where its models process what you send. You, when you host it with a local model. A hosted model you point it at sees what it processes. We found no documented option for customer-held keys.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offSupermemoryMemories and mounted files stay available from the hosted platform.RiftFiles stored in Rift Cloud stay available.

Which to choose

Choose Supermemory when

  • Agents need to recall facts about a user across sessions.
  • You want search by meaning over documents with no embedding pipeline to run.
  • You want connectors that pull from Google Drive, Notion or Gmail.

Choose Rift when

  • The files should reach other machines without a service indexing them.
  • A cloud should store the files and be unable to read them.
  • Another person's agent needs one folder and should hold its own key.

Using them together

An agent can keep what it has learned in Supermemory and the files it works on in Rift.

Use Rift with Supermemory

Based on Supermemory's documentation and privacy policy, read in October 2026. Sources: what it is, how it works, SMFS, security, API keys, namespaces, SMFS mount, self-hosting, privacy policy.

View as Markdown