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