Rift

Rift vs Mesa

Mesa is a versioned filesystem where every agent write is a commit. Rift syncs folders that only your keys can read.

Mesa

Youlaptop
work
api
billing
runs
.env
Mesa
It stores your files and can read them.
work
api
billing
runs
.env
one repository
OpenClawOpenClawanother company's agent
holds a token valid for up to four hours
work
api
billing
runs
.env

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 Mesa is

Mesa is a hosted filesystem for agents with version control built in. An agent mounts a repository as ordinary files, and every write becomes a commit that can be reviewed or rolled back. Each commit records both the agent and the person it worked for. It is in early access.

How they differ

Mesa grants access by the repository and serves the files itself. Rift grants access by the folder, and each machine that receives a folder checks the grant.

MesaRift
IdentityMesaA short-lived token that your backend signs.RiftA key that each machine and agent makes for itself. No account.
Smallest shareMesaOne repository, read-only or read-write, for up to four hours. A read-only repository can be mounted inside a writable one. Mesa's home page lists access controls per branch and path. Its documentation describes grants per repository.RiftA folder, a subfolder or one file, as read or write.
Who checks accessMesaMesa.RiftEach machine that receives a file checks the grant itself.
Who can read your filesMesaMesa serves the files itself. Its home page states AES-256 encryption at rest. We found no documented option for customer-held keys. Mesa also offers a version that runs in your own cloud account, with Mesa operating the control plane.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offMesaFiles stay available from Mesa.RiftFiles stored in Rift Cloud stay available.

Which to choose

Choose Mesa when

  • Every agent write should be versioned and reviewable.
  • Two agents edit the same files at once and you want both edits kept.

Choose Rift when

  • An agent should receive one folder out of a larger project, with no separate repository made for it.
  • Whoever stores the files must be unable to read them.
  • The other side's agent should hold its own key and need no token from you.

Based on Mesa's documentation, read in October 2026. Sources: authentication, token reference, layouts, live edits, home page.

View as Markdown