We Want You To Build The Next Git Platform On Cloudflare

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on networking and server gear

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

Cloudflare is inviting developers to build a new Git platform for software development increasingly handled by AI agents. Its competition will use Artifacts, now in open beta, with Workers for programmable repository workflows; details such as deadlines and prizes were not provided in the announcement.

Cloudflare is holding a competition for developers to build a new Git platform designed for software projects involving AI agents, using its Artifacts repository service and Workers. The company says Artifacts is now in open beta and provides programmable, Git-compatible storage, while the competition focuses on the coordination, review and collaboration tools built above it.

Cloudflare frames the proposal around a shift from software development organized mainly around human contributors, branches and pull requests to work involving hundreds or thousands of agents on the same codebase. The company says agents already handle tasks such as writing tests, fixing bugs, updating dependencies and reviewing changes. It argues that this creates practical questions about how agents track one another’s work, resolve conflicting edits and preserve the reasons behind changes.

The company says it launched Artifacts earlier this year as a versioned filesystem that speaks Git and is designed to scale to millions of repositories. It describes the service as a collection of primitives: repositories can be created or forked programmatically, and versioned storage can hold code and agent context. Cloudflare is asking builders to develop the layer above those capabilities, including how work is assigned, changes are reviewed and contributions are merged.

Cloudflare also listed recent additions to Artifacts. Repositories can be connected to Workers Builds so pushes to a production branch can trigger a Worker deployment, while pushes to other branches can create or update preview deployments. Workers can use an Artifacts binding to create or fork repositories, inspect files and commits, and issue repository-scoped Git tokens. Artifacts event subscriptions can trigger automated actions after repository activity, and customers can select U.S. or EU data jurisdiction for a namespace. The dashboard now displays repository operation, pull, push and error metrics, according to the company.

Building Tools for Agent Teams

The announcement targets a developing infrastructure need: when software agents can make changes independently, teams may need workflows that track tasks and revisions across many separate contributors. Conventional repository features remain part of the process, but Cloudflare is inviting developers to test whether agent-specific coordination and review tools can be built on top of programmable Git storage.

For developers, the competition offers a chance to build against Cloudflare’s infrastructure rather than first creating repository storage and deployment systems from scratch. If the approach proves useful, Workers could automate steps from creating an isolated repository for a task to launching a review workflow after a push. These are capabilities Cloudflare describes as possible uses of its APIs; the announcement does not establish that a complete platform or standard workflow has emerged.

The contest also gives Cloudflare a way to attract developers to Artifacts while the product remains in open beta. Its appeal will depend on how well the service performs for real workloads, what limits or costs apply, and whether developers want to build a new platform rather than extend existing tools.

Artifacts and Workers Capabilities

Cloudflare says its starting point is not a finished replacement for GitHub. Artifacts supplies repository primitives, while the proposed competition asks participants to create the user-facing collaboration and automation layer. The distinction matters: the blog post describes a platform-building invitation, not the launch of a new Cloudflare-operated Git hosting product.

Among the example workflows in the announcement, a Worker can fork a project for a new agent task, read repository instructions such as an AGENTS.md file and provide the agent with a repository remote and token. Separately, event subscriptions can notify automation when a repository is pushed to, allowing a Worker to start a code-review workflow. Cloudflare presents these as examples of programmable workflows, not as evidence that a particular review system is already available to all users.

Workers Builds connects repository changes to deployment. Cloudflare says production-branch pushes can deploy an updated Worker, while changes on other branches can produce shareable previews. The added jurisdiction setting lets customers specify U.S. or EU storage and processing for repositories in a namespace. The company also reports dashboard metrics for repository activity and errors, but the supplied announcement does not give performance figures or usage totals.

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

— Cloudflare, in its blog post

Contest Terms and Product Limits

The announcement does not specify the competition’s entry deadline, judging criteria, prizes or how participants should submit projects. It also does not describe the service’s pricing, repository or operation limits, or the full availability and support terms for the open beta.

Cloudflare’s claims about scaling to millions of repositories and the benefits of agent-driven development are company statements; the post includes no independent benchmarks or comparative results. It is also not clear what safeguards, access controls or conflict-resolution approaches builders will adopt when multiple agents work on the same project. The company has asked participants to tackle those design questions rather than announcing one settled solution.

Builders Shape the Next Layer

Developers can use the open-beta Artifacts service and Workers to build entries for the competition, according to Cloudflare. The company’s announcement points to repository creation and forking, Git-compatible operations, event subscriptions, deployment previews and data-jurisdiction settings as available building blocks.

The next concrete details to watch for are the contest rules, submission process and schedule, none of which appear in the supplied announcement. Until Cloudflare provides those terms and participants demonstrate their projects, it remains an open invitation to build—not confirmation that a new agent-focused Git platform has been selected or launched.

Key Questions

What did Cloudflare announce?

Cloudflare announced a competition inviting developers to build a Git platform for software development involving AI agents, using its Artifacts and Workers services.

Is Cloudflare launching a new GitHub competitor?

The announcement does not present a finished Cloudflare-operated competitor. Artifacts supplies repository capabilities, and Cloudflare is asking developers to build the coordination, review and collaboration layer above them.

What is Artifacts?

Cloudflare describes Artifacts as a versioned filesystem that speaks Git. Its stated capabilities include programmatic repository creation and forking, storage for code and agent context, and repository operations accessible through Workers.

What can developers build with Workers and Artifacts?

Cloudflare’s examples include creating a repository for an agent task, reading project instructions, responding to repository events with automated reviews, and connecting pushes to Worker deployments or previews.

When is the competition, and what are the prizes?

The supplied announcement does not state a deadline, schedule, judging criteria or prizes. Cloudflare says Artifacts is in open beta, but further contest terms were not included.

Source: hn