SaaS Ranking

Transparency alternatives to KrakenD

Other API management vendors we measure, sorted by how much we found at them and not at KrakenD. This is a comparison of disclosure, not of features or fitness.

12 shown of 44 that differ from KrakenD on at least one criterion we measured for both. Public transparency score, not a product or security rating.

KrakenD has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at KrakenD” is the one that closes them.

VendorScoreFound there, not found at KrakenDFound at KrakenD, not found there
Redoclyredocly.comSee also Transparency alternatives to Redocly 74/100 7 Data processing agreement, Subprocessor list, Status page with history, +4 1 Data location stated Compare
Svixsvix.comSee also Transparency alternatives to Svix 65/100 5 Subprocessor list, Status page with history, Public pricing, +2 nothing Compare
Postmanpostman.comSee also Transparency alternatives to Postman 57/100 5 Status page with history, Public pricing, Certifications named, +2 1 Named privacy contact Compare
Moesifmoesif.comSee also Transparency alternatives to Moesif 65/100 4 Data processing agreement, Subprocessor list, Certifications named, +1 nothing Compare
Hookdeckhookdeck.comSee also Transparency alternatives to Hookdeck 57/100 4 Data processing agreement, Subprocessor list, Public pricing, +1 1 Data location stated Compare
Theneotheneo.ioSee also Transparency alternatives to Theneo 52/100 3 Data processing agreement, Public pricing, Certifications named nothing Compare
Bump.shbump.shSee also Transparency alternatives to Bump.sh 48/100 3 Data processing agreement, Public pricing, Certifications named 1 Named privacy contact Compare
Kongkonghq.comSee also Transparency alternatives to Kong 48/100 3 Data processing agreement, Status page with history, Public pricing 1 HTTPS enforced with HSTS Compare
Fernbuildwithfern.comSee also Transparency alternatives to Fern 43/100 3 Status page with history, Public pricing, Certifications named 1 Named privacy contact Compare
Apollo GraphQLapollographql.comSee also Transparency alternatives to Apollo GraphQL 39/100 3 Subprocessor list, Public pricing, Notice before subprocessors change 2 Data location stated, Named privacy contact Compare
Hasurahasura.ioSee also Transparency alternatives to Hasura 35/100 3 Subprocessor list, Public pricing, Certifications named 2 Data location stated, Named privacy contact Compare
Stainlessstainless.comSee also Transparency alternatives to Stainless 35/100 3 Public pricing, No third-party tracking before consent, security.txt (RFC 9116) 2 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.