Alternatives to Semaphore
Other Developer collaboration and CI vendors we measure, sorted by how much they publish that Semaphore does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 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 “publishes and Semaphore does not” is the one that closes them.
| Vendor | Score | Publishes, and Semaphore does not | Semaphore publishes, and they do not | |
|---|---|---|---|---|
| Terramateterramate.io | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 2 Status page with history, Certifications named | Compare |
| CodeRabbitcoderabbit.ai | 70/100 | 7 Data processing agreement, Data location stated, Uptime SLA with a figure, +4 | 1 Status page with history | Compare |
| CircleCIcircleci.com | 74/100 | 6 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +3 | nothing | Compare |
| Replitreplit.com | 71/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 Certifications named | Compare |
| GitHubgithub.com | 57/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Namespacenamespace.so | 52/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 2 Status page with history, Certifications named | Compare |
| Codacycodacy.com | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| Scalrscalr.com | 36/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Status page with history, Certifications named | Compare |
| Daggerdagger.io | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Codercoder.com | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Public pricing | Compare |
| Oktetookteto.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Status page with history, Public pricing, Certifications named | Compare |
| Codebergcodeberg.org | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 3 Status page with history, Public pricing, Certifications named | 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.