Transparency alternatives to WoodWing Cloud
Other Digital asset management vendors we measure, sorted by how much we found at them and not at WoodWing Cloud. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from WoodWing Cloud on at least one criterion we measured for both. Public transparency score, not a product or security rating.
WoodWing Cloud has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at WoodWing Cloud” is the one that closes them.
| Vendor | Score | Found there, not found at WoodWing Cloud | Found at WoodWing Cloud, not found there | |
|---|---|---|---|---|
| Cloudinarycloudinary.comSee also Transparency alternatives to Cloudinary | 64/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 1 HTTPS enforced with HSTS | Compare |
| Frontifyfrontify.comSee also Transparency alternatives to Frontify | 52/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Imgiximgix.comSee also Transparency alternatives to Imgix | 43/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Massetgetmasset.comSee also Transparency alternatives to Masset | 43/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Brandfolderbrandfolder.comSee also Transparency alternatives to Brandfolder | 39/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Filecampfilecamp.comSee also Transparency alternatives to Filecamp | 36/100 | 4 Public pricing, Certifications named, Uptime SLA with a figure, +1 | 1 HTTPS enforced with HSTS | Compare |
| Uploadcareuploadcare.comSee also Transparency alternatives to Uploadcare | 30/100 | 4 Status page with history, Public pricing, Uptime SLA with a figure, +1 | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Sitecore Content Hubsitecore.comSee also Transparency alternatives to Sitecore Content Hub | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Aprimoaprimo.comSee also Transparency alternatives to Aprimo | 30/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Bynderbynder.comSee also Transparency alternatives to Bynder | 30/100 | 3 Public pricing, Certifications named, Named privacy contact | 1 Data location stated | Compare |
| Airair.incSee also Transparency alternatives to Air | 27/100 | 3 Public pricing, Certifications named, Uptime SLA with a figure | 1 Data location stated | Compare |
| Scaleflexscaleflex.comSee also Transparency alternatives to Scaleflex | 30/100 | 2 Status page with history, Public pricing | 1 Data location stated | 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.