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