Latest changeverification / certifiedshipped

Backup

An independent copy of your repositories, documents and configuration — held outside the platform that holds them.

Protection scope:Internal systems

This one has no third party in it. No beneficiary, no trigger event, no release. It is for you, against the day your git host has a very bad afternoon.

What is backed up

  • Repositories with their full history, branches and tags
  • Issues, wikis and pipeline definitions, where the platform exposes them
  • Configuration and environment descriptions
  • The documents and registers you keep beside the code

Included

  • Daily synchronization
  • The three most recent versions kept
  • Immutable storage, so a compromised account cannot rewrite history
  • AES-256 at rest, keys held separately
  • EEA only, no mirroring and no access from outside
  • Unlimited users

How it comes back out

  1. 01

    You ask for a version. Nobody else has to agree.

  2. 02

    You choose one of the three most recent versions.

  3. 03

    It is handed to you, and you restore it wherever you need it.

What we owe — and what we don't

We owe

  • The pull at the agreed frequency
  • Encrypted storage inside the EEA only
  • A checksum over each package and each file
  • A dated record of every pull
  • The notices

We do not owe

  • That the material is complete, correct, current or authentic
  • That it builds, runs or is free of defects or malware
  • That third-party rights in it exist or are transferable

A copy proves it was taken, not that it rebuilds. That is what Verification is for.

About Verification

Who it is for

Teams whose entire working history sits in one account at one provider. Backup is the cheapest product here and the one most people realize they needed in retrospect.

What it is not

From €79 per month

Single, Multi and All plans, the setup fee and the add-ons are on the pricing page.

  • No release fee
  • Inside the EEA only
  • Held by a lawyer in Vienna

FAQ

Common questions.

Is Backup an escrow?

No. There is no third party, no beneficiary, no trigger event and no release. It is a copy for you.

How many versions are kept?

The three most recent, side by side, in immutable storage — so a compromised account cannot rewrite history.

Where is it stored?

Inside the EEA only, with no mirroring and no access from outside. Encrypted at rest with AES-256, with the keys held separately.