We want you to build the next Git platform on Cloudflare

GitHub was designed for a world of human programmers who organize code into repositories and collaborate using branches, commits, issues, and pull requests. However, the next era of software development will be built by a different kind of developer: agents. These agents are already writing more code than ever, fixing bugs, building features, writing tests, reviewing changes, updating dependencies, and performing routine maintenance.

As a result, the fundamental structure of the foundation must adapt to accommodate hundreds or even thousands of agents working on the same codebase simultaneously.

Key questions arise when considering the next GitHub platform: How do agents know what their colleagues are working on? How do they handle conflicting changes? How can we effectively review all the work produced by agents? How do we keep track of not just what changed, but also why a particular change was made?

Earlier this year, GitHub launched Artifacts, a versioned filesystem built on Git that can scale to millions of repositories. Artifacts provides a foundation of programmable primitives that developers can use to build their own products, workflows, and abstractions. Repositories can be created and forked programmatically, storing versioned code and agent context, and supporting Git operations familiar to agents.

With Artifacts in open beta, Cloudflare is hosting a competition to see who can build the next Git platform on Cloudflare, utilizing Workers and Artifacts. The goal is to explore new ways of managing concurrent agent work, preserving agent context, comparing multiple changes simultaneously, and deciding which changes should be deployed. The competition will feature top three projects, with the first-place team receiving $25,000 in Cloudflare credits and VIP access to Cloudflare Connect.

Artifacts offers several new features to support the development of the next Git platform. Workers Builds allow connecting an Artifacts repository to a Worker, automatically building the project upon code pushes and deploying updates to Workers. Branches can automatically create or update Workers Previews, providing isolated, shareable versions for testing before deployment.

The Artifacts binding enables direct interaction with Artifacts repositories from a Worker, allowing creation, forking, inspection of files and commits, and issuing Git tokens.

Artifacts events, such as repository creation, import, fork, deletion, pushes, clones, and fetches, can be subscribed to trigger various actions, such as CI runs, code review agents, or deployments. Additionally, selecting the jurisdiction for data processing (U.S. or EU) when creating a namespace ensures repositories follow the same restrictions.

Metrics for Artifacts repositories, including total operations, pulls, pushes, errors, and error rates, are available in the Cloudflare dashboard. Users can also query Artifacts metrics directly to build custom dashboards or monitoring systems.

Pricing for Artifacts will be based on repository operations and data storage, with billing beginning on October 15, 2026. Cloudflare is inviting developers to reimagine the Git platform for the agentic era using Workers and Artifacts, encouraging creative approaches beyond traditional repositories, branches, pull requests, code review, and merge conflicts. The competition aims to foster innovation in how agents collaborate on codebases at massive scale.