Transparency alternatives to Fern
Other API management vendors we measure, sorted by how much we found at them and not at Fern. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from Fern on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Fern has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Fern” is the one that closes them.
| Vendor | Score | Found there, not found at Fern | Found at Fern, not found there | |
|---|---|---|---|---|
| Redoclyredocly.comSee also Transparency alternatives to Redocly | 74/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 1 Data location stated | Compare |
| Moesifmoesif.comSee also Transparency alternatives to Moesif | 65/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| Hookdeckhookdeck.comSee also Transparency alternatives to Hookdeck | 57/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 3 Data location stated, Status page with history, Certifications named | Compare |
| Svixsvix.comSee also Transparency alternatives to Svix | 65/100 | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Traefiktraefik.ioSee also Transparency alternatives to Traefik | 35/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Speakeasyspeakeasy.comSee also Transparency alternatives to Speakeasy | 30/100 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | 3 Data location stated, Status page with history, Public pricing | Compare |
| Postmanpostman.comSee also Transparency alternatives to Postman | 57/100 | 2 security.txt (RFC 9116), Notice before subprocessors change | nothing | Compare |
| Theneotheneo.ioSee also Transparency alternatives to Theneo | 52/100 | 2 Data processing agreement, Named privacy contact | 1 Status page with history | Compare |
| Apollo GraphQLapollographql.comSee also Transparency alternatives to Apollo GraphQL | 39/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Data location stated, Status page with history, Certifications named | Compare |
| Apitallyapitally.ioSee also Transparency alternatives to Apitally | 35/100 | 2 No third-party tracking before consent, Named privacy contact | 3 Status page with history, Public pricing, Certifications named | Compare |
| Kongkonghq.comSee also Transparency alternatives to Kong | 35/100 | 2 Data processing agreement, Named privacy contact | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | Compare |
| Stainlessstainless.comSee also Transparency alternatives to Stainless | 35/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 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.