Mercurial vs Unity
Mercurial
mercurial-scm.orgUnity
unity.comSide by side
| Figure | Mercurial | Unity |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 8 |
| Spec score · Version Control Software | 7.7 (#35) | 8.7 (#5) |
| Spec score · Source Code Management | 7.7 (#20) | 8.7 (#7) |
| Spec score · Game Version Control Software | 7.7 (#23) | 8.7 (#7) |
| Integrations | Official extensions include Bugzilla hooks, Git command mapping, Git fast-export, email notifications and external diff tools. | Unity Integrations connect Cloud Build, Cloud Diagnostics and Collaborate with webhooks, Discord, Slack and email. |
Plans
Unity
- Free tierFree
- Pay-as-you-goPrice not published
- Pay-as-you-goPriced on request
- Unity PersonalFree
- Unity Pro$210 a month
- Unity Pro$2,310 a year
- Unity EnterprisePriced on request
- Unity IndustryPriced on request
In their own words
Mercurial
Mercurial is a free, distributed source control system for managing development history. Each developer keeps a full local copy of that history, so work can continue without a network connection or central server. It is designed for projects of any size and supports diffs, commits, branching, and merging. The software runs on Windows, macOS, and Linux; binary releases are also listed for Solaris 11 Express and other platforms. Installation options include system packages, Windows winget, Homebrew, PyPI tools, and source builds. Python extensions can add or change commands and access core functionality. Official extensions cover tasks such as Git command mapping, email notifications, and external diff tools. Mercurial supports sparse checkout and nested repositories; large-file handling is available through an extension. It is licensed under the GNU GPL version 2 or later. One security caveat: carefully constructed Git subrepositories can pose a clone-time code-execution risk, so they are disabled by default.