Your code is
always available
Resentry mirrors your GitHub repositories to our servers and watches the integrity of your code. Catch silent code corruption before it does damage.
On April 23, 2026 GitHub's merge queue silently corrupted 292 pull requests The UI showed +29 / −34 lines — what landed on
mainwas +245 / −1,137. Status was green. CI passed.
Resentry would have caught it in seconds.
Set up in 3 steps
Setup in under 60 seconds. No server, no cron-job to maintain.
Connect
Sign in with GitHub, pick repos. Resentry registers the webhooks & tokens for you — no copy-paste.
Mirror
Full <code class="text-gray-200">git clone --mirror</code> onto our disk. Pulled fresh on every push, cloneable via Git Smart HTTP.
Secure
Diff comparison between PR data and the actual mirror. Force-push, mass-deletion, history-rewrite — instantly alerted, with a recovery URL to the last clean state.
Git Mirror
Full bare clones of your repositories with Git Smart HTTP access. Your backup is reachable any time.
Integrity check
Detects force-pushes, mass deletions, and divergence between PR data and actual commits.
Real-time alerts
Email notifications for critical integrity issues and GitHub outages. Always informed.
Simple pricing
Free
- ✓ 3 public repositories
- ✓ 15-min sync interval
- ✓ Basic integrity check
- ✓ Git Smart HTTP access
- ✗ Private repositories
- ✗ Webhook sync
Pro
- ✓ Unlimited repositories
- ✓ 5-min sync + webhooks
- ✓ Private repositories
- ✓ PR diff comparison & alerts
- ✓ 30-day snapshots
- ✓ Email notifications
Team
- ✓ Everything in Pro
- ✓ 5 team members
- ✓ 90-day snapshots
- ✓ Priority support
- ✓ Audit log
- ✓ SLA guarantee
Frequently asked questions
What does Resentry actually do?
Resentry is a GitHub backup and integrity service. Every repository you connect is mirrored as a full bare clone on our servers and re-synced on every push (Pro) or every 15 minutes (Free). After each sync we run integrity checks: force-push detection, history-rewrite detection, mass-deletion detection, and — for Pro — a diff comparison between the GitHub PR data and what actually landed on the branch.
How is this different from a normal GitHub backup tool?
Backup tools copy bytes. Resentry copies bytes AND verifies the result. The April 23, 2026 GitHub merge-queue incident corrupted 292 PRs silently — pure backup tools mirrored the broken state and called it a day. Resentry compares each merged PR's GitHub-API diff against what landed on the mirror; mismatches > 3× become critical alerts with a recovery URL pointing at the last clean snapshot.
What happens during a GitHub outage?
All your mirrors stay reachable. You can clone or pull from your Resentry mirror over HTTPS using your GitHub username plus a Resentry API token: git clone https://<host>/m/<user>/<owner>/<repo>.git. Pro users also get an email when GitHub goes down so you don't waste time poking at deploys before realizing it's not your fault.
How does the integrity check actually find corruption?
Three layers. (1) Before each fetch we save the current HEAD-SHA as a snapshot. (2) After each fetch we run git merge-base --is-ancestor to detect force-push, count commits to detect history-rewrite, and run git diff --diff-filter=D to find mass deletions. (3) For Pro, we fetch the merged PR's expected additions/deletions/changed-files via the GitHub API and compare against the actual diff in the mirror. Anything > 3× ratio or files deleted outside the PR scope triggers a critical alert.
Are private repositories supported?
Yes, on the Pro plan. We use OAuth tokens with the standard repo scope, encrypt them with AES-256-GCM at rest, and pass them to git via in-memory headers — never persisted to the on-disk repo config.
How much does it cost?
Free for up to 3 public repositories with basic integrity checks. Pro is €10/month for unlimited repositories, private repos, real-time webhook sync, full PR-diff integrity, 30-day snapshots, and email alerts. Team is €25/month with org-wide mirroring, multi-user accounts, and Slack integration (coming soon).
Where is the data stored?
Bare git repositories live on a Persistent Disk on Render (currently EU). Daily SQLite backups are uploaded to Cloudflare R2. We do not share, sell, or train on your code.
What's the recovery flow when a critical alert fires?
The alert email and the dashboard show the last clean snapshot's commit SHA. Run the provided git clone command against your Resentry mirror, git checkout that SHA, and you have the canonical pre-incident state. From there you can compare against GitHub, restore deleted files, or roll the branch back.