We want you to build the next Git platform on Cloudflare
GitHub was built for a world where humans write code, organize it into repositories, and collaborate through branches, commits, issues, and pull requests. But the next generation of software will be built by a different kind of developer: agents that are already fixing bugs, building features, writing tests, reviewing changes, updating dependencies, and handling routine maintenance. With hundreds or thousands of agents potentially working on the same codebase, Cloudflare asks how agents know what others are working on, how conflicting changes are handled, how their output is reviewed, and how changes are tracked not just by what changed but why.
The central question is what the next GitHub looks like, and Cloudflare wants developers to help answer it by building it. Earlier this year, Cloudflare launched Artifacts, a versioned filesystem that speaks Git and can scale to millions of repositories, designed from the start as programmable primitives for developers to build their own products, workflows, and abstractions. Artifacts provides repositories that can be created and forked programmatically, versioned storage for code and agent context, and the Git operations agents already know, leaving the layer above — agent coordination, review and merge workflows, and the developer experience for many agents on one codebase — for others to build.
Now that Artifacts is in open beta, Cloudflare is holding a competition to see who can build the next Git platform on Cloudflare using Workers and Artifacts. The goal is to make it possible to create a repository for every agent, session, task, or user at the scale agents require. Developers have already used Artifacts in several ways: vibe-coding platforms store the projects their users create, developers persist code and context from agent sessions, and others create isolated repositories so multiple agents can safely work from the same starting point and compare or merge results later.
Cloudflare also added new capabilities since the initial launch. Artifacts repositories can now be connected to a Worker through Workers Builds, so when a user or agent pushes code, Cloudflare builds the project and deploys the updated Worker for the production branch. Pushes to other branches automatically create or update Workers Previews, giving an isolated, shareable version of the work.