Alternatives to BorgBase
Other Backup and recovery vendors we measure, sorted by how much they publish that BorgBase does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 20 that differ from BorgBase on at least one criterion we measured for both. Public transparency score, not a product or security rating.
BorgBase has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, Notice before subprocessors change. The column “publishes and BorgBase does not” is the one that closes them.
| Vendor | Score | Publishes, and BorgBase does not | BorgBase publishes, and they do not | |
|---|---|---|---|---|
| Barracudabarracuda.com | 48/100 | 3 Status page with history, Certifications named, Notice before subprocessors change | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Keepitkeepit.com | 35/100 | 3 Subprocessor list, Status page with history, Certifications named | 4 Data location stated, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
| Afiafi.ai | 39/100 | 2 Public pricing, Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Cohesitycohesity.com | 39/100 | 2 Status page with history, Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Redstorredstor.com | 32/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Data location stated, No third-party tracking before consent, Named privacy contact | Compare |
| MSP360msp360.com | 22/100 | 2 Status page with history, Certifications named | 4 Data location stated, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
| Acronisacronis.com | 30/100 | 1 Certifications named | 2 No third-party tracking before consent, Named privacy contact | Compare |
| CloudAllycloudally.com | 30/100 | 1 Certifications named | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Comet Backupcometbackup.com | 26/100 | 1 Public pricing | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Carbonitecarbonite.com | 22/100 | 1 Status page with history | 3 Data location stated, No third-party tracking before consent, Named privacy contact | Compare |
| Commvaultcommvault.com | 22/100 | 1 Certifications named | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Ahsayahsay.com | 17/100 | 1 Public pricing | 4 Data location stated, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.