Pinned Tweet
We rebuilt Enroute’s Git infrastructure: it now handles 7,600+ concurrent pushes per second into one repo at millisecond latency.
How?: stateless compute, a replicated ledger for every ref update, object storage for data.
Write-up: enroute.sh/blog/everyone-is-…
🗞️New write-up on how we scaled @enroute_sh horizontally in v0.4.0!
Enroute now scales to 300k repos on a single cluster with up to 24k pushes/s. We went deep on the limits of scaling Git horizontally and why this meant moving beyond Multi-Raft
enroute.sh/blog/scaling-hori…
Everyone knows that agents are great at coding! Fact is, the amount of code and the rate of change will only grow exponentially from here.
We humans are notoriously bad at thinking in exponential terms, so it’s hard to imagine what that world will look like. Code will become the heart of every company, and every person will produce code, both at work and in their personal lives.
At @enroute_sh, we’re building for the most demanding workloads out there, and we’re just getting started. We’re already seeing tons of exciting developments that our infrastructure is built to support:
🤖 Coding agents turning into forges
🏭 Teams automating larger parts of their workflows while pushing straight to main
🤝 New forges built for humans and agents working together
⚙️ AI products helping enterprises automate their workflows by building custom applications
🗂️ Products using Git as embedded version control for agent artifacts
🖥️ Repos co-located with CI runners and sandboxes, without running into GitHub rate limits
🧑💻 Personal agents creating personal software
New @enroute_sh version is out 🚀
📈 Enroute now also scales horizontally
⚡️ 300k repos on a single cluster at 20k pushes/s
👀 We are building for the most demanding agentic workloads out there, with plenty more to come!
github.com/enroute-sh/enrout…
If you want to enforce similar rules server-side, so they run on every push from every human and agent and can't be skipped, try out @enroute_sh. It’s only a few lines of code in your own stack.
Prompt of the day:
Create a pre-commit hook that prevents files over 5,000 tokens. Tokens = bytes/4.
Run only on staged files. Ignore files which are not authored by agents, like lockfiles or codegen.
Provide explicit instructions on how to split files in the error message.
The simplest investment I ever made in my codebase. So good.
3
262
Buckle up, GitHub!
Stop working around your source control and make it actually fit your agentic workflows. You have options!
2
5
312
🔥🔥🔥 Indeed! OpenAI is buying Git infra. Codex is becoming a forge, and Git hosting will keep moving away from GitHub.
If you want to build on open Git infra, check out @enroute_sh:
7.6k+ pushes/s
Fully programmable via hooks
Designed with modern database principles in
mind
Git infrastructure is 🔥🔥🔥
@OpenAI buying @pierrecomputer fresh off launching its new Git backend, Pando - axios.com/2026/11/04/openai-…
After @AnthropicAI replaced Git with Scion and @cursor_ai launched Origin 💥
Anthropic alone runs ~25 million code checkouts a day for CI.
Git was built for humans working offline but now agents are always online… source-control needs to SCALE.
Watching entire.com code.storage enroute.sh atomic.dev - who else is building here?
2
9
517
Congrats to the @pierrecomputer team! Looks like Codex will become a code forge soon.
For everyone who wants to build on open Git infra: Go check out @enroute_sh
> Extremely fast: 7.6k pushes/s
> Fully programmable via hooks
> Built like a modern cloud database: compute/storage separation, distributed consensus layer, object storage backend
10
500
Super interesting read. Love that they are doubling down on Git as well.
Already going through in finer detail to see what we can learn from this to make @enroute_sh even better.
First @AnthropicAI, now @OpenAIDevs. Like OpenAI, we believe Git is still the right tool for the job.
Very soon, many more teams will hit source control scaling limits. Code is growing exponentially, and Git needs new infrastructure to keep up with agents.
If you’d rather not build your own VCS, check out @enroute_sh for fast, programmable Git infrastructure.
Have been working recently on making @enroute_sh scale better for large numbers of repositories. Part of that is a new per-repo consensus impl that’s inspired by Vertical Paxos.
Anyway, seems like this improves single repo throughout and latency as well? 🤔
This kind of feedback makes my day! ♥️
Super cool to see people building their own code forges on top of @enroute_sh.
We’ve also built our own forge for dogfooding Enroute, so it works exactly the way we want. The UI is super clean, and instead of PRs we have a simple breakdown and summary of everything your agent changed.
Fun fact: It runs on a single @flydotio machine and is still the fastest thing out there.
Nice comeback from @github after the (re-) launch of @GoEntire this week. Seems like 7k+ pushes/s is how you build Git infra these days.
Go check out @enroute_sh if you want to build on open-source git infra with that kind of performance already today!
I learned today that walgit won’t be maintained going forward.
If you are looking for a solution that combines "Git + Rust + Object storage + Open-source" have a look at @enroute_sh
hey @tobi any interest on continue improving walgit? I took few PRs made to your version into my fork, moving into adding direct integration with @nats_io so I can do all the event processing from it. Thinking on adding a CI to see how the whole thing could work for Agents, after that I want to move to treat GitHub as a fallback cache.
8
338
The @enroute_sh Git server is not only extremely fast but also fully programmable. Start it with a single command on your machine and build against it. Self-host it on your own VPS or deploy it as a multi-Raft cluster for high availability. Any setup is just a config change on the same binary.
Read our blog post to get the details! enroute.sh/blog/four-ways-to…











