Alternatives to Upwind
Other Container and cloud workload security vendors we measure, sorted by how much they publish that Upwind does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 17 that differ from Upwind on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Upwind has 6 gaps in what we could measure: Data location stated, Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Upwind does not” is the one that closes them.
| Vendor | Score | Publishes, and Upwind does not | Upwind publishes, and they do not | |
|---|---|---|---|---|
| Docker Scoutdocker.com | 43/100 | 5 Data location stated, Public pricing, HTTPS enforced with HSTS, +2 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Socketsocket.dev | 48/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Endor Labsendorlabs.com | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Subprocessor list, Certifications named | Compare |
| Chainguardchainguard.dev | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Prisma Cloudprismacloud.io | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Nirmatanirmata.com | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Anchoreanchore.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Cast AIcast.ai | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Isovalentisovalent.com | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Sweet Securitysweet.security | 17/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Fairwindsfairwinds.com | 9/100 | 1 HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Falcofalco.org | 9/100 | 1 HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 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.