Use case · Backup Infrastructure Protection
96% of ransomware attacks explicitly target backup. Myota makes the backup target itself immune by architecture: every backup is encrypted and Shard and Spread™ at write time, so the fragments at the target are individually inert.
Traditional target vs Myota target
| Traditional backup target | Myota target | |
|---|---|---|
| Immutability | A policy you configure, and an attacker can defeat | A mathematical property of the data |
| Compromise a location | The full backup is exposed | Fragments are individually inert |
| Recovery | Restore workflow plus rehydration | Rebuild from any two of four, no rehydration |
| Backup software supply chain | Compromised tools reach the data | Compromised tools can’t access meaningful data |
The economics
A 3-2-1 chain keeps three to four full copies of every backup, and each copy is another target and another line on the storage bill. Myota’s two-of-four shard set delivers equal or better fault tolerance while storing far less data, cutting storage infrastructure costs by 50% with return on investment in under 12 months. Fewer copies is both cheaper and safer: less to store, and less to attack.
Works with your backup software
Myota presents as a standard S3 object target, so any backup software that writes to S3-compatible object storage works behind it, with no change to your policies, schedules, or retention. Cortex monitors backup job health from the storage layer.
