Transparency alternatives to ReadMe
Other API management vendors we measure, sorted by how much we found at them and not at ReadMe. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from ReadMe on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ReadMe has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at ReadMe” is the one that closes them.
| Vendor | Score | Found there, not found at ReadMe | Found at ReadMe, not found there | |
|---|---|---|---|---|
| Redoclyredocly.comSee also Transparency alternatives to Redocly | 74/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 Data location stated | Compare |
| Moesifmoesif.comSee also Transparency alternatives to Moesif | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Status page with history, Public pricing | Compare |
| Svixsvix.comSee also Transparency alternatives to Svix | 65/100 | 3 Subprocessor list, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Hookdeckhookdeck.comSee also Transparency alternatives to Hookdeck | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Data location stated, Status page with history | Compare |
| Postmanpostman.comSee also Transparency alternatives to Postman | 57/100 | 3 Certifications named, security.txt (RFC 9116), Notice before subprocessors change | 1 Named privacy contact | Compare |
| Traefiktraefik.ioSee also Transparency alternatives to Traefik | 35/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Speakeasyspeakeasy.comSee also Transparency alternatives to Speakeasy | 30/100 | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Public pricing | Compare |
| Theneotheneo.ioSee also Transparency alternatives to Theneo | 52/100 | 2 Data processing agreement, Certifications named | 1 Status page with history | Compare |
| Bump.shbump.shSee also Transparency alternatives to Bump.sh | 48/100 | 2 Data processing agreement, Certifications named | 2 Status page with history, Named privacy contact | Compare |
| Apollo GraphQLapollographql.comSee also Transparency alternatives to Apollo GraphQL | 39/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Hasurahasura.ioSee also Transparency alternatives to Hasura | 35/100 | 2 Subprocessor list, Certifications named | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Stainlessstainless.comSee also Transparency alternatives to Stainless | 35/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 3 Status page with history, HTTPS enforced with HSTS, 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.