Automatic, private, and free. Own your code history forever. Preserve issues, PRs, releases, and wiki in your own Gitea server.
Powerful features designed to keep your code safe and accessible, no matter what happens.
Set it and forget it. Automatically sync your GitHub repositories to Gitea on a schedule.
Mirror entire organizations or user accounts with a single configuration.
Maintain your GitHub organization structure or customize how repos are organized.
Monitor mirror progress with live updates and detailed activity logs.
Self-hosted solution keeps your code on your infrastructure with full control.
Free, transparent, and community-driven development. Contribute and customize.
Explore real-world workflows where automated mirroring removes risk, accelerates migrations, and keeps engineering teams shipping.
Continuously mirror GitHub repositories into self-hosted Gitea so your side projects stay safe even when GitHub hiccups.
Install the project on Kubernetes in a few commands using the maintained Helm chart to keep your backup mirror humming.
Run the one-liner Proxmox VE script to launch gitea-mirror inside a tuned LXC container for your lab backups.
A clean, intuitive interface designed for efficiency and ease of use
Monitor all your mirrored repositories in one place
Swipe left or right to navigate
Choose your preferred installation method
git clone https://github.com/RayLabsHQ/gitea-mirror.git && cd gitea-mirrordocker compose -f docker-compose.alt.yml up -d# Open http://localhost:4321 in your browserFirst user becomes admin. After installation, create your account and configure GitHub and Gitea connections through the web interface.
Everything you need to know about self-hosted repository backups with Gitea Mirror.
Gitea Mirror is a self-hosted tool that automatically backs up your GitHub repositories to your own Gitea server. You need it because GitHub outages, account issues, or policy changes can lock you out of your code. With Gitea Mirror, you own your backups completely—no monthly fees, no third-party storage, just full control over your repository history, issues, pull requests, and releases.
BackHub and Rewind are cloud services that cost $600-2400/year and store your code on their servers. Gitea Mirror is free, open source, and runs on your own infrastructure. You pay $0/month and have complete data ownership. The tradeoff: you manage the infrastructure yourself, while cloud services are fully managed.
Yes! Enable 'Mirror metadata' in settings to backup issues with comments, labels, and assignees. Pull requests are mirrored as enriched issues with full metadata, commit history, and file changes (Gitea's API doesn't support creating PRs from external sources). Releases, including binary assets, and wiki pages are also backed up when enabled.
15-20 minutes with Docker. Run 'docker compose -f docker-compose.alt.yml up -d', visit localhost:4321, create an account, paste your GitHub and Gitea tokens, select repos to backup—done. The Proxmox LXC one-liner is even faster. No complex configuration files or manual scripting required.
You can immediately clone from your Gitea server instead. Your local backups include full commit history, branches, tags, issues, releases—everything. Recovery time is typically under 2 minutes (just point git to your Gitea URL). This is why it's called disaster recovery, not just mirroring.
Configurable from every 15 minutes to once per day (or longer). Most users choose 1-8 hours based on how fresh they want backups. The scheduler auto-discovers new repos and respects per-repo intervals, unlike Gitea's built-in mirroring which defaults to 24 hours.
Yes! Gitea Mirror can automatically backup all your GitHub stars into a dedicated Gitea organization. Perfect for preserving important open source projects before they disappear (projects get deleted, renamed, or removed all the time).
Minimal: 2 vCPU, 2GB RAM, 5-10GB storage (grows with repo count). Runs on Docker, Kubernetes, Proxmox LXC, or bare metal. Works on AMD64 and ARM64 (Raspberry Pi compatible). A small homelab server or cheap VPS is plenty for personal use.
Yes. All GitHub and Gitea tokens are encrypted at rest using AES-256-GCM. Even if someone gains access to the SQLite database, they can't read your tokens without the encryption key. Use the ENCRYPTION_SECRET environment variable for additional security.
Absolutely. Just use a GitHub personal access token (classic) with 'repo' scope enabled. Gitea Mirror will backup all repositories you have access to—public, private, and internal.
Gitea Mirror supports multiple organizations with flexible destination strategies: preserve GitHub structure in Gitea, consolidate into a single org, or use mixed mode (personal repos in one place, org repos preserve structure). Edit individual organization destinations via the dashboard.
Yes! Enable 'Mirror LFS' in settings. Make sure your Gitea server has LFS enabled (LFS_START_SERVER = true) and Git v2.1.2+. Large assets like videos, datasets, and binaries are backed up alongside your code.
Simple: 'git clone https://your-gitea-server/owner/repo.git'. Your full history, branches, and tags are there. For issues/PRs/releases, they're already in Gitea's web interface. For complete disaster recovery, restore the data volume to a fresh Gitea Mirror instance—everything (config, sync history) is preserved.
Yes! Many users run Gitea Mirror for local/warm backups while using cloud services for offsite redundancy. Best of both worlds: instant local recovery and geographic disaster protection. Totally compatible.
No. Gitea Mirror is a community open source project—no 24/7 support, no compliance certifications, no guaranteed uptime. It's perfect for homelabs, indie developers, and small teams comfortable with self-hosting. If you need enterprise SLAs, consider commercial solutions like BackHub or GitHub Enterprise Backup.
Still have questions? Ask in our GitHub Discussions
Join developers who trust Gitea Mirror to keep their repositories safe and accessible. Free, open source, and ready to deploy.
Gitea Mirror is licensed under GPL-3.0.View License