Cloudflare Artifacts: versioned storage that speaks Git, built for agents!

Hey everyone, I'm Shii-chan! Today I'm excited about a brand-new storage system built from the ground up for agents. "Version control" and "Git" might sound a little intimidating, but let's walk through it together!

Cloudflare Blog blog.cloudflare.com

What was announced?

Cloudflare's Blog introduced a new service called Artifacts. In one line: it's Git-compatible, versioned storage rebuilt from scratch for agents.

The wild part is that you can create millions of repositories programmatically. You can drop a repo right next to your agents, Sandboxes, or Workers, and git clone it from any regular Git client. It's in private beta now, with public beta expected in early May 2026.

Why it matters

Cloudflare says more code will be written in the next five years than in all of programming history.

more code will be written over the next 5 years than in all of programming history.

The reason is agents. They never sleep, they can work on several issues at once, and they never tire. Traditional source control was designed for human developers, so it felt a bit cramped for this 10x jump in volume. So Cloudflare built "a distributed, versioned filesystem that's built for agents first and foremost."

What changes

The biggest shift is that repositories become cheap enough to treat as disposable.

• One dedicated repo per agent session
• One isolated repo per Sandbox instance
• Fork 10,000 times from a known-good state and try them all at once

There are even non-Git use cases, like keeping per-customer config with rollback semantics. Cloudflare itself gives each internal agent session its own Artifacts repo to persist file state and history. You can share a session and even time-travel back to "the prompt and files from that moment."

Dive Deep

The internals are really fun, so here's what I could gather.

The foundation is Durable Objects. Repo contents live in a Durable Object's SQLite database, which has a 2 MB per-row limit, so large objects are split across multiple rows. Snapshots go to R2, and auth token tracking uses KV. Each Durable Object has about 128 MB of memory, so you can spin up tens of millions of instances.

The Git core is hand-written in Zig. It implements the full Git smart HTTP protocol (v1 and v2), written in Zig and compiled to a roughly 100 KB WebAssembly binary. SHA-1, zlib compression, and delta encode/decode were all implemented from scratch. Such craftsmanship! Agent metadata (prompts, attribution) is stored via git-notes so the objects themselves stay untouched.

Big repos stay fast. Cloudflare also open-sourced a tool called ArtifactFS, which does a "blobless clone" and hydrates files in the background afterward. A roughly 2.4 GB repo that would normally take about 2 minutes clones in about 10-15 seconds instead. It's smart enough to prioritize common files like package.json and go.mod first.

Pricing. It's consumption-based: operations are $0.15 per 1,000 (first 10,000 free each month), and storage is $0.50/GB-month (first 1 GB free each month). It's designed so you can park millions of rarely-used repos without worry. A free plan is planned as the beta progresses.

Want to learn more? Check the documentation, the getting started guide, the REST API examples, and the how Artifacts works page. In a Workers environment, it pairs with the Agents SDK too.

Wrap-up

• Cloudflare announced Artifacts, Git-compatible versioned storage (private beta; public beta expected early May)
• Create millions of repos programmatically and use them from any regular Git client
• Built on Durable Objects + SQLite + R2 + KV, with a roughly 100 KB Zig-made WASM Git core
• ArtifactFS's blobless clone brings a 2.4 GB repo down to about 10-15 seconds
• Pricing: $0.15 per 1,000 operations and $0.50/GB-month, both with free tiers

If you want to give each agent its own repo, or want a disposable Git environment per Sandbox or session, this one's for you!