Save your Git history
A worker mirrors your repository and creates a Git bundle stored through IPFS. Your commits, branches, and tags travel with the backup.
Rivet helps developers keep a recoverable copy of their Git history and a blockchain commitment to their work, while continuing to use GitHub.
A deleted repository, a lost account, or a platform outage should not be the end of your code’s history. Rivet adds a backup and recovery layer alongside GitHub, so your development workflow can stay familiar.
A worker mirrors your repository and creates a Git bundle stored through IPFS. Your commits, branches, and tags travel with the backup.
A commitment to the backup’s commit set is recorded on CKB testnet. Rivet sponsors the backup anchor fee.
Optionally connect JoyID, activate a sponsored CoTA identity, sync your backup proofs, and mint a wallet-owned developer passport.
Use repository restore controls or the source CLI’s exact local restore. Export a recovery file while your account is accessible.
Rivet is open source and currently runs on CKB testnet. Public repository backups work without a wallet. Identity activation is sponsored; an optional passport mint uses your wallet’s test CKB.
GitHub-first onboarding, JoyID ownership checks, sponsored identity activation, user-owned proof records, and Spore passport minting.
Read the delivery report ↗CLI release packaging, stronger backup commitments, attribution restore, and broader recovery acceptance remain in development.
Follow the milestone checklist ↗A CKB anchor establishes that a commitment existed at a blockchain checkpoint. Commit dates remain developer-supplied, and backup file availability depends on continued storage and retrieval.
Private backups, package-registry mirroring, and Bitcoin RGB++ bindings are not part of the current hosted flow. See the guides for the features available today.