Alternatives to Manitu
Other Email hosting vendors we measure, sorted by how much they publish that Manitu does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Manitu on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Manitu 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, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Manitu does not” is the one that closes them.
| Vendor | Score | Publishes, and Manitu does not | Manitu publishes, and they do not | |
|---|---|---|---|---|
| Tutatuta.com | 48/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| StartMailstartmail.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Stalwartstalw.art | 39/100 | 3 Data processing agreement, Data location stated, Public pricing | 1 Named privacy contact | Compare |
| Fastmailfastmail.com | 30/100 | 3 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent | 1 Named privacy contact | Compare |
| Gandigandi.net | 30/100 | 3 Data location stated, Status page with history, Certifications named | 1 Named privacy contact | Compare |
| Hushmailhushmail.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Migadumigadu.com | 30/100 | 3 Status page with history, Public pricing, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Purelymailpurelymail.com | 26/100 | 3 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Runboxrunbox.com | 26/100 | 3 Status page with history, Public pricing, No third-party tracking before consent | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Yandex 360yandex.com | 35/100 | 2 Data processing agreement, Data location stated | nothing | Compare |
| df.eudf.eu | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| All-Inklall-inkl.com | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 security.txt (RFC 9116) | 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.