Transparency alternatives to Wowza
Other Video and podcast hosting vendors we measure, sorted by how much they publish that Wowza does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 50 that differ from Wowza on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Wowza has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, 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 “publishes and Wowza does not” is the one that closes them.
| Vendor | Score | Publishes, and Wowza does not | Wowza publishes, and they do not | |
|---|---|---|---|---|
| Loomloom.com | 61/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 1 Data location stated | Compare |
| Simplecastsimplecast.com | 78/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | nothing | Compare |
| WeVideowevideo.com | 70/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| api.videoapi.video | 65/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| JWXjwx.com | 57/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 2 Data location stated, Public pricing | Compare |
| Vidyardvidyard.com | 57/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Status page with history, Public pricing | Compare |
| Cleanvoicecleanvoice.ai | 48/100 | 4 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Transistortransistor.fm | 48/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Auphonicauphonic.com | 52/100 | 3 Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Status page with history, Named privacy contact | Compare |
| Muxmux.com | 52/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Vimeovimeo.com | 43/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Acastacast.com | 35/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, 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.