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