Alternatives to Everdays
Other Funeral home software vendors we measure, sorted by how much they publish that Everdays does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 18 that differ from Everdays on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Everdays has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, 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, Named privacy contact. The column “publishes and Everdays does not” is the one that closes them.
| Vendor | Score | Publishes, and Everdays does not | Everdays publishes, and they do not | |
|---|---|---|---|---|
| Wellthywellthy.com | 43/100 | 4 Public pricing, Certifications named, security.txt (RFC 9116), +1 | nothing | Compare |
| Aeternitasaeternitas.de | 17/100 | 1 No third-party tracking before consent | 1 Data location stated | Compare |
| Passarepassare.com | 17/100 | 1 Status page with history | 1 Data location stated | Compare |
| Willowwillow.co | 17/100 | 1 Public pricing | 1 Data location stated | Compare |
| Empathyempathy.com | 13/100 | 1 security.txt (RFC 9116) | 1 Data location stated | Compare |
| Osirisosirissoftware.com | 9/100 | 1 Public pricing | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Bestattungsvergleichbestattungsvergleich.de | 4/100 | 1 Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Kartdatakartdata.co.uk | 4/100 | 1 Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Chroniclechronicle.rip | 13/100 | nothing we found there and not here | 1 HTTPS enforced with HSTS | Compare |
| Mymoriamymoria.de | 9/100 | nothing we found there and not here | 1 Data location stated | Compare |
| Aftercareaftercare.com | 0/100 | nothing we found there and not here | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Asdmyasd.com | 0/100 | nothing we found there and not here | 2 Data location stated, HTTPS enforced with HSTS | 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.