GoKawiilToday we’re announcing that GitButler has raised a $17M Series A led by a16z with continuing support from our lead seed investors, Fly Ventures and A Capital.
I know what you’re thinking. You’re hoping that we’ll use phrases such as “we’re excited,” “this is just the beginning,” and “AI is changing everything”. While all those things are true, I’ll try to avoid them and instead make this announcement a little more personal.
Our new board member, a16z's Peter Levine, and myself at the GitButler Series A signing. We're excited to have Peter join us - he and I also worked together on GitHub's board.
For me this is a long story.
I was one of the cofounders of GitHub and over the last 15 years I’ve watched Git go from a rather niche developer tool written for a very esoteric collaboration style to the foundational infrastructure of all software development on the planet. I may have even had a small hand in some part of that.
What I learned from watching that story unfold is that developer platforms win when they remove friction from collaboration, and when they let the people producing code have less overhead to deal with.
GitButler was started three years ago because we felt like our development practices have been shoehorned into what Git could do for such a long time, it would be amazing to see what we could do with tooling that was actually designed for those practices.
That’s fundamentally what is behind this round.
We think software development is quickly moving into a new phase, and the problem that Git has solved for the last 20 years is overdue for a redesign. Today, with Git, we're all teaching swarms of agents to use a tool built for sending patches over mailing lists. That's far from what is needed today.
At GitHub, one thing became painfully clear over and over: developers don’t struggle because they can’t write code. They struggle because context falls apart between tools, between people, and now between people and agents. The hard problem is not generating change, it’s organizing, reviewing, and integrating change without creating chaos.
... continue reading