Alternatives to Tettra
Other Knowledge base and wiki vendors we measure, sorted by how much they publish that Tettra does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Tettra on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Tettra has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, 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 “publishes and Tettra does not” is the one that closes them.
| Vendor | Score | Publishes, and Tettra does not | Tettra publishes, and they do not | |
|---|---|---|---|---|
| Docmostdocmost.com | 43/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| Codacoda.io | 39/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Gurugetguru.com | 30/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | 2 Data location stated, Public pricing | Compare |
| Slabslab.com | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| BookStackbookstackapp.com | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Nuclinonuclino.com | 22/100 | 3 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| Obsidianobsidian.md | 39/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 Named privacy contact | Compare |
| Anytypeanytype.io | 26/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Named privacy contact | Compare |
| Helpjuicehelpjuice.com | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Papyrspapyrs.com | 23/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Fiberyfibery.io | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Almanacalmanac.io | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | 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.