Raised $17M to Build What Comes After Git
Key point
GitButler raised a $17M Series A and laid out its vision for what comes after Git.
Details
GitButler raised a $17M Series A. The round was led by a16z, with continued participation from existing seed investors Fly Ventures and A Capital.
The core message is clear. GitButler says it isn't just building a better way to use Git, but infrastructure that redesigns how software itself is built.
Scott Chacon, a GitHub co-founder, explains that over the past 15 years he's watched Git become core foundational technology. But today's development environment still suffers from a problem: context keeps breaking down between tools, people, and now between people and agents.
As they see it, Git's existing model is still built around one person, one branch, one terminal, a linear flow. But actual development has already grown more complex, and the arrival of AI tools has made those limits even clearer.
As a first answer to this, a technical preview of the GitButler CLI was released last week. This CLI:
- is designed for short-lived branches and trunk-based workflows like GitHub Flow
- targets people, agents, and scripts alike
- supports stacked branches, multitasking, organizing changes, and easy undo
- can be applied directly to existing Git projects.
The bigger vision is more 'social' coding. GitButler envisions a future where version control tools:
- create logical, beautiful units of change based on the work done
- preserve agent interactions, related conversations, and team context
- surface the possibility of merge conflicts between teammates earlier
- make it more natural to collaborate by stacking one branch on top of a colleague's branch
- let each agent be aware of the work of other agents across the whole team.
Ultimately, this piece is a declaration that GitButler isn't building a "better git," but rather the foundational layer for the next generation of software development.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.