When comparing Gitblit vs Phabricator, the Slant community recommends Phabricator for most people. In the question“What are the best self-hosted web-based Git repository managers?” Phabricator is ranked 4th while Gitblit is ranked 9th. The most important reason people chose Phabricator is:
Phabricator is completely free and open source. It's source code is hosted on [GitHub](https://github.com/phacility/phabricator/).
Ranked in these QuestionsQuestion Ranking
Pro Just works
Setting up is easy and usage is intuitive.
Pro Free and open source
GitBlit is free and open source (under Apache License) .
Gitblit is available for Windows, OS X and Linux.
Pro Built-in authorization in windows
So you don't have to worry about setting up OpenSSH on Windows.
Pro Free and open source
Phabricator is completely free and open source. It's source code is hosted on GitHub.
Pro Actively updated
Phabricator is quickly improving, with bug fixes and new features added often. There is an update to the changelog every couple of weeks.
Pro Bug tracker is included
Includes a bug tracker out of the box. Allows for managing bugs, creating issues, commenting on them and closing them.
Pro Built-in Q&A platform - Ponder
Instead of having to have separate Q&A tool, there's Ponder which takes out the hassle.
Pro Built-in Wiki and pages support
Pro Fully customizeable workboard
You can configure your workspace to deal with tasks, bugs, todo's, etc.
Pro Supports the three major version control systems
Support for Git, SVN and Mercurial is available.
Pro Super flexible bussiness rules (Herald)
Pro Able to review graphical asset changes as well as code.
Pro Fine grained access control
With using Spaces and Project and custom policies you can have any combination of access to any object inside of your own Phabricator instance.
Pro Designed by software engineers for software engineers
The engineering workflow is far superior to Github style branching and merging. Phabricator separates local representations of the repository from remote, which enables a variety of workflow optimisations, like stacked diffs on a single branch.
Pro Code ownership
Users can subscribe to files or even repositories and notifications will be sent when code you are subscribed to is changed.
Pro Command line access (via ARC)
Pro Able to track design mockups
You can track not only code bud also design mockups.
Pro Built-in voting
You can create voting in an instant and need not to rely on external tools.
Pro Built-in blogging platform
There's a great platform which you can use to post stuff, or use as an internal blog, dev blog, release anouncement place and many others.
Pro Built-in chatrooms
Pro Able to manage legal agreements for open source projects
Con No code reviews
It's not possible to start any code reviews on Pull Requests
Con Access controls are repository-based
Built in access controls are not branch-based.
Con No Squash Merge
There is no Squash Merge functionality
Con No project admins
There's no separation between a system admin and a project admin. There's owners for projects, but to create a new repository one has to be a general admin.
Con For someone who likes formality, this is not for you
Has slang, sarcasm, and other informal things. If you need to stay formal you shouldn't use this. Personally I like it but others may have different opinion.
Con Difficult to configure
Compared to a solution like Bitbucket Server (granted Phabricator offers more options), it is difficult to configure. Settings are scattered everywhere and you must drill down through several screens to find some of them. Documentation is very complete but also not always in parity with the application itself.