Transparency alternatives to Scalar
Other API management vendors we measure, sorted by how much they publish that Scalar does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Scalar on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Scalar has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, 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 Scalar does not” is the one that closes them.
| Vendor | Score | Publishes, and Scalar does not | Scalar publishes, and they do not | |
|---|---|---|---|---|
| Svixsvix.com | 74/100 | 6 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +3 | nothing | Compare |
| Redoclyredocly.com | 65/100 | 6 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +3 | 1 Data location stated | Compare |
| Moesifmoesif.com | 65/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Hookdeckhookdeck.com | 57/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 2 Data location stated, Certifications named | Compare |
| Postmanpostman.com | 57/100 | 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Traefiktraefik.io | 35/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Data location stated, Public pricing, Certifications named | Compare |
| Speakeasyspeakeasy.com | 30/100 | 4 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), +1 | 2 Data location stated, Public pricing | Compare |
| Theneotheneo.io | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| ReadMereadme.com | 43/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| Apollo GraphQLapollographql.com | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Certifications named | Compare |
| Apitallyapitally.io | 35/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 2 Public pricing, Certifications named | Compare |
| Kongkonghq.com | 35/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 2 Data location stated, Certifications named | 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.