Blog

Field notes on lead arbitrage, antifraud, on-prem infrastructure, and running a self-hosted CRM.

• v1.2 beta is live — from closed alpha to public beta: We rebuilt the core for absolute authority over your data: single-digit-ms lead processing, sub-300ms analytics over millions of rows, an armored native core, and the visual JSON mapper v2.
• Why we built a CRM for arbitrage — not another tracker: Trackers count clicks. Money is made and lost on leads: their quality, their status, and whether the partner pays. d0pe is built around the lead, end to end.
• Anatomy of the Mask: five checks, one verdict: A tour of the edge filter — what each checker actually inspects, how the signals combine into a score, and why the visitor never notices.
• On-prem and anonymous: the licensing model, explained: How a self-hosted product still ships signed updates, protects its core, and detects a cloned VPS — without ever phoning your data home.
• How advertisers score your traffic — and how to pass: Every CPA network runs its own antifraud on the leads you send. Send junk and your rates get cut or your account closed. The fix is to score first — before delivery.
• Why on-prem beats cloud trackers for gray verticals: Cloud tools are convenient — until your sources, geos and real numbers live on someone else's server. For sensitive verticals, on-prem isn't paranoia; it's the default.
• Reading device entropy: beyond CreepJS: A device fingerprint is only as strong as the entropy behind it. Here's what actually separates a real human's device from an emulator — and why one signal is never enough.
• Approve rate: the hidden multiplier on every campaign: Two buyers run the same offer at the same cost and one prints while the other bleeds. The difference is approve rate — the number that quietly multiplies everything downstream.