Transparency alternatives to Roadmap
Other Product feedback and updates vendors we measure, sorted by how much they publish that Roadmap does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 14 that differ from Roadmap on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Roadmap has 9 gaps in what we could measure: 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, Named privacy contact. The column “publishes and Roadmap does not” is the one that closes them.
| Vendor | Score | Publishes, and Roadmap does not | Roadmap publishes, and they do not | |
|---|---|---|---|---|
| AnnounceKitannouncekit.app | 61/100 | 4 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | nothing | Compare |
| ProductLiftproductlift.dev | 61/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | nothing | Compare |
| Releasedreleased.so | 57/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Frillfrill.co | 48/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| Featurebasefeaturebase.app | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Cannycanny.io | 23/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, Data location stated | Compare |
| Beamergetbeamer.com | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, Data location stated | Compare |
| UserJotuserjot.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Noticeablenoticeable.io | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Upvotyupvoty.com | 30/100 | 1 HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Changelogfychangelogfy.com | 13/100 | 1 Named privacy contact | 2 Data processing agreement, Data location stated | Compare |
| LoopedInloopedin.io | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Public pricing | 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.