Rift vs Cloudflare Artifacts
Artifacts gives every agent task its own Git repository. Rift syncs whole folders, including the files Git does not track.
Cloudflare Artifacts
one repository
:%20the%20Clawd%20lobster,%20mirroring%20ui/public/favicon.svg%20base%20pose.%20--%3e%3cpath%20d='M60%2010%20C30%2010%2015%2035%2015%2055%20C15%2075%2030%2095%2045%20100%20L45%20110%20L55%20110%20L55%20100%20C55%20100%2060%20102%2065%20100%20L65%20110%20L75%20110%20L75%20100%20C90%2095%20105%2075%20105%2055%20C105%2035%2090%2010%2060%2010Z'%20fill='url(%23lobster-gradient)'/%3e%3cpath%20d='M20%2045%20C5%2040%200%2050%205%2060%20C10%2070%2020%2065%2025%2055%20C28%2048%2025%2045%2020%2045Z'%20fill='url(%23lobster-gradient)'/%3e%3cpath%20d='M100%2045%20C115%2040%20120%2050%20115%2060%20C110%2070%20100%2065%2095%2055%20C92%2048%2095%2045%20100%2045Z'%20fill='url(%23lobster-gradient)'/%3e%3cpath%20d='M45%2015%20Q35%205%2030%208'%20stroke='%23ff4d4d'%20stroke-width='3'%20stroke-linecap='round'/%3e%3cpath%20d='M75%2015%20Q85%205%2090%208'%20stroke='%23ff4d4d'%20stroke-width='3'%20stroke-linecap='round'/%3e%3ccircle%20cx='45'%20cy='35'%20r='6'%20fill='%23050810'/%3e%3ccircle%20cx='75'%20cy='35'%20r='6'%20fill='%23050810'/%3e%3ccircle%20cx='46'%20cy='34'%20r='2.5'%20fill='%2300e5cc'/%3e%3ccircle%20cx='76'%20cy='34'%20r='2.5'%20fill='%2300e5cc'/%3e%3c/svg%3e){kind=small}
Rift
one folder, read
What Cloudflare Artifacts is
Cloudflare Artifacts is versioned storage for agents that uses the Git protocol. It is built for very large numbers of small repositories, one for each project, session or task, and any Git client can clone and push to them. It has been in open beta since October 2026.
How they differ
Artifacts grants access by the repository, with tokens that your own Worker or API layer mints. It carries what Git tracks. Rift grants access by the folder and carries every file in it.
Cloudflare ArtifactsRift
IdentityCloudflare ArtifactsA repository token minted by the owner's Worker or API layer.RiftA key that each machine and agent makes for itself. No account.
Smallest shareCloudflare ArtifactsOne repository, as read or write.RiftA folder, a subfolder or one file, as read or write.
Who checks accessCloudflare ArtifactsCloudflare.RiftEach machine that receives a file checks the grant itself.
Who can read your filesCloudflare ArtifactsCloudflare stores the repositories. We found no documented option for customer-held keys.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offCloudflare ArtifactsFiles stay available from Cloudflare.RiftFiles stored in Rift Cloud stay available.
Which to choose
Choose Cloudflare Artifacts when
- Your agents already work through Git.
- You build on Cloudflare Workers.
- You want history for every change.
Choose Rift when
- Agents produce files that do not belong in a repository.
- An agent should receive one folder out of a larger project, with no separate repository made for it.
- The other side's agent should hold its own key and need no token from you.
Based on Cloudflare's documentation, read in October 2026. Sources: how Artifacts works, changelog.