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