Fluxzy vs Proxyfor

Fluxzy is an HTTP proxy for recording, analyzing, debugging, and changing HTTP/1.1, HTTP/2, and WebSocket traffic, over plain or secure channels. Its proxyless capture records application traffic without proxy configuration, including apps that ignore system proxy settings. Rules can change headers, add authentication, simulate slow networks, forward requests, spoof DNS, alter TLS fingerprints, and force HTTP versions. It can decode gRPC and Protobuf traffic, and inspect OpenAI, Anthropic, and Google Gemini API requests and responses, including streams and tool calls. Captures can be exported as HAR, Fiddler SAZ, PCAPNG, cURL commands,.http files, or native.fxzy files. Fluxzy works offline without an account or cloud sync, and its site says it has no telemetry. Community is free for personal use and adds an x-fluxzy-community header. Pro is €49, paid once; Enterprise is €59, paid once with a three-seat minimum.

Proxyfor is a proxy command-line tool for capturing and inspecting HTTP, HTTPS, WebSocket, and secure WebSocket traffic. It works in forward or reverse proxy modes and offers both terminal and web interfaces. Captures stream as requests and responses arrive, allowing filtering, searching, and export to Markdown, cURL, or HAR files. The CLI can filter HTTP(S) traffic with a regular expression matching method and URI, or by MIME type. HTTPS inspection requires installing Proxyfor’s CA certificate on the target device; the project describes a built-in certificate installation app. Proxyfor runs on Linux, macOS, Windows, web, and self-hosted deployments. Installation is documented through Cargo, Docker, or downloadable binaries, including a single-file portable executable for desktop systems. Docker instructions mount a configuration directory and expose port 8080. The project is open source under either the MIT License or Apache License 2.0. GitHub lists version 0.5.0 as the latest release.