We want you to build the next Git platform on Cloudflare

GitHub’s traditional model of human-driven collaboration is being reshaped by AI agents that write, test, and maintain code autonomously. These agents operate at scale, often working simultaneously on the same codebase, raising new challenges around coordination, conflict resolution, and traceability. Cloudflare’s Artifacts, launched earlier this year, provides a programmable foundation for repositories, versioned storage, and Git operations tailored to agent workflows. The platform enables developers to focus on higher-level coordination, such as reviewing agent-generated changes and merging conflicting updates, rather than reinventing basic version control.

Cloudflare has expanded Artifacts with new capabilities to integrate with Workers, its serverless platform. Code pushed to an Artifacts repository can trigger automated builds and deployments for Workers, while branches generate isolated previews for testing. Developers can also connect existing Workers to Artifacts or start new projects directly within the system. A programmable binding allows Workers to interact with repositories, enabling tasks like forking projects for agents, reading contextual files, and issuing repository-specific Git tokens. These features make Git workflows fully programmable, aligning with the needs of agent-driven development.

Artifacts now supports configurable data residency, allowing developers to set U.S. or EU jurisdiction when creating a namespace, with all repositories in that namespace adhering to the chosen location. The platform also introduces repository metrics in the Cloudflare dashboard, tracking operations, pulls, pushes, errors, and error rates. These metrics can be queried directly to build custom dashboards or monitoring systems. Artifacts pricing will be based on repository operations and data storage, with billing set to begin on October 15, 2026.

Cloudflare is hosting a competition for developers to build the next Git platform on Workers and Artifacts, encouraging innovation beyond traditional GitHub-like models. Participants are challenged to rethink repositories, branches, pull requests, and code review processes to accommodate multiple concurrent agents. The goal is to explore new ways to preserve agent context, compare simultaneous changes, and determine which updates should be deployed, fostering creativity in agentic-era software development.