Actually free. The Community edition has every feature - raw packet capture, breakpoints, rules engine, the works. The only difference is a small header annotation in captured traffic. If you're debugging your own stuff, you'll never care. If you're doing client work or don't want that header, grab a license. That's it. No 14-day trials. No "upgrade to unlock filters." No dark patterns.

Fiddler was brilliant. In 2010. But it's still built on .NET Framework, still thinks HTTP/2 is exotic, and still can't give you raw packet captures without bolting on Wireshark separately. Fluxzy was built for how we actually work now - streaming architecture, native PCAPNG support, TLS fingerprinting, YAML rules you can version control. If you've ever tried to get Fiddler working reliably in a CI pipeline, you know the pain. Fluxzy was designed for that from day one.

For HTTPS interception, yes - that's just how TLS works. But Fluxzy makes it painless. One-click certificate installation, auto-configured browser launching, and clear guidance for mobile devices. We also support custom root CAs if your organization already has one, and you can skip decryption entirely for traffic you don't need to inspect.

Absolutely. Same rule engine runs headless via CLI with the same YAML configuration. Stick it in a Docker container, run it in GitHub Actions, use it as a sidecar - Fluxzy doesn't care. Desktop and CLI aren't different products with different capabilities. They're the same engine with different interfaces.

Some servers detect automation by looking at your TLS handshake - cipher suites, extensions, the order they appear in. It's a bot-detection technique. Fluxzy can impersonate real browsers at the TLS level, not just with headers. As far as we know, we're the only tool in this category that does this properly.

HTTP/2 is fully supported - proper multiplexing, header compression, the whole deal. HTTP/3 support is on the roadmap. We'd rather ship features that work reliably than checkbox features that break under real conditions.

Most proxies show you parsed HTTP. That's usually enough. But sometimes you need to see what actually went over the wire - TCP retransmissions, TLS negotiation details, timing at the packet level. Fluxzy captures full PCAPNG alongside HTTP traffic. Open it in Wireshark, correlate packets with requests, diagnose problems that HTTP-level tools can't see. It's like having X-ray vision for debugging.

Yes. Fluxzy.Core is MIT-licensed on GitHub. You can audit every line of interception code, every cryptographic decision. Fork it, embed it, build products on it. The Desktop app is freeware but closed source - we need to keep the lights on somehow.

Really. Pay once, use forever. We're not going to hold your debugging sessions hostage to recurring payments. Major version upgrades might cost extra someday, but your license never expires and the version you bought keeps working.

GitHub issues. We actually read them and respond. For licensed users, there's priority email support. But honestly, most bugs get fixed through GitHub because that's where the community is.

We rewrote the frontend in Tauri. Same capabilities, native performance, no Chromium runtime bloating your Applications folder. The 2.0 release was basically "what if we rebuilt this without the parts that made everyone's laptop fans spin up?"