Transparency alternatives to Zed
Other Coding assistants vendors we measure, sorted by how much we found at them and not at Zed. This is a comparison of disclosure, not of features or fitness.
12 shown of 15 that differ from Zed on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Zed has 7 gaps in what we could measure: Data processing agreement, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Zed” is the one that closes them.
| Vendor | Score | Found there, not found at Zed | Found at Zed, not found there | |
|---|---|---|---|---|
| Factoryfactory.aiSee also Transparency alternatives to Factory | 74/100 | 5 Data processing agreement, Status page with history, Certifications named, +2 | 1 Subprocessor list | Compare |
| Cursorcursor.comSee also Transparency alternatives to Cursor | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Kilokilo.aiSee also Transparency alternatives to Kilo | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Cognitioncognition.comSee also Transparency alternatives to Cognition | 43/100 | 4 Data processing agreement, Certifications named, Uptime SLA with a figure, +1 | 3 Subprocessor list, Data location stated, Public pricing | Compare |
| Qodoqodo.aiSee also Transparency alternatives to Qodo | 35/100 | 4 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | Compare |
| Poolsidepoolside.aiSee also Transparency alternatives to Poolside | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Public pricing | Compare |
| Augment Codeaugmentcode.comSee also Transparency alternatives to Augment Code | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Magicmagic.devSee also Transparency alternatives to Magic | 39/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 3 Subprocessor list, Public pricing, Notice before subprocessors change | Compare |
| Roomoteroomote.devSee also Transparency alternatives to Roomote | 35/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Data location stated, Public pricing | Compare |
| Unblockedgetunblocked.comSee also Transparency alternatives to Unblocked | 30/100 | 3 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | Compare |
| OpenHandsopenhands.devSee also Transparency alternatives to OpenHands | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | Compare |
| Clinecline.botSee also Transparency alternatives to Cline | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Subprocessor list, Data location stated, Public pricing, +2 | 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.