Learn how GitButler and GitComet differ in their key features, development activity, technology stack and community adoption, so you can decide which of these git clients is best for you.
Last 30 days
Last commit
7 hours agoRepository age
4 yearsVersion
0.22.3License
FSL-1.1-MITRepository
gitbutler
Last 30 days

Both GitButler and GitComet have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
GitButler significantly outpaces GitComet in community adoption with 21,829 stars compared to 938 stars on GitHub. This 23.3x difference suggests GitButler has a much larger and more active community. In terms of developer contributions, GitButler has 1,031 forks, indicating strong developer engagement.
GitComet is growing faster, adding 77 stars in the last 30 days (+8.9%) against adding 156 stars for GitButler (+0.7%). GitComet is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with GitButler last updated 7 hours ago and GitComet 11 hours ago.
Both tools share common technology foundations, being built with Bash, Rust. However, they differ in their additional technology choices: GitButler uses JavaScript, CSS, Typescript, Tauri, SvelteKit, Rails.
GitButler has been in development longer, starting 4 years ago, compared to GitComet which began 9 months ago. This 3.0-year head start suggests GitButler may have more mature features and established processes.
The projects use different licenses: GitButler is licensed under FSL-1.1-MIT while GitComet uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Git Clients.