Transparency alternatives to Apitally
Other API management vendors we measure, sorted by how much we found at them and not at Apitally. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 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 “Found there, not found at Apitally” is the one that closes them.
| Vendor | Score | Found there, not found at Apitally | Found at Apitally, not found there | |
|---|---|---|---|---|
| Redoclyredocly.comSee also Transparency alternatives to Redocly | 74/100 | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 2 Data location stated, No third-party tracking before consent | Compare |
| Svixsvix.comSee also Transparency alternatives to Svix | 65/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Postmanpostman.comSee also Transparency alternatives to Postman | 57/100 | 5 Status page with history, Public pricing, Certifications named, +2 | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Moesifmoesif.comSee also Transparency alternatives to Moesif | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Hookdeckhookdeck.comSee also Transparency alternatives to Hookdeck | 57/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 2 Data location stated, No third-party tracking before consent | Compare |
| Theneotheneo.ioSee also Transparency alternatives to Theneo | 52/100 | 3 Data processing agreement, Public pricing, Certifications named | 1 No third-party tracking before consent | Compare |
| Bump.shbump.shSee also Transparency alternatives to Bump.sh | 48/100 | 3 Data processing agreement, Public pricing, Certifications named | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Fernbuildwithfern.comSee also Transparency alternatives to Fern | 43/100 | 3 Status page with history, Public pricing, Certifications named | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Apollo GraphQLapollographql.comSee also Transparency alternatives to Apollo GraphQL | 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.ioSee also Transparency alternatives to Hasura | 35/100 | 3 Subprocessor list, Public pricing, Certifications named | 3 Data location stated, No third-party tracking before consent, Named privacy contact | Compare |
| Kongkonghq.comSee also Transparency alternatives to Kong | 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 |
| Traefiktraefik.ioSee also Transparency alternatives to Traefik | 35/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 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.