Gitbacker is the self-hosted backup daemon for GitHub, GitLab, Bitbucket and anything that speaks git. Scheduled, GPG-encrypted, deduplicated, restorable with a diff preview. Deploy it in 30 seconds and sleep through the next platform outage.
curl -fsSL gitbacker.com/install.sh | bash
Twelve features in the box today. No “coming soon” asterisks. No SaaS lock-in. Read the source if you’re the trust-but-verify type.
Cron per repo or a global default. The scheduler runs in its own worker. Set once, forget for years.
AES-256 symmetric on every archive. Keys rotated from the UI. Your disks never see plaintext.
Review every file, branch, and tag that will change before any push. Never force-push on faith.
Per-host PATs and SSH keys, matched by hostname. GitHub, GitLab, Bitbucket, Gitea, you name it.
Failure, verification error, low disk — one channel, one click. Webhook-compatible with any destination.
Admins and operators, scoped per repo. Operators see what they own. No IAM language required.
Your disk, your network, your encryption keys. No cloud bill. No egress fees. No vendor roadmap.
GitHub-style green year. One glance tells you if everything is fine. Red dots start Monday meetings.
Download any archive, encrypted or decrypted on the fly. Your data, yours to move, whenever.
If nothing changed, no archive is written. Saves disk, saves time, needs no configuration.
Select 400 repos, hit one button. Filter, sort, search across everything. Built for real scale.
Credentials and keys sit in the database encrypted with Fernet (AES-128). Plaintext lives nowhere.
No agents in your repos. No SSH into your boxes. Gitbacker clones URLs and writes archives to disks you own. That’s the whole threat model.
Run the one-liner on any host with Docker. Images pulled, secrets generated, admin seeded, scheduler live.
Paste URLs in the UI, pick a schedule and a destination — or take the defaults. Connect a PAT once per host and Gitbacker handles the rest.
The scheduler keeps running. Unchanged repos skip. Failures ping Slack. Restore any snapshot with a full diff preview before a single ref moves.
Six real ways teams lose source code. Each one happens dozens of times a quarter to companies that thought their git host was their backup. It isn't.
One command. No signup. Your infrastructure, your keys, your data. The next git outage is already scheduled — be ready for it.