Founder-Survivable Public Hosting Provider Review Registry After MXRoute Got a User Fired for a Trustpilot Review
A 1,273-upvote, 327-comment r/selfhosted thread documented a popular email host (MXRoute) trying to get an ex-customer fired from his job after he criticized them publicly for posting retaliatory Trustpilot reviews against other ex-customers. The thread sat at the top of r/selfhosted for a week and produced extensive discussion about how all major hosting/email-provider review platforms (Trustpilot, G2, Capterra) are gamed or defanged by the providers themselves — including via legal threats against reviewers. The unmet need surfaced is a pseudonymous, evidence-supported, legally-hardened hosting-provider review registry where reviewers' identities are protected by a verifiable trust mechanism and a clear policy against complying with takedown demands without a court order. The category includes shared hosting, VPS, email, S3-compatible object storage, and managed Kubernetes — anywhere lock-in plus customer power-asymmetry creates retaliation incentives.
Don't try to be 'reviews for everything' — pick the hosting / VPS / email / object-storage niche where the audience is technically savvy enough to attest invoices via signed receipts or other zero-knowledge primitives. The legal hardness is most of the product: a published policy, a defamation insurance pool, a defamation-defense fund, and an editorial board of pseudonymous-but-trusted reviewers will draw the audience faster than any feature. Revenue model is a paid 'verified buyer' badge for hosts willing to publish their MRR/churn numbers, which separates the legit-but-imperfect hosts from the ones with something to hide.
landscape (5 existing solutions)
Every existing hosting-review surface either lacks structure (forums) or lacks reviewer protection (Trustpilot, G2). The wedge is structural: pseudonymous reviews tied to a verifiable trust score (paid invoice attestation via zero-knowledge proof, account-age signals, vouching from established reviewers), a clear no-comply-without-court-order takedown policy published on day one, and a separate 'incident' track for retaliation events the way SecurityScorecard tracks breaches. Funded as a non-profit or a co-op to avoid the conflict-of-interest trap that captured Trustpilot.