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 invited developers to compete to build a Git platform for software projects increasingly worked on by AI agents. Its open-beta Artifacts service supplies Git-compatible repositories and programmable workflows; the competition’s rules, timeline and prizes were not specified in the supplied announcement.

Cloudflare is inviting developers to build what it calls the next Git platform using Workers and Artifacts, its open-beta, versioned filesystem that supports Git operations. The competition targets tools for software development involving large numbers of AI agents, with Cloudflare providing repository infrastructure and asking participants to build the collaboration, review and coordination layer above it.

Cloudflare’s proposal starts from a change in how software may be produced: rather than mainly human developers coordinating work through repositories, branches, commits, issues and pull requests, the company expects agents to write and maintain more code. Its post describes agents fixing bugs, building features, writing tests, reviewing changes and updating dependencies. The company frames the challenge around how potentially hundreds or thousands of agents might work on a shared codebase, avoid or resolve conflicting edits, and make their work reviewable.

Cloudflare says it launched Artifacts earlier this year as a Git-speaking, versioned filesystem intended to scale to millions of repositories. The service is now in open beta. The company says developers can create or fork repositories programmatically, store code and agent context, and use familiar Git operations. The competition asks builders to use those capabilities as infrastructure while creating their own ways to coordinate agent work, review and merge changes, and present the workflow to developers.

The announcement also describes new integrations and controls. Through Workers Builds, an Artifacts repository can be connected to a Worker: pushes to the production branch can trigger a build and deployment, while pushes to other branches can create or update Workers Previews. A Worker can also use an Artifacts binding to create or fork repositories, inspect files and commits, and issue repository-scoped Git tokens. Artifacts event subscriptions can trigger follow-on tasks such as tests, code review or deployment.

Cloudflare says customers can select a U.S. or EU data jurisdiction when creating a namespace, with repositories in that namespace following the selected restriction. The company has also added dashboard metrics for repository operations, pulls, pushes, errors and error rates. These are product capabilities described in Cloudflare’s announcement; the post does not provide independent performance benchmarks or adoption figures.

Building Git Workflows for Agents

The proposal matters because it puts a platform provider’s infrastructure behind a broader question for software teams: whether collaboration tools designed around people will be sufficient when agents generate and modify code at high volume. A system handling many parallel contributions may need ways to assign isolated workspaces, record why an agent made a change, detect conflicts, and route changes through review. Those needs are the problem Cloudflare is asking competition entrants to address.

For developers, the approach separates repository storage and Git operations from the product experience built on top. Teams could use Cloudflare’s services as a foundation while designing their own review interfaces and automation. For Cloudflare, the contest may encourage applications that use Workers and Artifacts, but the announcement does not say how entries will be judged or whether Cloudflare intends to adopt or operate a winning platform.

The announcement is not evidence that agent-run development has displaced human-led software work, nor does it establish that a large number of agents can safely collaborate without oversight. Cloudflare presents that scale as a future design challenge. The practical value of any resulting platform will depend on how well it handles conflicts, traceability and human review—not just how quickly it can create repositories or trigger workflows.

Artifacts Supplies the Repository Layer

Cloudflare describes Artifacts as a set of programmable primitives, rather than a complete GitHub replacement. The service is intended to let developers create a repository for each agent, task, session or user. In the company’s examples, a Worker can fork a project when a task arrives, read its instructions file, and provide the agent with a repository and access token. A push event can then start a workflow that sends the change to a review agent.

The new Workers Builds connection extends that model from repository management to deployment. Production-branch pushes can build and deploy a Worker, while other branches can receive preview deployments. Cloudflare says developers may connect an existing Worker or begin a new project with its code stored in Artifacts. These integrations give competition builders examples of how code changes could move through an automated pipeline, though they do not prescribe a particular interface or review policy.

The jurisdiction setting and dashboard metrics address operational needs alongside workflow design. Cloudflare says namespaces can be restricted to U.S. or EU data processing and storage, and that repository-level metrics include operation counts and error rates. The post does not detail further jurisdiction options or provide specific metric results.

“That is the layer we want you to build.”

— Cloudflare, in its blog announcement

Competition Details Still Missing

The announcement does not specify the competition’s deadline, entry requirements, judging criteria, prizes or number of winners. It also does not say whether Cloudflare will fund, acquire, host or officially support a project that wins, or whether the event is intended primarily to showcase prototypes.

Cloudflare’s post describes Artifacts as being in open beta but does not provide service-level guarantees, pricing details, capacity limits or comparative performance data in the supplied material. It also leaves open how builders should handle agent identity and permissions, conflicts between simultaneous changes, accountability for generated code, and the level of human approval required before deployment. Those questions will affect whether a platform built on the service can meet the needs of production software teams.

Builders Shape the Next Layer

Cloudflare says the competition will use Workers and Artifacts, and its post points developers to the newly described repository, event, deployment and jurisdiction features as building blocks. The next visible step is for participants to create tools on top of those services; Cloudflare has not supplied a competition schedule or a date for results in the announcement.

Readers interested in taking part will need to look for Cloudflare’s competition rules and any later updates for submission instructions, eligibility, evaluation and deadlines. Further details are also needed to establish what, if anything, Cloudflare will do with winning entries and how the open-beta service will develop.

Key Questions

What has Cloudflare announced?

Cloudflare announced a competition to build a Git platform using its Workers developer platform and Artifacts, an open-beta versioned filesystem with Git operations.

What does Cloudflare expect builders to create?

The company is asking builders to develop the layer above repository storage: tools for agent coordination, change review and merging, and a developer experience for projects where many agents may work in parallel.

What is Artifacts?

Artifacts is Cloudflare’s Git-compatible, versioned repository service. Cloudflare says it supports programmatic repository creation and forks, code and agent-context storage, and Git operations.

Can Artifacts changes trigger builds or reviews?

Cloudflare says Workers Builds can build and deploy changes pushed to a connected repository, with previews for other branches. Artifacts events can also trigger workflows, including automated code review.

When are entries due, and what are the prizes?

The supplied announcement does not state a deadline, prize, judging process or winner-selection plan. Those details remain to be confirmed by Cloudflare.

Source: hn