Tanya

I'm the independent developer behind MonoProxy. I built it for a narrow testing problem: the proxy laptop had become another dependency whenever I needed to check whether a phone, tablet, TV, or test device on the same LAN could actually connect and move traffic.
MonoProxy 2.4.0 runs one local endpoint on an iPhone or iPad for HTTP, HTTPS CONNECT, plain WebSocket, SOCKS4/4a, and SOCKS5 clients. The part I found most useful was separating three states that are often collapsed into one green light:
1. Listening: the endpoint is ready.
2. Client Connected: another device reached it.
3. Traffic Verified: bytes actually crossed the proxy.
The 2.4.0 update also focuses on the cases that expose weak proxy implementations: large downloads, regular and chunked uploads, Range requests, long-lived sessions, and network recovery. A local setup page gives nearby devices the current host, port, PAC details, and platform-oriented commands.
The limits are intentional. This is a local-network tool, not a VPN or a remote proxy service. It does not install a certificate or decrypt HTTPS, and iOS can still suspend networking after the app leaves the foreground.
Product details and screenshots: https://proxy.monoware.app/
App Store: https://apps.apple.com/app/apple...
For anyone who tests devices on a LAN: which part usually fails first for you reachability, proxy configuration, authentication, or proving that real traffic moved?

I expected encryption to be the hard part of building Senvra. The harder decisions were the convenient features I left out.

Account recovery, cloud sync and remote access all sound helpful. They also create an account system, a server and another place where private files can exist. I decided the vault should work without an in-app networking layer or Local Network access. Photos, files and notes stay on the device. Recovery uses an access key and an encrypted backup kept by the owner.