Your laptop has the code. Nobody has the issues.
Culacc backs up each GitHub repository with everything around it — issues and pull requests with their comments, the wiki and releases — and keeps every version in the EU.
A Culacc account includes 5 GB of storage free. Works with GitLab, including self-hosted, and Bitbucket too.
A repository lives in one place you don’t control.
Most developers have the code on a laptop. Almost nobody has a copy of years of issue discussion, review comments and release notes — and when a repository or an organisation is deleted, that’s what disappears.
A repository is deleted
By mistake, by a departing admin, or with a leaked token — and GitHub can’t always bring it back.
History is rewritten
A force-push over main replaces commits everyone thought were safe.
The account is locked
A suspended or compromised account can cut you off from your own work.
What Culacc keeps, for each repository
Repositories are checked every hour, and one nobody has pushed to since the last check is skipped — so backing up hundreds of repositories stays quick.
When anything changes, the previous files are kept as versions. Commits replaced by a force-push are still in yesterday’s bundle.
repo.bundleevery branch, tag and commitissues.jsonwith their commentspull-requests.jsonwith review commentswiki.bundlethe wikireleases.jsonwith their notesrepo.jsonthe repository’s settings
Restoring is one git clone
A bundle is plain git, so restoring needs nothing from Culacc. To work with the code, git clone repo.bundle shop is enough. To move the whole repository — every branch and tag — to a new host, clone it as a mirror and push it:
git clone --mirror repo.bundle shop.git
cd shop.git
git push --mirror git@github.com:acme/shop.gitSet up in three steps
Connect GitHub
In Culacc, open Settings → GitHub and press Connect. GitHub asks you to approve access.
Choose what to keep
Every repository you can reach, or only the ones you pick.
Let it run
The first backup starts straight away; after that, every hour. Start one yourself whenever you like.
Send files back as commits or pull requests
From any file in Culacc, choose Send to GitHub: commit it to a branch, or open a pull request from a new one. Useful for design exports, generated docs and anything that starts life outside the repository.
About the access GitHub asks you to approve
To reach private repositories, GitHub offers one permission, and it includes writing. Culacc writes only when you send a file to a repository yourself; backups only read.
Questions people ask
Are private repositories included?
Yes — every repository the connected account can reach, including private ones and those in your organisations.
Where are the backups stored?
In your Culacc account, in data centres in the EU, separate from GitHub.
Do I need Culacc to restore?
No. A bundle is ordinary git, and the issues, pull requests and releases are plain JSON that any script can read.
What about GitLab and Bitbucket?
Both work the same way, including self-hosted GitLab.