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