git-backup.

Independent GitHub & GitLab backups

Your code deserves
a second home.

You put a lot into your repositories. Keep a copy beyond your Git provider, with scheduled snapshots and a clear path back when something goes wrong.

See how it works

Private preview · Accounts are currently created by invitation.

Scheduled snapshotsEncrypted archivesVerified downloads
Built around the tools you already use GitHub GitLabYour workflow. An independent copy.

A copy you can come back to

Version control is powerful.
So is having a backup.

Your Git provider is where work happens. An independent snapshot gives you another place to turn when that work is changed, deleted, or out of reach.

Before the force push.

Keep earlier snapshots of your repository, so a rewritten branch doesn’t have to erase your way back.

Beyond a single account.

Previously completed backups remain separate from your provider account. Losing provider access doesn’t remove those copies.

Ready for the next step.

Download a verified Git mirror archive. Recover locally and use standard Git tools to push to a destination you choose.

Less remembering. More building.

A backup routine
that fits your workflow.

Choose what to protect, set a schedule, and keep the history of each run in one workspace.

  1. 01

    Connect & choose

    Connect GitHub or GitLab with a personal access token, then select the repositories you want to back up.

  2. 02

    Set your rhythm

    Schedule hourly, daily, or weekly backups. Run an extra snapshot whenever you need one and follow its progress.

  3. 03

    Find your way back

    Pick a successful snapshot. We check the archive checksum and Git references before preparing your download.

Know what you’re protecting

Your Git history.
With the details intact.

Every successful snapshot holds an independent Git mirror. Give your team visibility without giving everyone the same permissions.

Explore the details

Commits, branches & tags

Preserve the Git objects and references captured by the mirror at backup time.

Schedules & snapshot history

See completed and failed runs, download earlier snapshots, and pin copies you want to keep.

Workspace roles & audit history

Separate owner, admin, operator, and viewer permissions, with a record of workspace activity.

Encryption & verified exports

Archives are encrypted at rest and served over HTTPS. Downloads are checked before release.

Pricing

Room for your code.
Clarity for your budget.

We’re shaping plans for individual developers and teams, with a backup storage allowance measured in GB.

Pricing announced soon · Paid plans aren’t available yet.

For individual developers

Your side projects.
Your safety net.

A straightforward home for the repositories you build and maintain yourself.

How storage works

For teams

One workspace.
A shared way back.

Bring repository schedules, recovery history, and team permissions into one place.

How storage works

What counts as backup storage?

The total size of your retained snapshot archives. For example, 10 snapshots of 200 MB each use about 2 GB. More snapshots mean more storage, even when the repository has changed only a little. Final allowances and rates will be published before paid plans open.

A few good questions

The details,
without the guesswork.

Why back up a repository that’s already on GitHub or GitLab?

A saved snapshot gives you a separate copy of your Git history from before an accidental deletion, force push, or loss of account access. It complements the provider you use every day.

What is included in a backup?

The repository’s Git history, branches, tags, and other Git references captured by the mirror. Issues, pull request discussions, release attachments, CI artifacts, and provider settings are not included. Git LFS file contents and submodule repositories need separate protection; their pointers alone do not back up that data.

How do I restore my code?

Select a successful snapshot in your workspace and choose “Verify & download.” The service checks its checksum and Git references, then returns a Git mirror archive. Extract it locally and use Git to inspect it or push it to a repository you control. Automatic restore into your provider is not available.

How do I connect my repositories?

Existing account holders can connect GitHub or GitLab using a personal access token with the required read permissions, then select repositories in their workspace. Provider OAuth is not enabled in the current preview.

Where are backups stored today?

The current private preview stores encrypted archives on our application server, separately from your Git provider. Off-site object storage is not yet configured. The preview does not currently protect against loss of this server.

Can I sign up or buy a plan?

Access is currently by invitation, and self-service registration and paid subscriptions are not available yet. Existing account holders can sign in above. Prices and storage allowances will be published before paid plans open.

Build what’s next. Keep what got you here.

A little less “what if”.
A way back to your code.

Explore the backup workflow