Dimension scores are derived from public data and fields; weighted into the composite. Reference only.
Podkop is a traffic-routing tool for OpenWrt, positioned around the idea of “send only the resources that need it through a tunnel, and connect directly for everything else.” It is built on sing-box and FakeIP, and provides a LuCI page, Dashboard, diagnostics, and documentation. It is suitable for transparent proxying, VPN-based traffic splitting, or blocking specific resources at the router level.
Its core abstraction is the Section, which lets you configure different outbounds for different types of traffic. Sections support Proxy, VPN, Block, and Exclusion modes: Proxy covers VLESS, Shadowsocks, Trojan, Hysteria2, Socks4/5, and supports connection URLs, Selector, URLTest, and custom sing-box outbounds; VPN mode can use configured interfaces such as WireGuard, AmneziaWG, OpenVPN, and OpenConnect; Block can drop specified domains or subnets; and Exclusion is used to exclude routes. On the DNS side, it supports DoH, DoT, UDP, Bootstrap DNS, FakeIP TTL, and configurable source interfaces, QUIC disabling, list update frequency, and downloading lists via a proxy/VPN.
The text indicates that the Podkop package is written entirely in ash, that the ipk package works across all architectures, and that it has been tested on OpenWrt 24.10. It requires at least 20MB of NAND, with sing-box as a dependency. It can be installed or updated automatically with a one-line shell script, or manually from releases by installing podkop and luci-app-podkop. No paid plans are mentioned; given its GitHub presence, source builds, and releases, it can be regarded as a free and open-source tool. In terms of ecosystem, it integrates with OpenWrt/LuCI, sing-box, dnsmasq, nftables, and YACD, and includes guidance related to AdGuardHome, custom outbounds, and community domain lists.
Its strengths are fine-grained traffic splitting, broad protocol coverage, support for URLTest-based automatic selection, and a diagnostics page that checks DNS, sing-box, nftables, outbounds, and FakeIP, providing a systematic set of troubleshooting information. The downsides are also clear: the documentation is mainly in Russian; the dependency chain is relatively complex; OpenWrt 23.05 is not recommended, while 25.12 has not been tested; and it conflicts with Getdomains, https-dns-proxy, and some legacy iptables packages. For ordinary developers, this is not an “out-of-the-box” cloud tool, but rather a router component geared toward network engineering.
Podkop is best suited to advanced home-network users familiar with OpenWrt, proxy protocols, and DNS/FakeIP, small network administrators, and users who need to route different websites or services through different tunnels. For users in mainland China, installation scripts, releases, and community lists often depend on GitHub. The text also notes that when GitHub or list sources are restricted, lists can be downloaded via Proxy/VPN, so real-world usage may be “partially restricted.” Alternatives include OpenClash, PassWall, Mihomo/Clash Meta, native sing-box configuration, and Xray.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on podkop.net official site.
podkop.net is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach podkop.net directly.