Source code disaster recovery for GitHub is live
When the systems you depend on fail, your business keeps going.
hailm.io builds disaster recovery and resilience for the infrastructure an organization can't run without. We start with your source code: an independent, immutable copy of every repository, ready to restore on day zero.
- Every repository, full history, LFS and wikis
- Locked so nobody can delete it early
- Two AWS regions, per-customer encryption
Restore points
ProtectedIllustration of the dashboard
Today, 01:59 UTC
Incremental · 2 regions
Yesterday, 01:59 UTC
Incremental · 2 regions
6 days ago, 01:59 UTC
Full · 2 regions
Why it matters
Your Git provider is a single point of failure
Most companies keep every line of code in one place, under one set of credentials. If that place is gone, so is the business. Local clones are partial, and provider-side backups share the same blast radius.
Deleted organizations
A mistaken or malicious deletion can take repositories, history and settings with it.
Compromised accounts
A stolen admin token or session is enough to wipe or rewrite what you depend on.
Ransomware and extortion
Attackers increasingly target source code and the backups meant to protect it.
Provider outages and lockouts
Billing disputes, suspensions or long outages can cut you off from your own code.
Insider mistakes
Force-pushes and cleanup scripts destroy history that local clones rarely hold in full.
hailm.io keeps a copy that lives outside your provider, outside your accounts, and outside the reach of anyone who compromises them.
See howHow it works
Set up in minutes, protected every day
- 1
Connect read-only
Install our GitHub App or add a fine-grained token with read access to contents and metadata. We can never change your code.
- 2
Mirror daily
A fresh, isolated machine mirrors every repository with all branches, tags, LFS objects and wikis, and checks each one for integrity.
- 3
Lock in two regions
The copy is snapshotted, encrypted with a key only your workspace uses, locked in compliance mode and copied to a second AWS region.
- 4
Restore on day zero
Push everything to a new GitHub organization, or download an archive of bare mirrors, from any restore point.
Security model
A backup that survives the worst day
A disaster recovery copy is only useful if it is still there when everything else is compromised. Every design decision starts from that assumption.
Immutable by design
Restore points are compliance-locked for the retention period. Until they expire nobody can delete or shorten them: not you, not us, not an attacker with access to our cloud account.
Your own encryption keys
Every workspace gets dedicated encryption keys in each region. Keys are protected against deletion, and any attempt raises an alert.
Two regions
Each restore point is copied and locked in a second AWS region, so a regional outage does not stand between you and your code.
Least privilege everywhere
Read-only GitHub access, an isolated machine per backup with no inbound access, credentials that never touch disk, and a full audit log.
Restore
Two ways to get everything back
Push to a GitHub organization
Recreate every repository, with LFS objects, branches and tags, in an organization you choose. Write access exists only for the restore, through a separate app or a single-use token that is never stored.
Download an archive
An encrypted archive of every repository as a bare mirror, including LFS and wikis, behind a short-lived link. Works with any Git server, not just GitHub.
Restores require the workspace owner and a fresh identity check, and every step is recorded in the audit log.
Our mission
Resilience for the systems you can't run without
hailm.io exists to make sure an organization can recover when a critical system disappears, whether through attack, accident or a provider it depends on. Source code is where we start, because for a software company it is the business.
What we hold ourselves to
- Recovery that does not depend on the system that failed.
- Copies nobody can quietly delete, including us.
- Restores you can rely on without heroics at the worst moment.
Protection for more of your critical infrastructure is on the roadmap.
FAQ
Questions teams ask us
What exactly is backed up?+
Every repository you select, as a full mirror: all branches, tags and history, Git LFS objects, and wikis. New repositories are included automatically unless you exclude them.
How often, and for how long?+
Once a day at a time you choose. Each restore point is locked for 7 days in two AWS regions. A full copy from a blank disk is taken every 7 days, and the days in between fetch only what changed.
Can hailm.io change or read my code?+
Backups use read-only access to repository contents and metadata, so we cannot change anything in GitHub. Your data is encrypted with keys dedicated to your workspace and is only read when you ask for a restore.
What if our GitHub organization is deleted?+
That is the scenario hailm.io is built for. Your restore points live outside GitHub and outside your accounts, so you can push everything into a new organization or download it.
Which providers do you support?+
GitHub today. Other providers and more of your critical infrastructure are on the roadmap.
Protect your code before you need to.
Connect GitHub, choose your repositories, and have your first locked restore point today.