Valrify — safer account trading.

Valrify began from my own experience buying and selling Valorant accounts and seeing recurring scams and hack-back cases in the community. Transaction history is often scattered across chats, social posts, and private groups, so the product brings searchable identifiers, reviewed reports, transaction confirmations, and community context into one reputation profile—without presenting the platform as a guarantee of safety or a legal authority.

I shaped the product around evidence, neutrality, and privacy. Reports move through a controlled review workflow before publication; raw evidence and reporter identities stay private; and public identifiers are normalized, linked, or masked according to explicit rules. Search supports the identity types people actually encounter before a transaction, from Riot IDs and usernames to phone, bank, and e-wallet details.

Valrify is a TypeScript monorepo with a Next.js and React web app backed by a NestJS REST API. PostgreSQL and Drizzle model users, entities, identifiers, reports, evidence, moderation history, transaction confirmations, community activity, and notifications. Shared domain and validation packages keep normalization, role permissions, risk labels, and schemas consistent across the system. Evidence can be stored locally in development or in a private Cloudflare R2 bucket, while targeted rate limits protect authentication, search, uploads, and submissions.

Valrify is publicly available at valrify.app. The product brings identity search, evidence-backed reporting, admin review and publication, reputation profiles, positive transaction confirmations, authentication, notifications, and community discussion into one platform.

Building a trust-sensitive product required more than a polished interface. The key lesson was to encode moderation states, attribution, identifier visibility, and privacy boundaries as shared domain rules, so the web app and API cannot quietly drift into different interpretations of what is safe to expose.