Alternatives to Stoplight
Other API management vendors we measure, sorted by how much they publish that Stoplight does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Stoplight on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Stoplight has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, 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. The column “publishes and Stoplight does not” is the one that closes them.
| Vendor | Score | Publishes, and Stoplight does not | Stoplight publishes, and they do not | |
|---|---|---|---|---|
| Redoclyredocly.com | 65/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Data location stated, Status page with history | Compare |
| Moesifmoesif.com | 65/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 Status page with history, Public pricing | Compare |
| Postmanpostman.com | 57/100 | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Named privacy contact | Compare |
| Speakeasyspeakeasy.com | 43/100 | 4 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 2 Status page with history, Public pricing | Compare |
| Traefiktraefik.io | 35/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Theneotheneo.io | 52/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Bump.shbump.sh | 48/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Apollo GraphQLapollographql.com | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Hasurahasura.io | 35/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Apitallyapitally.io | 35/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Status page with history, Public pricing | Compare |
| Fernbuildwithfern.com | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Graviteegravitee.io | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Status page with history, 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.