Your Bitbucket repositories, kept outside Bitbucket.
Culacc saves each repository as a git bundle — every branch, tag and commit — with its pull requests and settings, and keeps every version in the EU.
A Culacc account includes 5 GB of storage free. Works with GitHub and GitLab too.
What Culacc keeps, for each repository
Repositories are checked every hour, and one nobody has pushed to since the last check is skipped. When anything changes, the previous files are kept as versions — so commits replaced by a force-push are still in yesterday’s bundle.
repo.bundleevery branch, tag and commitpull-requests.jsonopen, merged and declinedrepo.jsonthe repository’s settings
Restoring is plain git
A bundle needs nothing from Culacc. To work with the code, git clone repo.bundle api 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 api.git
cd api.git
git push --mirror git@bitbucket.org:acme/api.gitGood to know
Atlassian retired Bitbucket’s own issue tracker and wikis on 20 August 2026, so a backup holds the code, pull requests and settings. Issues Culacc saved before then stay in your account. Bitbucket has no releases.
About access
Culacc reads your repositories to back them up. It writes only when you send a file to a repository yourself.
Questions people ask
Are private repositories included?
Yes — every repository your Bitbucket account can reach, including private ones and those in your workspaces.
Where are the backups stored?
In your Culacc account, in data centres in the EU, separate from Bitbucket.
Do I need Culacc to restore?
No. A bundle is ordinary git, and pull requests are plain JSON.