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