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