Transparency alternatives to Semaphore
Other Developer collaboration and CI vendors we measure, sorted by how much we found at them and not at Semaphore. This is a comparison of disclosure, not of features or fitness.
12 shown of 54 that differ from Semaphore on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Semaphore has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Semaphore” is the one that closes them.
| Vendor | Score | Found there, not found at Semaphore | Found at Semaphore, not found there | |
|---|---|---|---|---|
| Terramateterramate.ioSee also Transparency alternatives to Terramate | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 2 Status page with history, Certifications named | Compare |
| CodeRabbitcoderabbit.aiSee also Transparency alternatives to CodeRabbit | 70/100 | 7 Data processing agreement, Data location stated, Uptime SLA with a figure, +4 | 1 Status page with history | Compare |
| Replitreplit.comSee also Transparency alternatives to Replit | 76/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Warpwarp.devSee also Transparency alternatives to Warp | 74/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| CircleCIcircleci.comSee also Transparency alternatives to CircleCI | 61/100 | 5 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Daytonadaytona.ioSee also Transparency alternatives to Daytona | 61/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | 1 Status page with history | Compare |
| GitHubgithub.comSee also Transparency alternatives to GitHub | 57/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Namespacenamespace.soSee also Transparency alternatives to Namespace | 52/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 2 Status page with history, Certifications named | Compare |
| Onaona.comSee also Transparency alternatives to Ona | 43/100 | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | 2 Status page with history, Public pricing | Compare |
| Codacycodacy.comSee also Transparency alternatives to Codacy | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| Retriumretrium.comSee also Transparency alternatives to Retrium | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| Codercoder.comSee also Transparency alternatives to Coder | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Public pricing | 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.