Phabricator

Phabricator is a suite of open-source tools that software teams once used to build software together — a single web application bundling code review, repository hosting, bug and task tracking, and internal wikis. Its best-known component was Differential, a code-review tool where engineers proposed changes and reviewers commented before the code merged; alongside it sat Diffusion for browsing repositories, Maniphest for tracking tasks and bugs, and Phriction for documentation. Originally built inside Facebook and later maintained by a company called Phacility, Phabricator was aimed squarely at engineering workflows, not marketing ones. It is worth stating plainly that Phabricator is a developer tool, not a martech product: it has nothing to do with campaigns, audiences, or analytics. It belongs in a glossary of technology terms because engineering tools shape how the software behind marketing gets built, not because it markets anything itself.

The single most important fact about Phabricator today is that it is no longer actively developed. In 2021, Phacility announced it was winding down and put Phabricator into minimal maintenance, effectively ending official development. Rather than let the project die, its community created a fork — a new project built from the same code — called Phorge, which released publicly in 2022 and continues to be maintained. So while plenty of teams still run Phabricator installations, the software itself is a legacy product, and new adopters are steered toward Phorge or toward modern alternatives. Any honest description has to lead with that status: Phabricator was a capable, integrated developer suite, but it is now discontinued, and its living continuation is Phorge. Treating it as a current, supported product would be misleading.

Phabricator competed with the platforms most teams now use — GitHub, GitLab, and Azure DevOps — but with a distinct philosophy. Where those platforms grew around a pull-request or merge-request model, Phabricator championed a different code-review workflow built on individual changes rather than branches, which some engineers still prefer for keeping review focused. It was also self-hosted and integrated: one installation gave you review, repositories, and task tracking without stitching together separate services. That integration was its strength. Its weakness, in the end, was momentum: as GitHub and GitLab added rich review, issue tracking, and continuous-integration features and captured the open-source community, a self-hosted suite maintained by a small company struggled to keep pace, and eventually its maintainers stepped back. Phorge now carries that same integrated, opinionated approach forward for teams who value it.

The practical contrast matters when you compare Phabricator to something like Azure DevOps or a CI server like Jenkins. Azure DevOps is a broad, actively developed, commercially supported suite covering repositories, boards, and pipelines; Jenkins is a live open-source automation server for building and deploying code. Phabricator overlaps with the repository and review parts of that world but not the automation, and — crucially — it is no longer maintained, while those tools are. So if you are choosing a system today, Phabricator is not the candidate; Phorge is its supported descendant, and the mainstream platforms are the common defaults. Understanding Phabricator is mostly useful for reading legacy setups, appreciating an influential code-review model, and knowing where the project went after its maintainers moved on.

If you encounter Phabricator now, treat it as legacy software with a clear succession story. Existing installations still function, and its code-review model remains influential, but it receives no meaningful official updates. Teams running it face the usual choices for unmaintained software: keep operating a frozen version, migrate to the actively maintained fork Phorge, or move to a mainstream platform like GitHub, GitLab, or Azure DevOps. Which path fits depends on how much a team values Phabricator's particular workflow and self-hosted integration versus the security patches, ecosystem, and features of supported tools. The honest recommendation is not to adopt Phabricator fresh; if its approach appeals, Phorge offers the same design under active maintenance, and the mainstream platforms offer breadth and support.

The trap to avoid is describing or selecting Phabricator as if it were current. Documentation, tutorials, and habits from its heyday can make it look alive, but its discontinued status is the fact that governs any decision. For a marketer or manager reading this, the takeaway is simpler still: Phabricator is a software-engineering tool, not a marketing technology, and it is a discontinued one at that — relevant background if your engineers mention it, but never something to reach for as a live product. Knowing that it exists, what it did, why it was influential, and that Phorge is its living successor is the complete and honest picture. Anything more current-sounding overstates a project its own maintainers have already set down.

Phabricator's name plays on fabricator, a maker of things, with a mock-scientific Ph- prefix, casting the suite as a workshop where software is built.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where phabricator is a core concern: