Alternatives to CodeGPT
Other Coding assistants vendors we measure, sorted by how much they publish that CodeGPT does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 14 that differ from CodeGPT on at least one criterion we measured for both. Public transparency score, not a product or security rating.
CodeGPT has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and CodeGPT does not” is the one that closes them.
| Vendor | Score | Publishes, and CodeGPT does not | CodeGPT publishes, and they do not | |
|---|---|---|---|---|
| Factoryfactory.ai | 74/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | nothing | Compare |
| Poolsidepoolside.ai | 52/100 | 5 Data processing agreement, Data location stated, security.txt (RFC 9116), +2 | 1 Public pricing | Compare |
| Cognitioncognition.com | 43/100 | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | 1 Public pricing | Compare |
| Augment Codeaugmentcode.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Cursorcursor.com | 48/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Zedzed.dev | 48/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 1 HTTPS enforced with HSTS | Compare |
| Magicmagic.dev | 39/100 | 4 Data location stated, No third-party tracking before consent, security.txt (RFC 9116), +1 | 1 Public pricing | Compare |
| Roomoteroomote.dev | 35/100 | 4 Status page with history, Certifications named, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Kilokilo.ai | 43/100 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | nothing | Compare |
| Qodoqodo.ai | 39/100 | 3 Status page with history, No third-party tracking before consent, security.txt (RFC 9116) | nothing | Compare |
| Tabninetabnine.com | 13/100 | 2 Status page with history, Certifications named | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Clinecline.bot | 13/100 | 1 security.txt (RFC 9116) | 1 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.