Cloudflare opens Artifacts beta and a contest to build the next Git platform

Cloudflare has put out a call to build what it calls the next GitHub, aimed at a world where software is written largely by agents. The company's argument is that GitHub was designed for humans who write code, organize it into repositories and collaborate through branches, commits, issues and pull requests. Agents, it says, are already fixing bugs, building features, writing tests, reviewing changes and updating dependencies. With hundreds or even thousands of agents working on one codebase at once, Cloudflare asks open questions: how do agents know what others are doing, what happens when their changes conflict, how do you review everything they produce, and how do you track not just what changed but why.

The foundation Cloudflare offers is Artifacts, which it launched earlier this year as a versioned filesystem that speaks Git and can scale to millions of repositories. It was designed as a set of programmable primitives: repositories that can be created and forked programmatically, versioned storage for code and agent context, and the Git operations agents already know. Artifacts is now in open beta, available to customers on the Workers Paid plan. Cloudflare says developers already use it in three ways: vibe-coding platforms store the projects their users create, developers persist code and context from agent sessions, and others create isolated repositories so multiple agents can start from the same point and compare or merge results later.

The post lists new capabilities added since launch. First, an Artifacts repository can be connected to a Worker through Workers Builds. A push triggers a build; the production branch deploys the updated Worker, while pushes to other branches create or update Workers Previews, which are isolated, shareable versions for testing. Second, a Worker can manage Artifacts directly through an Artifacts binding: create or fork repos, inspect files and commits, and issue repo-scoped Git tokens. The example forks a project for a new agent task, reads its AGENTS.md for instructions and hands the agent a remote and token. Third, Artifacts publishes events whenever a repository is created, imported, forked, deleted, pushed to, cloned or fetched, so a Worker can run CI, start a code review agent or deploy a change; the example starts a review workflow on each push event. Fourth, a U.S. or EU jurisdiction can be set when a namespace is created, and every repository in it follows the same restriction. Fifth, the dashboard now shows per-repository total operations, pulls, pushes, errors and error rate, and the metrics can also be queried to build custom dashboards.

On pricing, Cloudflare says Artifacts is priced on repository operations and the amount of data stored, and billing for usage begins on October 15, 2026.

The competition asks entrants to build their vision of a Git platform for the agentic era on Cloudflare Workers and Artifacts. Cloudflare suggests rethinking repositories, branches, pull requests, worktrees, code review and merge conflicts, or building new ways to preserve agent context, compare several changes at once and decide which one ships. It says it is not looking for GitHub as it exists today with agents added on top; at a minimum it wants to see multiple agents working on changes concurrently.

Entries need three things: a 5-10 minute video showing what was built, what it enables for agents and developers and how it works; a link to source code under a permissive open source license (MIT, Apache or BSD); and instructions for running or trying the project. Submissions are open until October 14, 2026. Cloudflare will select the top three projects and fly up to two members of each team to San Francisco for Cloudflare Connect to show their work. The first-place team also gets $25,000 in Cloudflare credits and invitations to the VIP speaker dinner on Monday night at Connect.

Key facts

Cloudflare's Artifacts, a versioned filesystem that speaks Git and is designed to scale to millions of repositories, is in open beta for Workers Paid plan customers.
New since launch: deploying Artifacts repos to Workers via Workers Builds, an Artifacts binding for Workers, event subscriptions, U.S. or EU data jurisdiction per namespace, and per-repository metrics.
Billing for Artifacts usage begins October 15, 2026, based on repository operations and data stored.
The competition runs until October 14, 2026; entries need a 5-10 minute demo video, permissively licensed source code (MIT, Apache or BSD) and run instructions.
The top three projects get a trip to Cloudflare Connect in San Francisco for up to two members each; first place also gets $25,000 in Cloudflare credits.

Why it matters

Cloudflare is making a public bet that the Git hosting model built around human workflows will need rethinking once hundreds or thousands of agents edit the same codebase at once. Instead of shipping its own answer, it supplies primitives (programmable repositories, forks, versioned storage for code and agent context) and asks outside developers to build the coordination, review and merge layer on top. The brief is explicit: not GitHub with agents bolted on, but at minimum multiple agents working on changes concurrently.

Who it affects

Teams building agent products and vibe-coding platforms are the direct audience; Cloudflare says such platforms already store user projects in Artifacts, and that developers use it to persist agent session code and context or to give multiple agents isolated repositories from the same starting point. Existing Workers users are affected by the new Workers Builds deploys and the Artifacts binding. Teams with data-location requirements get the U.S. or EU jurisdiction option. Anyone who wants to enter the contest is also in scope.

How to use it

Artifacts is available in open beta to customers on the Workers Paid plan. You can view or create repositories in the dashboard, or point a coding agent at the prompt in the post to set up a first repository and start pushing code. From a Worker, the Artifacts binding lets you create or fork repos, read files and commits, and issue repo-scoped Git tokens; event subscriptions can trigger CI, a code review agent or a deploy. To enter the competition, submit a 5-10 minute demo video, a link to source code under MIT, Apache or BSD, and instructions for running it, by October 14, 2026. Pricing is based on repository operations and stored data, with billing starting October 15, 2026.

How solid is it

This is Cloudflare's own announcement, written in the company's voice, so the capabilities and the contest rules are first-party statements. The scale claim (millions of repositories) is a design claim rather than a measured result, and the post gives no usage figures such as repository, developer or customer counts. The usage examples (vibe-coding platforms, persisted agent sessions, isolated repos) are described in general terms without named customers. Artifacts is still in open beta and no general availability date is given.

Risks and caveats

Billing starts October 15, 2026, the day after the contest deadline, and no per-unit prices or rates for operations or storage are given, so costs cannot be estimated from the post. Using Artifacts requires the Workers Paid plan, and the programmable workflow is built around Cloudflare Workers, which ties a project to that platform. Contest entries must be released under a permissive open source license. Judging criteria, named judges and prizes for second and third place are not stated; only the trip for the top three and the $25,000 credits for first place are.

“We aren’t looking for GitHub as it exists today with agents added on top.”

— Cloudflare, blog post