Use cases
Capture, store, match, and decide - complete job-to-be-done solution hubs for every major anti-fraud use case. 6 guides published.
Anti-fraud
A metered paywall counts free articles in a cookie the reader controls, so clearing site data, opening a private window, or switching browsers hands them a fresh allowance. Keying the meter to a cross-browser hardware fingerprint, which survives all three, makes the meter hold.
Anti-fraud
Account sharing is multi-accounting in reverse: one login spread across many physical devices. Counting distinct cross-browser hardware fingerprints per account measures real machines, so one person on two browsers counts once and a sharer who switches browsers does not look like a new device.
Anti-fraud
Referral programs pay real credit per signup, so the dominant abuse is self-referral and referral rings: one person or a handful of devices behind many 'distinct' referees. Cross-browser device matching links the referee back to the referrer and collapses the ring, even across browser switches and incognito.
Anti-fraud
Bots and anti-detect browsers are two unrelated threats that a single fingerprint hash misses. Benny returns two independent scores on every call, an automation likelihood for drivers and a spoof likelihood for forged browsers, so you can gate both client-side without a CAPTCHA.
Anti-fraud
Multi-accounting survives every identity check users control: new email addresses, VPNs, cookie clears, different browsers. A hardware-bound device fingerprint with cross-browser comparison is the durable key that catches the same device regardless of how the account layer is reset.
Anti-fraud
Cookie-based trial gates fail the moment a user clears their browser history. A hardware-bound device fingerprint persists through cookie clears, browser switches, and incognito mode, making it the practical foundation for per-device trial enforcement.
