Service description
What lionbackup provides: architecture, encryption, storage and lifecycle.
This is a convenience translation. Only the German version is legally binding: German version.
1. Overview
lionbackup is a cloud backup service for businesses. Customers back up data in encrypted form through a lightweight client into dedicated storage zones that are isolated from each other. Organisations, projects, access tokens and billing are managed in a customer portal. The service is multi-tenant and designed for transparent, sovereign data storage in Europe.
2. Zone model: backup zone and storage zones
The platform consists of one central backup zone (BZ) and several storage zones (SZ):
- The backup zone runs the central services: portal, management API, databases, message queues and observability (monitoring and logging). It exists exactly once per environment.
- The storage zones are storage clusters isolated from each other at network level, possibly with different providers and at different locations. In each storage zone the Citadels receive the encrypted backups.
Storage zones and the backup zone are connected by encrypted, mutually authenticated connections. Only management data and metadata travel over these connections (for example reference data, file metadata, replication); the customer uploads themselves go directly to the public endpoints of the Citadels and do not pass through the backup zone.
3. Citadels: the storage endpoints
A Citadel is the customer-facing storage endpoint of a storage zone. It accepts the encrypted data objects over HTTPS, checks authentication, quotas and limits, and stores the objects in the zone's local storage system. Several Citadels can run per storage zone; the client selects an available endpoint and switches to another one by itself if a failure occurs during the transfer.
4. Encryption
The data to be backed up can be encrypted end-to-end on the client side before it leaves the customer's system. The client-side keys remain exclusively with the customer; the provider receives this content only as ciphertext. In addition, the objects are stored encrypted on the server side. Asymmetric methods make it possible to encrypt backups for a recipient without that recipient holding the same secret key.
Specific algorithms and key lengths are documented in the security concept.
5. Immutable, write-protected storage (WORN) and retention period
Backups are kept for a retention period chosen by the customer (default: 30 days, at most 365 days). For projects configured accordingly, the principle WORN ("Write Once, Read Never") applies: objects are written exactly once and can be neither changed nor deleted during the retention period. The platform enforces this immutability; in addition, a write token cannot read existing backups. This protects backups against accidental or malicious deletion, for example in ransomware incidents. A separate token with read permission is used for restores. The chosen retention period is also a binding order to retain the data: until it expires, the storage remains occupied and chargeable, even if the contract otherwise ends earlier (see Terms, § 10). Customers who do not want to commit choose a shorter retention period or a project without immutable storage.
6. Lifecycle of a backup
Every stored object passes through a clearly defined lifecycle:
- stored: the object is stored and protected during the retention period;
- expired: the retention period has been reached; the object is scheduled for removal;
- deleted: the object is marked as deleted and removed from the active inventory;
- finally removed (purge): the associated data is irretrievably removed from storage.
7. Replication and zone isolation
The storage zones are separated from each other and from the backup zone at network level (own private subnets, separate providers or projects). Management data and metadata are synchronised between the zones over the encrypted, mutually authenticated connections. If the backup zone is temporarily unavailable, the storage zones can continue operating with zone-local data.
The backed-up objects themselves are not mirrored between zones; they reside exclusively in the storage zone the customer chose for the project. If the infrastructure provider of a zone ceases permanently, we move the zone to an equivalent provider (§ 11 of the Terms). For particularly critical data we recommend additionally backing up into a project in a second storage zone with a different provider.
8. Customer portal: organisations, projects and tokens
The portal is the central management interface. Customers create organisations and manage projects within them. Access is controlled through roles (for example owner, administrator, writer, reader, billing). Project-specific access tokens are issued for automated use through the client. Sign-in uses single sign-on with mandatory multi-factor authentication (TOTP) through a central identity platform.
9. Anomaly detection
Security-relevant events of the Citadels are evaluated centrally. An automated anomaly detection recognises, among other things, the use of tokens outside their intended project, indications of unencrypted uploads (low entropy) and statistical outliers in volume and throughput. Findings are shown as notices in the portal and can optionally be delivered by email to subscribed recipients.
10. Client software
Backups are made with a lightweight client written in Go, provided as an open-source client. The client compresses, encrypts and transfers the data to an available Citadel and supports both Linux and Windows. Prebuilt binaries are available for download; the source code is publicly available.
11. Locations and providers
The service is operated in data centres in Europe. Currently available are the storage zones de01-1 in Nuremberg, Germany (data centre provider: Hetzner), de02-1 in Frankfurt am Main, Germany (IONOS) and it01-1 in Ponte San Pietro, Italy (Aruba); further zones are in preparation. The customer chooses the zone per project. The service specification summarises specific locations and parameters.