[hansgru]

> I need to be sold on why I should use it as a product.

What about self-hosting for public and private repos? (Internet or intranet)?

It's main usage is for small teams and projects that don't want to put theirs source on external servers, nor do have the money for GitHub Enterprise.

[joeblau]

There are already multiple established solutions (which are noted in other comments) that are free, paid, open-source and closed source with large communities that solve this problem. At my last company, we had an Ubuntu machine running our git-server and it solved the issue you're saying.

Edit: You know what would make this awesome. If this project could some how extend GitHub via the API and somehow replace GitHub when it goes down. Sort of like a private HA solution to GitHub incase of an emergency. Now THAT is something that I'd look at and say "okay this solves a new challenge with the current state of hosted Git platforms."

[hansgru]

> There are already multiple established solutions

Of course there are, but everything I've tried was a paint to setup. GitBucket was the first project that was very easy to setup: in an existing Tomcat (or other container), just drop the WAR file, and everything works. Also no dedicated machine is required for this (I host it along with other applications)