Alternatives to Speakeasy
Other API management vendors we measure, sorted by how much they publish that Speakeasy does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Speakeasy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Speakeasy has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, Notice before subprocessors change. The column “publishes and Speakeasy does not” is the one that closes them.
| Vendor | Score | Publishes, and Speakeasy does not | Speakeasy publishes, and they do not | |
|---|---|---|---|---|
| Moesifmoesif.com | 65/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Postmanpostman.com | 57/100 | 3 Status page with history, Public pricing, Notice before subprocessors change | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Apollo GraphQLapollographql.com | 39/100 | 3 Subprocessor list, Public pricing, Notice before subprocessors change | 5 Data location stated, Certifications named, No third-party tracking before consent, +2 | Compare |
| Kongkonghq.com | 35/100 | 3 Data processing agreement, Status page with history, Public pricing | 5 Data location stated, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| Bump.shbump.sh | 48/100 | 2 Data processing agreement, Public pricing | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| ReadMereadme.com | 43/100 | 2 Status page with history, Public pricing | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Hasurahasura.io | 35/100 | 2 Subprocessor list, Public pricing | 4 Data location stated, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
| Archbeearchbee.com | 26/100 | 2 Status page with history, Public pricing | 5 Data location stated, Certifications named, No third-party tracking before consent, +2 | Compare |
| Doctavedoctave.com | 22/100 | 2 Data processing agreement, Public pricing | 6 Data location stated, Certifications named, HTTPS enforced with HSTS, +3 | Compare |
| Fernbuildwithfern.com | 35/100 | 1 Public pricing | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Graviteegravitee.io | 35/100 | 1 Public pricing | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Mintlifymintlify.com | 35/100 | 1 Public pricing | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | 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.