Cloudflare opens Artifacts and sets a next-Git contest

Cloudflare is inviting developers to build a replacement for Git on top of its own platform, opening its Artifacts repository service in beta and setting a competition with a 14 October deadline.

Repositories built for agents, not people

Artifacts is Cloudflare's answer to a problem it says today's Git hosts were never designed for. GitHub, the company argues, was built for humans who write code, organise it into repositories and collaborate through branches and pull requests. Agents now write more code than ever - fixing bugs, building features, reviewing changes and updating dependencies - and the open question is how thousands of them work on one codebase at once without overwriting each other.

What is new since launch

Artifacts arrived earlier this year as a versioned filesystem that speaks Git and scales to millions of repositories. Ahead of the open beta Cloudflare has added several capabilities. A repository can now be connected to a Worker through Workers Builds, so a push builds the project and deploys the production branch automatically, while pushes to other branches create or update previewable Workers. A Worker can also drive Artifacts directly through a binding, creating or forking repositories, reading files and commits and issuing repository-scoped Git tokens, which turns the workflow itself into code.

Artifacts publishes an event whenever a repository is created, imported, forked, pushed to or fetched, and developers can subscribe to those events to trigger the next step - a CI job, a deployment or a code-review agent. Repositories can be pinned to a US or EU data jurisdiction at the namespace level, per-repository metrics covering operations, pulls, pushes, errors and error rate are visible in Cloudflare's dashboard, and billing for storage and operations begins on 15 October.

The competition, and what it pays

The contest asks for a working Git platform built on Workers and Artifacts. Cloudflare is explicit that it does not want today's GitHub with agents bolted on, and that entries must show at least several agents working on changes at the same time. Each entry needs a five-to-ten minute video, source code under a permissive licence such as MIT, Apache or BSD, and instructions for running the project. Submissions close on 14 October.

Cloudflare will choose three projects and fly up to two people from each team to San Francisco for its Connect event, where they will show their work. The winning team also receives $25,000 in Cloudflare credits and invitations to the VIP speaker dinner.

Our opinion

Cloudflare is doing here what it does best: taking a piece of infrastructure everyone assumed was settled and asking what it looks like when the workload underneath it changes. Git's assumptions - that a human writes a branch, opens a pull request and waits for review - fray badly when the author is a process that can produce a hundred commits before lunch, and the genuinely interesting part of Artifacts is not the storage but the event stream, which is what lets a platform react to agents rather than merely host them. Outsourcing the hard design questions to a competition is shrewd. What Cloudflare cannot outsource is the harder one: a repository is a social contract as much as a filesystem, and no amount of programmable forking decides who is allowed to merge what. Whether the agentic era gets one GitHub or a thousand incompatible islands depends on the people it is asking to apply.