Phabricator vs Bugsnag

Phabricator is completely free and open source. It's source code is hosted on GitHub.

Phabricator is quickly improving, with bug fixes and new features added often. There is an update to the changelog every couple of weeks.

Support for Git, SVN and Mercurial is available.

Includes a bug tracker out of the box. Allows for managing bugs, creating issues, commenting on them and closing them.

Instead of having to have separate Q&A tool, there's Ponder which takes out the hassle.

Users can subscribe to files or even repositories and notifications will be sent when code you are subscribed to is changed.

You can track not only code bud also design mockups.

You can create voting in an instant and need not to rely on external tools.

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.

With using Spaces and Project and custom policies you can have any combination of access to any object inside of your own Phabricator instance.

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.

You can configure your workspace to deal with tasks, bugs, todo's, etc.

Clear, concise documentation. Plus docs on cross-domain script errors and enabling CORS.

Bugsnag can be set up to send email notifications as soon as exceptions occur. It can also integrate with a number of third-party services that can be used for notifications including Campfire, HipChat, Twilio SMS and custom solutions via Webhook.

Bugsnag integrates with a wide variety of 3rd party tools to automatically create issues or tickets. Integrations include GitHub, BitBucket, UserVoice, Trello and many, many others.

After a two-week full-featured free trial period the user is limited to 2,000 errors/month, 1 user and 1 project.

Bugsnag groups similar exceptions together displaying the number of occurences so that there's no need to deal with each instance of the error separately.

Their documentation was well organized, easy to search through for the platform of choice and quick work of full product integration.

Drop in place integration with Unity 3D, only a simple API Token configuration on game object and everything was up & running with almost zero code written.

Not many products have decided to finally start doing this, phabricator now has a champion.