Transparency alternatives to Mux
Other Video and podcast hosting vendors we measure, sorted by how much we found at them and not at Mux. This is a comparison of disclosure, not of features or fitness.
12 shown of 49 that differ from Mux on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mux has 5 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Mux” is the one that closes them.
| Vendor | Score | Found there, not found at Mux | Found at Mux, not found there | |
|---|---|---|---|---|
| Simplecastsimplecast.comSee also Transparency alternatives to Simplecast | 78/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Certifications named, security.txt (RFC 9116) | Compare |
| api.videoapi.videoSee also Transparency alternatives to api.video | 65/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| JWXjwx.comSee also Transparency alternatives to JWX | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Transistortransistor.fmSee also Transparency alternatives to Transistor | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 4 Data location stated, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Vidyardvidyard.comSee also Transparency alternatives to Vidyard | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| WeVideowevideo.comSee also Transparency alternatives to WeVideo | 70/100 | 2 Data processing agreement, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Loomloom.comSee also Transparency alternatives to Loom | 61/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Data location stated | Compare |
| Cleanvoicecleanvoice.aiSee also Transparency alternatives to Cleanvoice | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 5 Data location stated, Status page with history, Certifications named, +2 | Compare |
| Ravnurravnur.comSee also Transparency alternatives to Ravnur | 22/100 | 2 Subprocessor list, Notice before subprocessors change | 7 Data location stated, Status page with history, Public pricing, +4 | Compare |
| Tellatella.tvSee also Transparency alternatives to Tella | 48/100 | 1 Data processing agreement | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Dacastdacast.comSee also Transparency alternatives to Dacast | 43/100 | 1 Uptime SLA with a figure | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Auphonicauphonic.comSee also Transparency alternatives to Auphonic | 39/100 | 1 No third-party tracking before consent | 4 Status page with history, Certifications named, 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.