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