Clash Traffic Detective

See exactly which apps and sites eat your proxy traffic

Problem

Proxy subscription quotas quietly vanish every month. Clash Verge's connections page only shows currently open connections, keeps no history, and offers no daily or per-app breakdown, so users can only guess which app or domain burned the traffic.

Solution

A local daemon polls the Clash kernel every second, aggregates connection snapshots into SQLite, and reports traffic by app (merging child processes like Chrome Helper), by root domain, and by node/subscription, separating proxied from direct traffic with daily/weekly comparisons.

Users

Self-hosted Clash/Clash Verge users, proxy subscription buyers, and developers or small teams who need traffic accountability

MVP

Support only Clash Verge; aggregate by app and by site daily/weekly; separate proxy vs direct; store everything locally; ship one overview dashboard

Revenue

Free open-source core plus a one-time Pro license (multi-subscription comparison, quota alerts, CSV export); sponsorships or affiliate deals with proxy providers

Why now

The Clash user base is large but its official views are thin, and traffic aggregation needs no cloud infrastructure, so a solo dev can ship it in a couple of weekends; the more people self-host proxies, the more they care where bytes go