Plenty of code never goes near a public GitHub repo. It's the private side project, the dotfiles, the home automation scripts, or the whole lot sitting in a Gitea instance on a box under the desk. Most git clients handle that badly. Private repos sit behind a paid tier, and a self-hosted server gets treated as an edge case, or a feature for the enterprise plan.
Git Revenge is a free desktop client that doesn't care where your repos live. This post covers why that is, and how to get a private server set up for it if you don't have one yet.
Why the host doesn't matter
Most clients are built around a hosting provider's API. Sign in to GitHub or GitLab, and the client lists your repos, opens pull requests and pulls in avatars. That's handy when you're on one of the big hosts. When you aren't, those features go missing, and sometimes the client gets confused about what it's looking at.
Git Revenge never talks to a host's API. Every fetch, pull, push and clone runs the git installed on your machine, with your credential helpers and your SSH agent. If git push works in a terminal, it works in the app.
So all of these behave the same:
- GitHub or GitLab, public or private
- Codeberg, or your own Forgejo or Gitea
- GitLab self-managed
- a bare repo on a Raspberry Pi or NAS, over SSH
- a folder on a USB drive
Private repos cost nothing extra, because the app doesn't know which ones are private. It just runs git.
No server yet? You need less than you think
If you've got a machine you can SSH into, you've got a git server. A bare repository is all it takes:
ssh me@nas.local 'git init --bare ~/repos/robot.git'
git remote add home me@nas.local:repos/robot.git
git push -u home main
That's a private remote with no web UI, no accounts and nothing to update. For a solo project it might be enough.
If you want issues, a web view and LFS, Forgejo and Gitea run as a single binary or container on modest hardware. GitLab self-managed does far more and needs a lot more memory to do it.
You can also keep two remotes, which works well for something you want to back up off-site:
git remote add codeberg git@codeberg.org:me/robot.git
git push codeberg main
Things that trip people up on their own servers
A self-signed certificate
A home Gitea behind HTTPS with your own certificate makes git refuse to talk to it. Don't fix that with http.sslVerify false. Tell git to trust your certificate for that one host:
git config --global http.https://git.home.arpa/.sslCAInfo ~/certs/home-ca.pem
Git Revenge reads the same config, so once that works in a terminal, it works in the app. If you'd rather not edit config by hand, the app's Git Config tab shows the setting and where it came from.
SSH host keys
The first time you connect to a server your machine hasn't seen before, git wants you to confirm its host key. In a terminal that's a yes/no prompt. In Git Revenge you get a dialog with the fingerprint, and it asks before accepting.
Passphrases
If your SSH key has a passphrase and no agent is holding it, the app asks for it in a dialog. It doesn't store what you type. Saving credentials is your credential helper's job, or your agent's.
What the app gives you on top
The graph handles more than one remote. A branch that's on both home and codeberg gets one label with a count beside it, so you can see at a glance whether your backup is behind. Ctrl+Shift+F fetches every remote at once. Manage remotes… adds and edits them without a trip to the terminal.
Issue links work with any server. Add a Numbered (#123) link in Settings, point it at https://git.home.arpa/me/robot/issues/{1}, and #42 in a commit message becomes a link to your own issue tracker. The app builds the address and never contacts the server.
Insights work offline. Commit activity, open branches and what shipped between two tags are all computed from the repository, so they don't depend on your host having an API the app understands.
LFS works with whatever LFS server git-lfs talks to, including Gitea and Forgejo. The sidebar shows which patterns are tracked and which files are only placeholders, and you can lock a file before you edit it.
The rest is what you'd expect from a client. You can stage single lines, and dragging one branch onto another merges or rebases it after showing which files will conflict.
What it costs, compared
These are list prices for one person on a private project, as of this month. They change, so check before you buy.
| Client | Private repos | Notes |
|---|---|---|
| GitKraken Desktop | Paid plan | Free for public and local repos |
| Tower | From $69 per year | |
| Fork | $59.99 once | Works with any remote |
| GitHub Desktop | Free | Pushes anywhere, but sign-in and PRs are GitHub only |
| Git Revenge | Free | Apache-2.0, no account |
Fork is a good deal if you're happy to pay once. It's a mature app with a company behind it, and it doesn't care about your host either.
What it doesn't do
It doesn't do pull requests, on any host. Reviews stay in your forge's web UI. That's deliberate, and it's also part of why it works the same everywhere.
It doesn't create repos on a server for you. Make the repo on the server or in the forge's UI, then clone or add it as a remote.
It doesn't include git. You need 2.40 or newer. On Linux, installing from the project's apt or dnf repository brings git in for you. On Windows and macOS you install git first.
The Windows installer is signed, but SmartScreen might warn you anyway. Click More info, then Run anyway. The macOS build is signed and notarized.
It's a young project with one maintainer, and releases come often.
Getting it
Installers are on the releases page, and there's a Homebrew tap, winget, and signed apt and dnf repositories. The install guide has the commands.
The app makes one network request on its own, an update check against GitHub Releases, and you can turn it off. For anyone who self-hosts to keep their code on their own hardware, that probably matters.
If you run something odd, like a forge I haven't heard of or a remote over a protocol nobody uses anymore, I'd like to know whether it works. Open an issue letting me know.






