Alternatives to LinuDent
Other Medical practice software vendors we measure, sorted by how much they publish that LinuDent does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from LinuDent on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LinuDent has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and LinuDent does not” is the one that closes them.
| Vendor | Score | Publishes, and LinuDent does not | LinuDent publishes, and they do not | |
|---|---|---|---|---|
| Nookalnookal.com | 78/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | nothing | Compare |
| Clinikocliniko.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Heidi Healthheidihealth.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Doctenadoctena.com | 35/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Tebratebra.com | 30/100 | 3 Data location stated, Status page with history, Public pricing | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| NextGennextgen.com | 30/100 | 2 Data location stated, Certifications named | nothing | Compare |
| SimplePracticesimplepractice.com | 26/100 | 2 Status page with history, Public pricing | 1 Named privacy contact | Compare |
| Doctolibdoctolib.de | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Duriaduria.de | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| CGMcgm.com | 17/100 | 2 Certifications named, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| DrChronodrchrono.com | 17/100 | 2 Status page with history, Public pricing | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| tomedotomedo.de | 26/100 | 1 Data location stated | 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.