From sign-up to an encrypted, restorable snapshot of your GitLab groups - code, wiki, issues, merge requests, CI/CD and settings, on GitLab.com or your own instance.
Confirm your e-mail, then open Dashboard → GitLab.
2
Connect GitLab
Create a token for backup and restore
CYBBACK reads GitLab with one access token that backs up and restores. Use a dedicated account, for example backup-svc, never a person's own account.
Prepare the account
Create a dedicated GitLab account and add it to the groups to protect with the Owner role (Maintainer is enough to back up; CI/CD variables, webhooks and protections need Maintainer or Owner, and restoring into a group needs the right to create projects).
Signed in as that account: User settings → Personal access tokens → Generate token → Legacy token.
Scopes: api, read_repository, write_repository. read_api alone backs up but cannot restore.
Pick an expiry date - CYBBACK warns you 30 days before it.
Group access token
A group access token (Owner role) also works and is not tied to a person - on GitLab.com it needs a Premium or Ultimate subscription.
Enter the instance URL (https://gitlab.com or your own), the full group paths (as in the URL) and the token, then click Validate.
CYBBACK shows the account, the token scopes and expiry, and the number of projects per group. The token is encrypted (AES-256-GCM) before being stored.
CYBBACK paces itself at 600 requests per minute by default (GitLab.com allows about 2,000) and follows the limit announced by a self-managed instance, so the first backup of a large group can take several hours; the next ones only read what changed.
3
Project selection
Pick what to back up
All projects (default) of the configured groups, subgroups included - new projects are picked up automatically - or Limit to selected projects (click Load projects).
A repository is cloned again only when one of its branches or tags moved; issues and merge requests are re-read only when they changed. Each project is a sub-task: one failing project never blocks the others and is retried alone.
Out of scope, and secrets
Container and package registries, job artifacts and logs, Pages, snippets and Git LFS objects are not backed up. CI/CD variable values are secrets: turn on backup encryption (Storage page). Hidden variables and webhook secret tokens cannot be read through the API.
4
Bring Your Own Bucket
Use your own S3-compatible storage
Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.
Provision the bucket
In your S3 provider, create a private bucket (no public access, versioning recommended).
Create an access key / secret key with permissions limited to that bucket.
Required IAM actions:PutObject, GetObject, DeleteObject, ListBucket.
Resilience: CYBBACK stores an encrypted snapshot of S3 credentials with each backup. Old backups remain restorable even after you switch providers.
Disk usage: a typical mirror of 100 active projects (~2 GB combined) takes ~500 MB on S3 thanks to git's natural compression.
5
First backup
Run your first backup
Back on the Dashboard tab, click Start a backup. A daily schedule (04:30 Europe/Paris) is created automatically after the first backup.
Follow the progress live in the history (Per-project detail) or on the Events page.
A project that fails (permissions, repository too large…) is listed with its reason under the backup - the others are still saved.
6
Restore
Restore - same or another group
Selection. Browse groups and projects like in GitLab - Repository, Issues, Merge requests, Wiki, CI/CD, Settings - and tick a whole project or single items in every tab: branches and tags, files or folders of a branch, issues, open merge requests, releases, variables, environments, protections, webhooks, members. Compare with GitLab preselects the branches deleted or rewritten since the backup.
Files and folders. In the Repository tab, the Restore files or folders card shows the file tree of any branch or tag as it was on the backup date: expand folders, search a path, tick files or whole folders (a ticked folder covers everything below it), then choose the branch receiving the commit (the source branch or a new branch created from a base branch, with an optional merge request). The rest of the repository is left untouched. The tree is available for backups that captured the code after this feature was released.
Options. Dry run, target group, path suffix, create the project when missing, keep the old number in the title, recycle bin, branch naming (same name, safe restored/<date>/ prefix or names you choose), another existing project, overwrite (explicit confirmation; a protected branch is unprotected for the push and protected again).
Execution. The worker pushes the bundles, recreates labels, milestones, issues with their notes, variables, schedules and protections, and logs every step. A re-run never duplicates restored issues.
Issues and merge requests get a new number (the old one is kept in the title); author and date become the restore account's, with the originals written in the text and no mention, so nobody is notified. Only open merge requests are recreated; merged and closed ones, approvals and issue boards stay in the export (JSON, CSV, HTML). Webhook secret tokens and hidden variables must be re-entered.
You're all set.
Need help? Our team replies within one business day on every plan.