lionbackup
lionbackup is a cloud backup service for businesses and teams. Data is backed up through a lightweight client, optionally end-to-end encrypted on the customer's own system, and transferred to geographically distributed storage zones in Europe. Everything is managed through a customer portal with organizations, projects and access tokens.
At a glance
- Client-side encryption. Backups can be encrypted before they ever leave the customer's system. The client-side keys remain exclusively with the customer; lionbackup only ever receives the content as ciphertext.
- Sovereign data storage in Europe. Data is stored in data centres in Europe, spread across several providers and locations. You choose the region your data lives in.
- Immutable, write-protected storage (WORN). Projects configured accordingly store backups immutably for the chosen retention period — protection against accidental or malicious deletion, e.g. in ransomware incidents. Reading is done exclusively via a separate token with read permission (see Lifecycle of a backup).
- Multi-tenant portal. Organizations, projects, roles, tokens and billing in one place, with single sign-on and multi-factor authentication.
- Open-source client. Backups run through a lightweight client written in Go for Linux and Windows, whose source code is publicly available.
How the platform is built
lionbackup is divided into a central Business Zone and several mutually isolated Storage Zones. The Business Zone runs the portal, the management API and central services; the Storage Zones receive the encrypted backups through so-called Citadels. The actual uploads go directly to the Citadels and do not pass through the Business Zone.
Read more under Architecture.
Where to go next
- Getting started — organization, project, token and the first backup run.
- Encryption — how your data is protected.
- Lifecycle of a backup — from
storedtodeleted. - Frequently asked questions (FAQ) — short answers to the most common questions.
lionbackup is being continuously developed. The content and level of detail of this documentation may change as the platform evolves. The binding, currently usable parameters are summarized in the service specification.