Transparency alternatives to Coda
Other Knowledge base and wiki vendors we measure, sorted by how much we found at them and not at Coda. This is a comparison of disclosure, not of features or fitness.
12 shown of 42 that differ from Coda on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Coda has 6 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, Notice before subprocessors change. The column “Found there, not found at Coda” is the one that closes them.
| Vendor | Score | Found there, not found at Coda | Found at Coda, not found there | |
|---|---|---|---|---|
| Waybookwaybook.comSee also Transparency alternatives to Waybook | 52/100 | 3 Subprocessor list, Data location stated, Notice before subprocessors change | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Scribescribehow.comSee also Transparency alternatives to Scribe | 48/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Kipwisekipwise.comSee also Transparency alternatives to Kipwise | 48/100 | 2 Subprocessor list, Data location stated | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Claromentisclaromentis.comSee also Transparency alternatives to Claromentis | 43/100 | 2 Data processing agreement, Data location stated | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Docmostdocmost.comSee also Transparency alternatives to Docmost | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Shelfshelf.ioSee also Transparency alternatives to Shelf | 39/100 | 1 Data location stated | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Slabslab.comSee also Transparency alternatives to Slab | 39/100 | 1 Data location stated | 2 Status page with history, Named privacy contact | Compare |
| Sliteslite.comSee also Transparency alternatives to Slite | 39/100 | 1 Data location stated | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Whaleusewhale.ioSee also Transparency alternatives to Whale | 39/100 | 1 Data location stated | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Gurugetguru.comSee also Transparency alternatives to Guru | 30/100 | 1 Uptime SLA with a figure | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Nuclinonuclino.comSee also Transparency alternatives to Nuclino | 30/100 | 1 No third-party tracking before consent | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Anytypeanytype.ioSee also Transparency alternatives to Anytype | 26/100 | 1 No third-party tracking before consent | 4 Status page with history, Certifications named, security.txt (RFC 9116), +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.