GitHub commits on pace for 14x growth, so Microsoft rents AWS
GitHub's commit volume is on pace to grow 14x in a single year, almost entirely from coding agents. Microsoft, which owns Azure, is reportedly renting Amazon's cloud to absorb it.
The kicker isn't 14 billion commits. It's that those are agent check-ins, not features shipped — agents now write to GitHub while they think, not after a human has.
One commenter recalls GitHub's founder telling a Microsoft exec years ago that Azure's virtual disks weren't fast enough on IOPS to host GitHub.
And the article making this claim is itself an AI-generated, mostly-empty React page from a self-described one-person, vibecoded site.
A 14x jump in one year, written by agents that commit while they think
The report at RuntimeWire is that GitHub is straining under AI-driven load and Microsoft is turning to AWS to handle the overflow. The load-bearing figure surfaced in the thread: commits were on pace to hit 14 billion in 2026, up from 1 billion in 2025. That is a 14x increase in a single year, and it is not 14x more features shipped.
So AI means 14x the checkins? That's not 14x features completed, but still... wow. — a commenter linking to his own site, chris.brooks6.com
The behavioral shift behind the number is the real story. Agents don't wait for a human to finish reasoning before they write.
GitHub used to get code after someone had thought about it. Agents are starting to use it while they think. — a developer building modulex.dev
The irony: Microsoft owns Azure and is renting Amazon's
Microsoft bought GitHub and runs Azure, yet the fix for its own platform's growth is a competitor's data centers. The thread reached for historical rhymes ("a Hotmail moment," an "Embrace, Extend, Extinguish" inversion), but the most concrete came from someone present at the origin. He recalls a Microsoft exec asking GitHub's founder what it would take to move GitHub onto Azure.
I was surprised that Tom had a response ready, saying that IOPS were really important and that virtual disks weren't fast enough. — the person who set up that first Microsoft-GitHub meeting
A former AWS employee offered why Amazon, specifically, can absorb a surge like this: the capacity-fulfillment machine is the actual product.
the scale and competence of the units fulfilling the colossal and unceasing growth in capacity demand… I still think of it basically as a logistics firm, with the shop and the public cloud merely a monetisation thereof. — a former AWS engineer of a decade ago
The source is the dead-internet punchline
Here the thread turned on the article itself. A reader inspected RuntimeWire and found a fully client-side React page with an empty body, broken title tag, 2007-style keyword stuffing, and — per the builder's own blog — AI-generated articles on a one-person site.
What kind of vibecoded website is this?… the entire page is client-side react with a completely empty body? — a Matrix developer, previously at Element
That is the loop closing on itself. Agents flood GitHub with commits; the surge gets reported on an AI-generated site; the report can't even be machine-read by a fetcher. The skeptical read: "mostly text, shouldn't be hard," several insisted — yet the platform that taught the world distributed version control is reportedly outsourcing its busiest year to its biggest rival. If commit volume is now decoupled from work completed, the capacity crunch isn't a success story. It's bots talking to bots, billed to Microsoft and rented from Amazon.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
New York wants to make posting a job you'll never fill illegal
Senate Bill S8877 would target "ghost jobs" — listings companies float with no intent to hire. The thread's first reaction wasn't celebration. It was: how would anyone ever enforce this?