Gitnuro vs Tower
Gitnuro
gitnuro.comTower
git-tower.comSide by side
| Figure | Gitnuro | Tower |
|---|---|---|
| Price from | Free | $5.75/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | — |
| Plans published | 2 | 6 |
| Spec score · Git GUI Clients | 8.5 (#5) | 7.6 (#23) |
| Spec score · Git clients | 8.4 (#5) | 8.3 (#7) |
| Free plan | Yes | No |
| Product | Gitnuro is a multiplatform Git client aimed at newbies and professionals. | Tower is a graphical Git client that makes advanced Git operations available through a visual interface. |
| Support | Users can report bugs or suggest features by opening an issue, and pull requests are welcome. | Tower lists friendly email support and documentation, while Enterprise includes priority support. |
Plans
Tower
- Basic$69 a year
- Pro$129 a year
- Enterprise$149 a year
- BasicPrice not published
- EnterprisePrice not published
- ProPrice not published
In their own words
Gitnuro
Gitnuro is a free, open-source Git client for Linux, macOS, and Windows, aimed at newcomers and experienced users. It supports cloning, committing, merging, rebasing, pushing and pulling, stashing, and managing branches and remotes. For reviewing changes, it offers text diffs, image comparisons, commit search, file history, blame, and staging or unstaging selected lines and hunks. Its listed capabilities also include Git LFS, submodules, and interactive rebase. The source code is licensed under GPL-3.0, and the maker says the app does not track users or their projects. Gitnuro uses the JVM and avoids web technologies, which the maker says helps it work with large repositories. Users can create themes and customize the colour palette. Downloads include Linux Flatpak and JAR builds, Windows installable and portable versions, and a macOS app bundle ZIP or Homebrew installation. Git Credential Manager is supported when its full binary path is specified in .gitconfig. The macOS version is currently unsigned; multicast DNS remote URLs and self-signed server certificates are identified as setups that can cause authentication failures.