TechnicalApril 15, 2026 5 min
Building a Real-Time Ganker Intelligence System
How COMPASS profiles gankers from zKillboard data — behavioral analysis, activity patterns, fleet detection, and threat scoring.
Every highsec kill in EVE flows through our pipeline. We classify, profile, and score — turning raw kill data into actionable intelligence.
R2Z2
Data Source
~5s
Kill → Alert
4
Confidence Tiers
12
Behavioral Labels
Evidence-Based Classification
Verified
CONCORD on attacker list + victim corp not war-eligible = definitive criminal act
Likely
Known ganker corp/alliance, zKillboard labels, fleet composition matching gank patterns
Suspected
Heuristic signals: fleet size, ship types, ISK value anomalies
Legal PvP
Confirmed wardec — not a gank. Excluded from ganker profiles.
Behavioral Labels
Fleet CommanderAvg fleet 5+
Solo GankerOperates alone
Pipe Camper90%+ in 1-2 systems
Whale HunterAvg victim >2B ISK
Nomadic5+ systems active
High Frequency5+ ganks/week
From Kill to Alert
1
R2Z2 Ingestion
Sequential polling from Cloudflare R2. Every kill in EVE, filtered to highsec.
2
Classification
Evidence-based: CONCORD presence, war eligibility, corp/alliance analysis, fleet composition.
3
Profile Update
Ganker profiles, ship usage, system activity, kill counts — all updated in real-time.
4
Watchlist Check
If the system or any attacker is on a user's watchlist → instant Supabase Realtime alert.