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