We Want You To Build The Next Git Platform On Cloudflare

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get monitors, keyboards and dev gear delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Cloudflare has opened a competition inviting developers to build a Git platform for software projects increasingly handled by AI agents. The effort uses Cloudflare Artifacts, now in open beta, alongside Workers; the company has also added deployment, repository automation, event subscriptions, data-jurisdiction controls and metrics.

Cloudflare is inviting developers to build a new Git platform for software work involving AI agents, through a competition using its Artifacts repository service and Workers. The announcement comes as the company opens Artifacts to beta users and adds tools for deploying code, automating repository workflows, and choosing where repository data is stored.

Cloudflare’s proposal is based on a shift in how software is developed: rather than relying only on people working through repositories, branches, commits, issues and pull requests, the company expects agents to take on more coding and maintenance tasks. Its blog describes potential workflows in which hundreds or thousands of agents operate on the same codebase. That scale raises questions about coordinating work, handling conflicting edits, reviewing output and recording why changes were made.

Cloudflare says Artifacts provides the underlying versioned storage, with Git-compatible operations and the ability to create and fork repositories programmatically. The company says the service is designed to scale to millions of repositories. It wants competition participants to build the application layer above that foundation: tools for agent coordination, change review and merging, and the experience for developers supervising the work.

New integrations let developers connect an Artifacts repository to a Worker through Workers Builds. Cloudflare says pushes to a production branch can trigger a build and deployment, while pushes to other branches can create or update preview Workers. A Worker can also use an Artifacts binding to create or fork repositories, inspect files and commits, and issue repository-scoped Git tokens. Repository events—including pushes, forks and imports—can trigger automated workflows such as testing or code review.

The company has also added U.S. and EU data-jurisdiction choices for Artifacts namespaces, with repositories in a namespace following its selected restriction. Cloudflare says its dashboard now displays repository metrics including operations, pulls, pushes, errors and error rate. These additions are presented as capabilities available alongside the open beta; the blog post does not describe a finished, company-built replacement for GitHub.

Building Tools for Agent Collaboration

The announcement matters because it shifts attention from storing source code to coordinating automated contributors. If agents make changes independently and in parallel, a platform needs ways to give each one an isolated workspace, preserve relevant instructions and context, and route proposed changes through review. Cloudflare’s repository forks and event-triggered workflows are building blocks for such systems, while the competition asks developers to decide how those pieces should work together.

For developers, the approach could support custom processes rather than requiring every team to adopt one fixed collaboration model. A Worker could assign a task, create a repository fork, start an agent, and respond to its push with automated checks or review. That programmability may be useful to companies building coding agents and development tools, but it also leaves the product design and policies—such as conflict resolution and human approval—to whoever builds on the platform.

The proposal also gives Cloudflare a way to encourage use of its developer services in a new category. Artifacts supplies versioned storage, while Workers can run the automation surrounding it. The competition is a call for third-party builders, not evidence that Cloudflare has already solved the operational or governance problems of large-scale agent collaboration.

Artifacts Moves Into Open Beta

Cloudflare says it launched Artifacts earlier in the year as a programmable, Git-speaking versioned filesystem. It describes use cases including storing projects made on vibe-coding platforms, preserving code and context from agent sessions, and giving multiple agents separate repositories from a shared starting point. Those examples are the company’s account of how developers have used the service; the post does not provide adoption figures.

The latest announcement pairs that storage layer with integrations for building and deploying Workers, repository management from Workers, subscriptions to repository events, jurisdiction selection and dashboard metrics. Together, these features let developers connect repository activity to code execution and automation. The company says Artifacts remains in open beta, so the service and its capabilities are still being developed.

“We want you to help us answer it, by building it out.”

— Cloudflare, in its blog post

Competition Details Still Missing

The blog post does not give a competition deadline, judging criteria, prizes, or submission process. It also does not identify selected participants or projects, or say whether a winning entry will become a Cloudflare product. Those details would help developers understand the scope and expectations of the challenge.

Cloudflare describes a possible future involving very large numbers of agents, but the post does not quantify current agent usage or show how the proposed workflows perform at that scale. It also leaves open how builders should handle overlapping edits, review quality, permissions, accountability for agent-generated code, and when human approval is required. Artifacts’ open-beta status means its capabilities may also change.

Developers Build Above the Repository Layer

The next step is for developers to use Artifacts and Workers to build and submit their proposed Git platforms. Cloudflare has not stated a timetable or described how entries will be evaluated in the supplied announcement, so the competition’s milestones remain unclear.

As projects emerge, the key developments to watch are whether they offer practical ways to coordinate agents, review and merge changes, and preserve the reasoning behind code edits. Further Cloudflare updates may clarify competition rules and the evolution of Artifacts during its open beta.

Key Questions

What did Cloudflare announce?

Cloudflare announced a competition inviting developers to build a Git platform for agent-driven software work using its Artifacts and Workers services.

Is Cloudflare launching a new GitHub competitor?

The announcement is a call for developers to build the platform on Cloudflare’s infrastructure. It does not announce a finished Cloudflare-built replacement for GitHub.

What is Artifacts?

Artifacts is Cloudflare’s versioned filesystem with Git-compatible operations. The company says developers can create and fork repositories programmatically and use them to store code and agent context. It is in open beta.

What new capabilities did Cloudflare describe?

Cloudflare described Workers Builds integration, repository management through a Worker binding, event subscriptions for repository activity, U.S. and EU data-jurisdiction options, and dashboard metrics for repository operations and errors.

When is the competition due, and what are the prizes?

The supplied announcement does not state a deadline, judging rules, or prizes. Cloudflare’s blog post also does not explain how entries will be submitted or whether a winning project will become a company product.

Source: hn