Never loose your work.
Automatic GitHub backups to keep your work, code and repositories safe on autopilot.
Open core
Review the backup path before trusting the hosted service.
Git native
Mirror clones and portable bundles, not proprietary exports.
Hosted operations
Schedules, storage, retention, alerts, and restores managed for you.
acme/api
Latest verified artifact
- Refs
- 184
- Size
- 2.4 GB
- Age
- 18m
# mirror every ref
git clone --mirror repo_url repo.git
# create a portable artifact
git -C repo.git bundle create repo.bundle --all
# verify before storage
git bundle verify repo.bundleHow backups are created
Plain Git artifacts, created by code you can read.
The backup engine is deliberately simple: scoped GitHub App access, standard Git commands, verification, then storage.
Install the GitHub App
Grant scoped access to only the repositories you choose.
Create Git-native artifacts
GitRescue mirrors refs and creates portable bundles your team can inspect.
Verify and store
Backups are checked before durable hosted storage and retention policies take over.
Open core
Trust the hosted service because the backup path is visible.
Review the commands, run the worker yourself when policy requires it, or use hosted GitRescue when you want us to operate storage and schedules.
Inspectable by default
The important work happens in Git-native steps your team already understands.
Self-hostable when needed
Run the core backup worker directly for environments that require direct control.
Hosted when operations matter
Let GitRescue manage durable storage, retention, monitoring, and restore workflows.
Hosted GitRescue
Pay us to run the boring parts.
Self-hosting should be possible. Hosted should be easier. GitRescue keeps that tradeoff clear without hiding the mechanics.
Scheduled snapshots
Automatic backup runs keep selected repositories protected without manual jobs.
Failure alerts
Operational status stays visible when credentials, repositories, or runs need attention.
Restore readiness
Recent artifacts and restore actions stay close together for incident response.
Restore confidence
A backup is only real if restore is obvious.
GitRescue centers the artifact and the verification path so teams can reason about recovery before an emergency.
Inspect the artifact
Bundles stay close to the Git model your team already understands.
Verify the backup
Run Git verification before storage and keep a clear status trail for each run.
Restore without lock-in
Use standard Git tooling to clone from a bundle or rebuild a mirrored repository.
Questions
Clear answers for skeptical engineers.
Why use Git bundles instead of a proprietary backup format?
Bundles are native Git artifacts. You can verify and clone from them with Git even if GitRescue is not in the loop.
Can we self-host the backup worker?
Yes. The core connect, fetch, and backup logic is open source so teams can run it themselves when direct control matters.
Why pay for hosted GitRescue?
Operations. We manage schedules, encrypted storage, retention, monitoring, and restore workflows so your team does not maintain another backup system.
Start with trust
Back up your GitHub repos with artifacts you can understand.
Run it yourself, or use hosted GitRescue and let us manage the operational load.