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