Transparency alternatives to SysCloud
Other Backup and recovery vendors we measure, sorted by how much we found at them and not at SysCloud. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from SysCloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SysCloud has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at SysCloud” is the one that closes them.
| Vendor | Score | Found there, not found at SysCloud | Found at SysCloud, not found there | |
|---|---|---|---|---|
| Rewindrewind.comSee also Transparency alternatives to Rewind | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Data location stated | Compare |
| Keepitkeepit.comSee also Transparency alternatives to Keepit | 35/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Duplicatiduplicati.comSee also Transparency alternatives to Duplicati | 57/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | Compare |
| SimpleBackupssimplebackups.comSee also Transparency alternatives to SimpleBackups | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| BorgBaseborgbase.comSee also Transparency alternatives to BorgBase | 39/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Redstorredstor.comSee also Transparency alternatives to Redstor | 32/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Acronisacronis.comSee also Transparency alternatives to Acronis | 30/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Public pricing, Named privacy contact | Compare |
| Carbonitecarbonite.comSee also Transparency alternatives to Carbonite | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Afiafi.aiSee also Transparency alternatives to Afi | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| SpinOnespin.aiSee also Transparency alternatives to SpinOne | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Barracudabarracuda.comSee also Transparency alternatives to Barracuda | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Cloudbackcloudback.itSee also Transparency alternatives to Cloudback | 26/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Named privacy contact | 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.