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