Software development is becoming much more parallel. Coding agents let a team have dozens or hundreds of related changes moving at the same time, creating more branches, reviews, CI runs, and automation than existing workflows were designed to absorb.

Today, we’re opening GitCafe in public beta. It is a Git forge built for teams where humans and coding agents may ship hundreds or thousands of changes a day. We’re building the hosting, review, CI, security, and automation layer for that way of working.

Hundreds of users are already on GitCafe, and we’re currently running trials with roughly a dozen YC companies.

Generating code is only part of the problem. Teams still need to understand what is changing, review it safely, keep CI moving, catch security issues, and coordinate work without becoming overwhelmed.

We’re not building GitCafe because putting repositories, code review, and CI in one product is new. We’re building it because we believe the workload those systems need to support is about to change dramatically.

We started by rebuilding the Git infrastructure itself. Now we’re closing the product gap feature by feature.

Recently, we added secret scanning, Buildkite and Harmont CI support, stacked diffs with Jujutsu and Sapling integration, and beta support for GitHub Actions.

These are foundational capabilities, not the destination. Building them on infrastructure we own gives us a base we can keep extending for higher-volume, agent driven development.

The honest version is that GitCafe is behind GitHub today. GitHub has spent more than a decade building an enormous product, and GitCafe does not yet have every workflow, administrative control, or integration that mature teams need. Some features are missing, some are experimental, and some edges are rough. We expect to earn the broader product surface, not claim it on day one.

We’re opening GitCafe now because the fastest way to improve it is to put it in the hands of teams doing real work.

If your team is already using coding agents heavily, try GitCafe at https://git.cafe and tell us where the workflow breaks down.

https://www.youtube.com/watch?v=blHKFEOmoFg