Cross-provider replication
Mirror repositories between GitHub, GitLab, Bitbucket, and self-hosted Git servers — in any direction.
Real-time Git backup & mirroring
Replicate and backup your git repositories in real time in one click.
Real-time sync
Bidirectional mirroring
Encrypted archives
Free for private & open source
Repository protection without compromise
Connect your accounts, define a binding, and Git Replica handles the rest — replication, archiving, and recovery all in one place.
Encrypted archive backups
Store AES-256-GCM encrypted archives in S3, Azure Blob, Google Drive, or OneDrive — fully under your control.
Self-hosted Git support
Replicate from or to any Git-compatible server reachable over HTTPS or SSH, including private GitLab instances.
Bidirectional sync
Keep two repositories in sync both ways. Any commit on either end is mirrored to the other in real time.
Manual backup vs. Git Replica
See how Git Replica compares to running your own backup scripts or relying on provider exports.
| Feature | Manual backup | Git Replica |
|---|---|---|
| Runs automatically | — | ✓ |
| Real-time | — | ✓ |
| Cross-provider | — | ✓ |
| Encrypted archives | — | ✓ |
| Handles branches & tags | — | ✓ |
| Restore process | Manual, hours of work | Single git push |
| Scales with team | — | ✓ |
| Cost of engineer time | High — ongoing maintenance | Zero |
Built for teams with security requirements
Git Replica is designed to handle credentials and code with minimal exposure and strong encryption throughout.
OAuth-only auth
No passwords stored. Login via GitHub, GitLab, or Bitbucket OAuth. JWTs are HTTP-only cookies.
AES-256-GCM token encryption
All OAuth tokens are encrypted at rest using AES-256-GCM before writing to the database.
No permanent code storage
Repositories are cloned into isolated temporary directories and deleted immediately after each sync job completes.
Signed webhook verification
All incoming webhook payloads are verified against provider-issued HMAC signatures before processing.
Simple plans for every team size
Free for personal and open source use. Predictable per-repo pricing for commercial teams. No per-seat tax.
Free
$0
/forever
For private non-commercial projects and open source contributors.
- Unlimited open source repos
- Unlimited private non-commercial repos
- Real-time replication
- Cross-provider mirroring
- Bidirectional sync
- Community support
Most popular
Team
$49
/month base
For startups and small teams running commercial projects.
- Includes 10 repositories
- 1 GB cloud archive storage
- +$5 per additional repo
- +$5 per additional 1 GB archive
- Encrypted archive backups
- Priority email support
- Commercial use license
Enterprise
From $299
/month
For growing organizations with compliance needs.
- 100 repositories included
- 100 GB archive storage
- SSO / SAML
- Role-based access control
- Audit logs
- SLA & priority support
- Advanced retention controls
Self-Hosted
From $499
/month
Deploy on your own infrastructure for maximum control.
- Runs on customer infrastructure
- 250 repositories
- Unlimited internal users
- SSO / SAML / LDAP / OIDC
- Audit logs
- Private networking
- Assisted onboarding
Common questions
Everything you need to know before getting started.
How does real-time Git repository backup work?
Git Replica uses webhooks to receive push events from your provider the moment a commit lands. It immediately queues a mirror job that runs a git clone --mirror and pushes to your destination — whether that's another provider or an encrypted archive. The round-trip typically completes in seconds.
Can I back up from GitHub to GitLab (or the other way around)?
Yes. Git Replica supports cross-provider bindings between GitHub, GitLab, and Bitbucket in any direction. You can also mirror from a self-hosted Git server. Multiple source-destination pairs can be configured per repository.
Is Git Replica really free for open source projects?
Yes — unlimited repositories for open source and private non-commercial use are covered by the Free plan with no time limit. You only move to a paid plan if you use Git Replica in a commercial context.
Where are encrypted Git archives stored?
Archives can be stored in Amazon S3, Azure Blob Storage, Google Drive, or OneDrive. Repositories are archived with AES-256-GCM encryption before leaving our infrastructure. You control the destination and retain the encryption keys.
Do you support self-hosted Git servers?
Yes. Git Replica can mirror from and to self-hosted GitLab instances and any Git-compatible server reachable over HTTPS or SSH. Self-hosted destinations are included from the Team plan upward.
What happens if I restore from a backup?
Restoration is a git push — we decrypt the archive and push the full ref set (branches, tags, notes) to any Git remote you specify. No proprietary format to decode. You can restore to any provider in minutes.
Stop relying on a single Git host.
Set up real-time replication in under two minutes. Free for open source and private non-commercial use — no credit card required.
Get started free