Tower review

Tower is an installable desktop Git client for macOS and Windows, not a hosted Git service, library or server. It sits between a developer and Git repositories, adding visual controls for common operations and advanced workflows. The vendor lists drag-and-drop actions, single-line staging, interactive rebase, conflict resolution, submodules, Git LFS, Git-Flow, file history, blame and cherry-pick.

The client also includes pull requests and a Services Manager for cloud code hosting, plus workflows such as automatic stashing and fetching. Tower Pro features include stacked branches, custom workflows, branch cleanup, merge detection and support for self-hosted repositories. That last feature means connecting a repository hosted on your own server; it does not make Tower itself a self-hosted server. For developers who work locally with Git and want a visual interface around repository operations, Tower is a desktop productivity layer in the version-control stack.

Tower is a desktop application operated through its visual interface, rather than an API-first service or a command-line tool. Its listed integration surface includes pull requests and a Services Manager for cloud code hosting, along with the ability to connect self-hosted repositories. The homepage also lists integrations generally, but names no particular providers in the published feature text.

The product uses Git workflows such as interactive rebase, staging, cherry-pick, submodules and worktrees. The vendor links to documentation, but does not publish SDK or programming-language names in the published product details. Developers planning to automate Tower or connect a specific hosting provider should confirm that path in Tower's documentation before making it part of a build or release pipeline. Avoid assuming a REST API, webhooks, plugins or a supported CLI; those are different integration surfaces from the desktop controls described by the vendor.

Tower has no free plan. The vendor offers a 30-day Pro trial without limitations, then lists annual-billing equivalents of $5.75 per user per month for Basic, $10.75 for Pro and $12.42 for Enterprise. Monthly billing prices are not listed. Basic includes one user, macOS and Windows versions, unlimited app updates, and pull requests and Services Manager for cloud code hosting.

Pro adds exclusive features, basic team management, dedicated billing and admin roles, and consolidated billing. Pro plans receive a 10% discount at 10 or more seats; additional users can be added through the customer portal. Enterprise adds advanced team management, invoicing and wire transfer, priority support, and SAML-based SSO. The bill scales by user count, not API calls, compute or repository activity. The pricing page lists no usage-based overages. Teams should confirm the billing term and seat costs before budgeting, especially if they need Enterprise-only controls.

Tower is not presented as an open-source client, and the vendor does not publish a source-code license in its product details. Tower itself is a desktop application; the vendor does not describe a self-hosted Tower server. Its self-hosted repositories feature is for connecting Tower to repositories on your own server.

The work is based on Git repositories, so repository history remains in Git rather than being held only inside a Tower-hosted service. Developers can continue using Git tooling if they stop using the client. That limits lock-in for repository data, but does not establish how Tower-specific preferences, workflows or account settings can be exported. Teams that depend on custom Tower configurations should ask the vendor about portability and account-data export before standardizing on them.

Tower is a developer desktop client, so production use depends on developers having it installed and compatible with their macOS or Windows environment. The vendor lists versions for both operating systems, but the published product details do not publish service-level commitments, availability targets, API rate limits or scaling limits. Those are relevant questions if a team expects to make the client part of a required workflow.

For security and administration, Enterprise includes SAML-based SSO, advanced team management and priority support; Pro includes basic team management and dedicated billing and admin roles. The pricing page does not list separate usage charges or overages. Before rolling Tower out broadly, confirm how the plan handles seats, account provisioning, repository-host compatibility and support response expectations. Also verify whether the team can meet its access-control requirements on the plan it intends to buy.