Is Tower's undo unreliable?

No. Tower's undo works and people rely on it. The difference is what it can reach: an undo that runs after the fact reverses what the client captured, or what Git's own safety nets happen to still hold. GitAegis captures more, earlier, and refuses to proceed when it cannot.

Can I run both on the same repositories?

Yes. Both execute your installed Git against a standard repository, and nothing GitAegis does changes the on-disk format. Capsules live in the GitAegis application support directory and in refs/aegis/.

Does GitAegis need an account the way Tower does?

No. An account is optional and never gates local Git work. Sign in only when you want the account features available to you.

Is GitAegis cheaper than Tower?

The GitAegis macOS edition is free and requires no account. Tower's published figures are in the table above, per user per year, excluding tax.

Does GitAegis run on Windows or Linux?

No. GitAegis ships for macOS 12 or later, on Apple Silicon and Intel. Tower ships for macOS and Windows and has no Linux build, so Tower covers a platform GitAegis does not.

What does GitAegis require to run?

Git 2.38.0 or newer, already installed. GitAegis never bundles or downloads Git. On macOS 12, Apple's Command Line Tools ship Git 2.37.1, which is below the floor, so install Git with Homebrew first.

Comparison · Verified 9 August 2026 · Sources at the foot of the page

Tower undoes it afterwards. GitAegis refuses to start without a way back.

Of every client in this category, Tower’s undo is the one worth taking seriously. It is genuinely good, it is why a lot of professionals pay for Tower, and “undo almost anything” is not an empty claim. The difference is structural rather than a matter of degree: GitAegis writes a six-domain recovery capsule before the command runs, and blocks the operation if that capsule can’t be written.

Download GitAegis See how recovery works

Tower facts verified 9 August 2026 against git-tower.com · GitAegis ships for macOS · Corrections to press@gitaegis.com

Tower

Operation
Something goes wrong
Undo

Reverses from here, backwards: Undo

The way back is assembled afterwards, out of what the client happened to capture.

GitAegis

Plan
Capsule written
Precondition check
Operation
Journal

Rollback restores from here, before anything ran: Capsule written

If step 2 fails, steps 3 to 5 never happen.

The same failure, on two timelines. The difference is where the arrow back starts.

Start by being fair to Tower

Tower has been shipping since 2010 and is the client a lot of senior engineers reach for. What it does well is not marketing: its conflict handling is the best in this category, its coverage is thorough, and its undo reverses a large set of actions taken inside Tower, including restoring local changes you discarded, which is the single most common way developers destroy their own work.

Published pricing, from git-tower.com on 9 August 2026: Basic $69/year, Pro $129/year, Enterprise $149/year, per user, tax excluded. A 30-day trial, and free licences for students. macOS and Windows; no Linux build.

If Tower’s undo covers the situations you actually get into, buy Tower. This page is for readers whose answer to that is “it doesn’t.”

Where Tower is the better choice

Conflict resolution is the strongest in this category. If you resolve conflicts often, that alone is a legitimate reason to buy it.
Coverage is thorough: interactive rebase, single-line staging, file history, submodules, LFS, SSH key handling and multiple accounts.
Its undo reverses a large set of actions taken inside Tower, and restores local changes you discarded: the single most common way developers destroy their own work.
Service integrations across GitHub, GitLab, Bitbucket and Azure DevOps, including self-hosted instances. GitAegis has none of these in the client.
Native on both macOS and Windows, with unusually good documentation, responsive support, a 30-day trial, and free licences for students.
It has been shipping since 2010. That counts, and it should count in your decision.

Where the two products diverge

Five axes. Only the first two are the argument; the rest follow from them.

When the safety net is created.
Tower’s undo operates after the fact: the action happens, then Tower reverses it. The GitAegis capsule is written to disk before the first git command in the operation executes. Nothing about the operation begins until the way back exists.
What happens when the safety net can't be created.
This is the part with no equivalent. If GitAegis cannot write the capsule (disk pressure, permissions, a repository state it can’t snapshot) the operation is blocked. You get the reason and the domain that failed, and no control in the interface waives it.
How much is captured.
Six domains: refs, index, staged changes, working changes, untracked files and operation state. Untracked files are the one that catches people out. A scratch fixture that was never git added is in no reflog anywhere. Restore runs per domain: refs only, working tree only, untracked files only, or all of it.
Whether the record covers what the client didn't do.
Tower records what Tower did. The GitAegis Flight Recorder runs a filesystem watcher, so a branch you moved in your terminal, a checkout your editor’s extension performed and an index change a build script caused land on the same timeline as GitAegis’s own operations. It is a pointer-level record (refs, HEAD, index, stashes, worktree registrations) not a log of every file you edited.
What the tool will never run.
GitAegis does not implement git gc, git prune or git reflog expire. Not behind a confirmation, not behind an advanced setting. Those are the operations that turn recoverable work into unrecoverable work, and a recovery layer is only as good as the objects still on disk.

Side by side

Including the five rows Tower wins outright, and the two where both products read the same dash.

GitAegis and Tower compared across recovery behaviour, everyday Git capability, platform support, integrations and licensing.
Capability	GitAegis	Tower
Snapshot captured before the operation	Full support	Not offered
Operation refused if the snapshot cannot be taken	Full support	Not offered
Undo of the client's own actions, after the fact	Full support	Full support
Discarded local changes recoverable	Full support	Full support
Untracked files included in the safety net	Full support	Not offered
In-progress operation state captured¹	Partial or limited support	Not offered
Restore by domain (refs, index, staged, working, untracked)	Full support	Not offered
Timeline of ref and index changes made outside the client²	Full support	Not offered
Unreachable or dangling commit discovery across the reflog, stashes, recovery refs, capsule bundles, sibling worktrees and a bounded fsck	Full support	Partial or limited support
Repository damage scan with evidence and proposed repairs	Full support	Not offered
Mutating controls lock when the index or HEAD is damaged	Full support	Not offered
Stated commitment never to run git gc, git prune or git reflog expire³	Full support	Not offered
Exact commands shown before execution	Full support	Partial or limited support
Conflict resolution⁴	Full support	Full support
Interactive rebase⁴	Partial or limited support	Full support
bisect in the interface	Full support	Not offered
GitHub and GitLab in the client, including self-hosted⁵	Not offered	Full support
Bitbucket and Azure DevOps in the client	Not offered	Full support
Native application	Full support	Full support
macOS	Full support	Full support
Windows⁶	Not offered	Full support
Linux	Not offered	Not offered
Signed org policy, audit trail, SSO and SCIM⁷	Not offered	Not offered
Free for students	Not offered	Full support
Free edition, no account	Full support	Not offered
Pricing model	Free, no account	Subscription: $69 / $129 / $149 per user per year

Full supportPartial or limited supportNot offered

¹ GitAegis captures the merge, cherry-pick and revert markers and puts them back on restore. A rebase in progress is recorded as present rather than captured, and it is not replayed. You drive the sequencer yourself.

² The Flight Recorder records ref, HEAD, index, stash and worktree-registration changes made by your terminal, your editor or a build script. It does not turn edits to file contents into timeline events.

³ A dash means Tower publishes no commitment either way, not that Tower runs those commands.

⁴ GitAegis performs rebase, cherry-pick, revert and reset through the operation model with the full conflict sequencer: continue, skip and abort. Tower's interactive rebase editor and conflict wizard are more developed, which is why those rows read the way they do.

⁵ GitAegis does not connect to a hosting provider from the client today: no pull requests, no reviews, no CI status. Tower does, across GitHub, GitLab, Bitbucket and Azure DevOps.

⁶ GitAegis ships for macOS. There is no Windows or Linux build to download.

⁷ Neither product offers org policy, an audit trail, SSO or SCIM in the shipped desktop client today.

Tower rows and prices are published figures in USD, excluding tax, read on 9 August 2026: Tower pricing and platform support · GitKraken vs Fork vs Tower, 2026.

The scenario that separates them

One repository state, resolved twice.

You are three days into a branch. Two files are staged. One file is modified but unstaged. There is an untracked fixtures/large-payload.json you generated this morning. And you are midway through an interactive rebase that hit a conflict. Then you run the wrong operation.

With an after-the-fact undo

The question is what the client recorded before you acted. Refs are usually recoverable, because Git’s own reflog is doing that work. The staged hunks, the untracked fixture and the sequencer state are a different matter. Those are not in the reflog, and no client can reverse what it never captured.

With GitAegis

All six domains were written to disk before the first command ran. You restore the index and the untracked files without touching your refs, or restore everything, or restore nothing and read the journal entry to work out what actually happened.

And the honest limit, in the same breath: the capsule does not resume your rebase. It records that an operation was in progress and restores your refs, index, working changes and untracked files. The sequencer you drive yourself.

The claim GitAegis will not make

“Undo almost anything” is a fair marketing sentence, and Tower is careful to include the word “almost”. The GitAegis version is longer and less quotable, because it is the whole promise.

What GitAegis can put back

If a recovery capsule was taken, you can roll the operation back.
If a Flight Recorder event captured a state hash, you can roll back to that state.
If any reflog entry, ref, branch, stash, or capsule references a commit, Lost Work can recover it.
Outside those, it cannot, and GitAegis says so instead of pretending otherwise.

Known limits, stated with the claim rather than in a footnote

Rebase state is not restored from a capsule.
Config is captured as evidence rather than restored.
.gitattributes content filters cannot be wholesale disabled.
bisect and a conflicted stash apply have no generic resume.
The Flight Recorder records pointer-level truth. Edits to file contents show up in status, not as timeline events.

What Lost Work can still find →

When Tower is the right purchase

Buy Tower rather than GitAegis if

Conflict resolution is the part of your day that hurts most.
You want the deepest interactive rebase interface available.
You need GitHub, GitLab, Bitbucket or Azure DevOps inside the client.
You work on Windows. There is no GitAegis build for it.
You are a student, and free matters more than the recovery layer.
Your recovery needs are met by reversing an action shortly after you took it, and you do not need untracked files, index state or operation state in the net.

Buy GitAegis rather than Tower if

You have lost work the reflog could not get back.
You need the safety net to exist before the operation, and the operation refused without it.
You need a record of what happened to a repository, including ref and index changes the client did not cause.
You want a client that will never run git gc, git prune or git reflog expire.
You are on macOS and want the recovery layer at no cost and with no account.

Both, if you like Tower’s conflict wizard and want GitAegis’s recovery layer. They execute the same Git against the same repositories and neither changes the on-disk format.

Questions people ask about this comparison

Sources

Tower pricing and platform support, read 9 August 2026
GitKraken vs Fork vs Tower, 2026, read 9 August 2026

Tower facts verified 9 August 2026. Prices are the vendors’ published figures in USD and exclude tax. If something here is out of date or wrong, send the correction to press@gitaegis.com and it will be applied and re-dated.

Free edition · No account required

A recovery capsule before every risky Git operation.

You see the exact commands before they run, and the operation is refused if the capsule cannot be written.

Download GitAegis See how recovery works →

Requires Git 2.38.0 or newer, already installed.

Every risky operation, in this order

Previewthe exact commands, shown before anything runs
Capsulerefs, index, staged and working changes, untracked files, operation state: written to disk first
Executethe commands as shown, or not at all
Journalplan, commands, capsule id, outcome

No capsule, no operation. Restore plans, previews, and takes its own capsule.