# Cloudflare Artifacts Artifacts is a versioned file system from [[Cloudflare]] that speaks [[Git]]. You create repositories from code (a Worker, a REST call), hand the remote URL and a token to an agent, and the agent clones and pushes like it would with any Git host. The point is scale: one repository per agent, per session, per task or per user, and millions of them per namespace. Why Git and not a new protocol? Because models already know Git. It's all over their training data, edge cases included. A bespoke protocol would mean shipping skills, a CLI or docs to every agent before it could do anything. Cloudflare's bet is that an authenticated HTTPS Git remote removes that bootstrap problem entirely. The Git data model also works for more than code. Cloudflare uses Artifacts internally to store the file system state AND the session history of its own agents, one repo per session. You can fork a session at any point and hand it to a colleague, or time-travel back through prompts and files. ## Timeline - **2026-04-16**: announced in private beta, together with ArtifactFS - **2026-08-04**: CI on push, via a CI [[Cloudflare Workflows|Workflow]] defined with the `@cloudflare/ci` SDK and triggered by `cf.artifacts.repo.pushed` events - **2026-08-13**: data localization; pick the US or the EU per namespace (it can't be changed after creation) - **2026-10-01**: open beta for customers on the Workers Paid plan, plus a competition to build "the next GitHub" on top of it - **2026-10-14**: billing starts (the docs and the changelog say October 14; the announcement post says October 15) ## How it works - A [[Cloudflare Workers|Worker]] sits in front: authentication, metrics and routing to the right repository - Each repository is a [[Cloudflare Durable Objects|Durable Object]]. Files live in its SQLite database, chunked across rows because of the 2 MB row limit, and each object has roughly 128 MB of memory to work with - The Git server is written from scratch in Zig without libc and compiled to a ~100 KB WebAssembly binary. It handles SHA-1, zlib, delta encoding, pack parsing and the smart HTTP protocol (v1 and v2, shallow clones, incremental fetch) - [[Cloudflare R2|R2]] stores snapshots; [[Cloudflare KV|KV]] tracks auth tokens - Native support for git notes, so agents can attach prompts, attribution and other metadata to commits without rewriting them ArtifactFS is the open source companion. It mounts a large repo through a blobless clone (tree and refs first) and hydrates file contents in the background, manifests and code before binaries. Reads block only for files that haven't arrived yet. Cloudflare's example: a 2.4 GB web framework repo takes close to 2 minutes to clone, and the target with ArtifactFS is 10 to 15 seconds. It works with any Git remote, GitHub and GitLab included. ## What the open beta adds - **Deploy from a repo**: connect a repo to Workers Builds. A push to `main` builds and deploys the Worker; pushes to other branches create or update Worker Previews. Only `main` works as the production branch for now - **Workers binding**: create and fork repos, read files and commits, issue repo-scoped Git tokens. The typical flow: a task arrives, a Worker forks the project for an agent, reads its `AGENTS.md`, and hands back a remote and a token - **Event subscriptions**: a repo emits events when it's created, imported, forked, deleted, pushed to, cloned or fetched. Hook CI, a code review agent or a deployment on them - **Metrics**: operations, pulls, pushes, errors and error rate per repo, in the dashboard or through the API Pricing has two dimensions. Operations (create, push, pull, clone and so on) cost $0.15 per 1,000 beyond the first 10,000 each month. Storage costs $0.50 per GB-month beyond the first GB. Repos stay stored until you delete them. Nothing is available on the Workers Free plan yet. ## The "next Git platform" competition The open beta post asks a question I find more interesting than the product itself: what does the foundation look like when hundreds or thousands of agents work on the same codebase at once? How do they know what the others are doing? What happens with conflicting changes? Who reviews all of it? And how do you keep track of WHY a change was made, beyond what changed? Cloudflare doesn't answer. It asks people to build the answer on Workers and Artifacts. The bar: multiple agents working on changes concurrently, at a minimum. They explicitly don't want GitHub with agents bolted on. Repositories, branches, pull requests, worktrees, code review and merge conflicts are all up for rethinking. - **Submit**: a 5 to 10 minute demo video, the source code under MIT, Apache 2.0 or BSD (2- or 3-clause), and instructions to run it - **Deadline**: October 14, 2026 - **Judging**: originality and quality of the prototype (50%), multi-agent concurrency, coordination, context, review and conflict handling (25%), ease of use (25%) - **Prize**: three finalists (announced October 16) present on stage at Cloudflare Connect in San Francisco on October 21, with travel for up to two people per team. The winner gets $25,000 in Cloudflare credits (valid 12 months) and a seat at the VIP speaker dinner Two details from the official rules matter more than the headline. First, only legal residents of the United States or Canada aged 18+ can enter, so Europeans (me included) are out. Second, submissions aren't confidential, and the rules say Cloudflare may build products that are similar to or compete with the entries. Contestants keep their IP, but the ideas become public R&D, and you're working for a shot at the prize. ## What I make of it I like the framing. GitHub was designed for humans who branch, commit and open pull requests at human speed. [[GitHub Agent HQ]] adds a control plane for agents on top of that model; the repository and the pull request stay the unit of work. Tools like [[Git Worktree|worktrees]] and [[GitButler]] help one developer run a handful of agents in parallel. Nobody has a convincing answer yet for coordination at the scale of hundreds of agents, and that's precisely the layer Cloudflare is outsourcing to the community. The skeptics have fair points too. When Artifacts launched, Hacker News commenters asked who the target market was (most agent platforms run on non-Cloudflare sandboxes plus GitHub), noted that operations cost a lot more than S3 PUTs, and worried about the 128 MB memory cap during delta resolution on large pushes. One of the authors replied that the Git interface is "by no means the end goal" and that they now have the parity to experiment with a more "agent first" version control system. That's the part I'll be watching. First signs of the community taking the bait: GitOrange, posted on Hacker News on October 2, is a single-tenant GitHub-like host running as one Worker, with repos in Artifacts, everything else in [[Cloudflare D1|D1]], and GitHub Actions workflows running on [[Cloudflare Containers]]. Useful, but it's GitHub as it exists today, which is exactly what the competition says it doesn't want. ## References - Source: We want you to build the next Git platform on Cloudflare (Dina Kozlov, Dillon Mulroy, Zebulon Piasecki; Cloudflare Blog, 2026-10-01): https://blog.cloudflare.com/next-git-platform-on-cloudflare/ - Artifacts: versioned storage that speaks Git (Cloudflare Blog, 2026-04-16): https://blog.cloudflare.com/artifacts-git-for-agents-beta/ - Competition page: https://www.cloudflare.com/git-competition/ - Competition official rules (PDF): https://www.cloudflare.com/documents/build-next-gen-git-platform-competition-terms.pdf - Artifacts documentation: https://developers.cloudflare.com/artifacts/ - Artifacts pricing: https://developers.cloudflare.com/artifacts/platform/pricing/ - Artifacts changelog: https://developers.cloudflare.com/changelog/product/artifacts/ - Workers Builds integration: https://developers.cloudflare.com/workers/ci-cd/builds/git-integration/artifacts-integration/ - ArtifactFS: https://github.com/cloudflare/artifact-fs - Hacker News discussion of the Artifacts launch: https://news.ycombinator.com/item?id=47792374 - Hacker News submission of the competition post (no comments when checked): https://news.ycombinator.com/item?id=49921168 - GitOrange (Show HN, 2026-10-02): https://github.com/choyiny/gitorange ## Related - [[Cloudflare]] - [[Cloudflare Workers]] - [[Cloudflare Durable Objects]] - [[Cloudflare Sandbox SDK]] - [[Cloudflare Agents SDK]] - [[Cloudflare R2]] - [[Cloudflare KV]] - [[Cloudflare Queues]] - [[Git]] - [[GitHub]] - [[GitHub Agent HQ]] - [[Git Worktree]] - [[GitButler]] - [[AI Agents]]