Anti-ransomware backups: immutability, explained simply
A good backup is not enough if an attacker can delete it. Immutability (Object Lock) makes your backups indestructible—here's how, and how we compare to Veeam.
The worst scenario of a modern ransomware attack: it encrypts your data AND deletes your backups. A backup that can be erased will not save you. The solution is called immutability.
Immutability = indestructible backup (for a set period)
With Object Lock (WORM mode — *Write Once, Read Many*), a backup, once written, can neither be modified nor deleted for a defined period — even with valid credentials, even by an administrator. An attacker who steals your access credentials therefore cannot destroy your backups.
Our setup (in plain terms)
l'état complet de votre application
une copie datée, prête à restaurer
hors du serveur d'origine — un incendie ne suffit pas
la copie devient physiquement immuable
Pendant 30 jours, personne ne peut modifier ni supprimer cette sauvegarde — pas même nous.
Concrete proof: we attempt to delete a locked backup → the system responds "access denied: object protected by object lock". That is exactly what we want.
How does this compare to Veeam Data Vault?
Veeam Data Vault is an excellent reference (immutability by default, encryption, isolation). We share the same principles — but with one major difference: Veeam Data Vault runs on Microsoft Azure (US), and is therefore subject to the Cloud Act. We apply the same principles while staying in Europe (Scaleway), so as not to break the sovereignty promise.
| Veeam Data Vault | Us | |
|---|---|---|
| Immutability | Yes | Yes (Object Lock) |
| Encryption | Yes | Yes |
| Sovereignty | Azure (US) ❌ | Scaleway (EU) ✅ |
What this guarantees you
Even under attack, even with compromised credentials: your data remains recoverable. That is the difference between "we have backups" and "we have backups that survive an attack".
A sovereign application, delivered and hosted for you.
From idea to production, on a European cloud.
See pricing