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