GitButler Raises 17M to Build What Comes After Git: Post-Git Version Control

GitButler Raises 17M Series A to Build the Post-Git Version Control System

GitButler, the company behind the popular Git client of the same name, has raised a 17M Series A to build what they call the next generation of version control. The announcement has gained 95 points on Hacker News with 185 comments, sparking intense debate about whether Git needs replacing.

The Problem with Git

Git has been the dominant version control system for over 15 years, but it has well-known issues:

• Steep learning curve: Branching, rebasing, and merge conflicts confuse beginners
• Poor UX: Command-line interface is powerful but unfriendly
• Large monorepo problems: Git struggles with repositories containing millions of files
• Slow for large binary files: Despite Git LFS, binary handling remains awkward
• Collaboration overhead: Feature branches, code reviews, and merge workflows add friction

GitButler Vision

GitButler proposes a fundamentally different approach:

• Virtual branches: Work on multiple features simultaneously without traditional branching
• Automatic conflict resolution: Smart merging that reduces manual conflict resolution
• Per-line ownership: Track which changes belong to which task without switching branches
• Integration with existing Git: Not a replacement but an evolution that outputs standard Git commits

The 17M Funding

• Investors: Not disclosed in the announcement
• Use of funds: Expanding the engineering team and developing the new version control system
• Timeline: The post-Git system is described as a longer-term vision beyond the current GitButler client

Community Reaction

The 185-comment HN thread reveals divided opinions:

Skeptical:

• Git is good enough for most use cases
• The Git ecosystem (GitHub, GitLab, CI/CD) is too entrenched to replace
• Previous attempts to replace Git (Mercurial, Bazaar, Pijul) all failed
• 17M is a lot for a company with no clear technical moat

Optimistic:

• Git UX genuinely needs improvement
• Virtual branches solve a real pain point
• AI-assisted code changes need better version tracking than Git provides
• The team has proven they understand developer workflows through the GitButler client

Competitive Landscape

Source: blog.gitbutler.com / HN — 95 points, 185 comments