Cloudflare Artifacts, versioned Git-style storage for AI agents, starts billing on 12 November 2026

Cloudflare Artifacts, versioned Git-style storage for AI agents, starts billing on 12 November 2026

1 October 2026: Cloudflare says it will begin billing for Artifacts on 15 October 2026, a date it has since moved to 12 November (see the update below). Artifacts is a Git-compatible, versioned storage service that the company pitches as the place for AI coding agents and applications to store and version their work. It is in open beta for customers on the Workers Paid plan.

Not yet independently verified. This rests on Cloudflare's own blog post and pricing page; no independent report was found. We will update this when it can be confirmed, and remove this note.

Update, 29 October 2026: Cloudflare's Artifacts pricing page, last updated on 28 October, now says billing for Artifacts operations and storage begins on 12 November 2026, not 15 October. It lists the first 10,000 operations a month as free, then $0.15 per 1,000 operations, and the first 1 GB-month of storage as free, then $0.50 per GB-month, on the Workers Paid plan only.

What Cloudflare announced

In a blog post of 1 October 2026, Cloudflare described Artifacts as storage organised as repositories that agents can create, commit to and branch at scale, and invited developers to build "the next Git platform" on top of it, with a competition attached. The post says pricing is based on repository operations and the amount of data stored, and that billing for Artifacts usage begins on 15 October 2026.

Who is affected

Teams already experimenting with Artifacts during the free part of the open beta, especially those whose agents create many repositories or commit frequently, since operations are billed. Developers evaluating where AI coding agents should keep their output, and platform teams on the Workers Paid plan who may find usage appearing on their bill.

What to do

1. Check your Cloudflare account for Artifacts usage and estimate costs from Cloudflare's published per-operation and storage prices before 12 November.
2. Set usage alerts or limits so that a runaway agent cannot generate unexpected charges.
3. Decide whether data you store there needs a specific location and check the options offered.
4. Treat it as a beta: keep a copy of anything important elsewhere until the service is generally available.

Why it matters for buyers

AI agents generate far more commits, branches and files than human developers, so storage priced per operation behaves differently from storage priced per seat. The end of a free beta period is the moment to check the economics. It also fits a wider pattern this autumn of usage-priced AI infrastructure, where budget controls matter as much as features.

Related on TrustList:

• GitHub Enterprise Cloud with data residency refuses X25519-only TLS clients from 7 October 2026
• Git 2.56.1 fixes six flaws, one allowing code execution on clone

Sources

• Cloudflare blog: We want you to build the next Git platform on Cloudflare - 1 October 2026
• Cloudflare Developers: Artifacts pricing - updated 28 October 2026