Experience precise traffic control with Proxly - HTTP SOCKS Proxy, developed by m.derekand, designed to route Android app traffic through external proxy servers to add privacy and bypass network restrictions. The app accepts HTTP and SOCKS4/SOCKS5 server details, supports username/password authentication, and enables per-app routing so selected applications use the tunnel while others connect directly. Background service keeps connectivity persistent, a clean configuration UI simplifies setup, and the client targets advanced users, network administrators, and developers.

Proxly directs selected apps through standard proxy protocols

Proxly functions as a proxy client that accepts externally hosted servers, supporting HTTP, SOCKS4, and SOCKS5. It requires users to provide server address, port, and optional credentials, and it supports proxies that require username/password authentication. Typical setup involves entering connection details and selecting the apps to tunnel. Practical verification steps include testing credentials and endpoint reachability before enabling app routing.

It runs persistently as a background service with low battery impact

The app operates as a background service to maintain tunneling without manual restarts, and the developer optimizes it for low battery usage during active tunneling. Compatibility targets modern Android releases (typically 5.0 and up) and the project is actively maintained to align with system networking changes. For ongoing tasks like messaging or developer testing, the persistent mode preserves connectivity while the device remains in typical use.

It uses Android networking features so root is not required

Proxly creates a local tunnel using internal Android networking capabilities, so it functions without root access. The architecture gives a VPN-like routing experience while remaining a proxy client, and the app does not supply proxy servers itself. This design avoids direct low-level system writes and keeps changes within the networking layer, which reduces the kind of system modifications some advanced tools perform.

Best suited to technically capable users who manage their own proxies

The tool targets advanced users, network administrators, and developers who supply their own server endpoints and need selective routing or region-based testing. It serves as a single client for both HTTP and SOCKS protocols, offering a compact alternative to configuring broader system-level network solutions. A practical trade-off is reliance on external proxy infrastructure, which places availability and trust responsibilities on the user rather than the client.

Practical choice for technically capable users with one clear trade-off

Proxly suits users comfortable managing external proxy endpoints and configuring app-level network rules; the main trade-off is dependence on externally hosted proxy infrastructure beyond the app. Tip: verify server credentials and connectivity with a non-essential application before directing critical services, and perform initial configuration during idle hours to confirm persistent background operation without interrupting daily use.