Alternatives to Namespace
Other Developer collaboration and CI vendors we measure, sorted by how much they publish that Namespace does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Namespace on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Namespace has 7 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and Namespace does not” is the one that closes them.
| Vendor | Score | Publishes, and Namespace does not | Namespace publishes, and they do not | |
|---|---|---|---|---|
| CircleCIcircleci.com | 74/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Data processing agreement | Compare |
| CodeRabbitcoderabbit.ai | 70/100 | 4 Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), +1 | nothing | Compare |
| GitHubgithub.com | 57/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 2 Data processing agreement, Data location stated | Compare |
| Aviatoraviator.co | 35/100 | 3 Subprocessor list, Status page with history, Certifications named | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | Compare |
| Codacycodacy.com | 39/100 | 2 Certifications named, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Depotdepot.dev | 35/100 | 2 Subprocessor list, Certifications named | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | Compare |
| Codercoder.com | 30/100 | 2 Certifications named, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Codebergcodeberg.org | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| GitLabgitlab.com | 17/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| Buddybuddy.works | 35/100 | 1 Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Codeclimatecodeclimate.com | 35/100 | 1 Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Daggerdagger.io | 35/100 | 1 Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | 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.