A desktop HTTP and HTTPS proxy for macOS, Windows, and Ubuntu. It lets developers, QA engineers, and testing specialists inspect and modify network traffic from their own browsers, mobile apps, and devices.

The Base tier is free with no time limit, but limited in functionality. You can start using it right away, no account needed. The Pro subscription lifts all limits; it needs an account.

Does it work with HTTPS?

Yes, by installing a local root certificate for decryption. Fully optional — you choose what to decrypt, and can remove the certificate any time.

The proxy runs locally on your machine: captured data stays on your device and is not sent to external servers. HTTPS is decrypted only after you install a local certificate yourself. You remain responsible for whose traffic you debug.

What must Solpuga not be used for?

It is a tool for debugging your own systems. It must not be used to intercept the traffic of third parties without their consent, to bypass protection on services that are not yours, to covertly monitor other people’s devices, or to reach resources restricted by the law of the Russian Federation.

Anyone with lawful access to the system whose traffic they're debugging: a regular user on their own machine, an employee within company policy, or a contractor under agreement.

Can I use it with iOS / Android devices?

Yes. Point the device's Wi-Fi proxy setting to the proxy address, then install and trust the Solpuga certificate. Android also supports proxying over USB.

What protocols does it support?

HTTP/1.1, HTTPS, Server-Sent Events (SSE), and WebSocket — plaintext or encrypted, with full visibility into headers, bodies, and timing. Streaming responses show event by event as they arrive, without waiting for the connection to close.

Migrating from Fiddler

Fiddler is two different products and you leave them for different reasons.

First: Classic or Everywhere

Fiddler Classic — Windows only, and since 3 August 2026 licensed for personal, non-commercial use only: for commercial use Telerik points you at Everywhere. It is not in active development, with no commitment to releases, patches or support. It has FiddlerScript, AutoResponder, Composer, its own .saz archive, and HTTP/1.x.

Fiddler Everywhere — Windows, macOS and Linux, by subscription, with HTTP/2. There is no FiddlerScript in it: a Rules tab replaces AutoResponder.

If you are on Classic and the work is commercial, you have to move anyway and the only question is where. If you are on Everywhere, read the table below more carefully — Everywhere does more.

What maps to what

Fiddler	Solpuga
AutoResponder (Classic) / Rules (Everywhere)	Map Local
Breakpoints (`bpu`, `bpafter`)	Breakpoints
Inspectors	Request and response inspector
Statistics	Per-phase timing and body sizes
Decryption skip rules	Exclusion list
Export Sessions → HTTPArchive v1.2	HAR 1.2 export
Import Snapshot → `.har`	HAR import, read-only
Filters	Search and filters
WebSocket	Partly: messages recorded, none sent
FiddlerScript (Classic)	—
Composer	—
Replay	—
Reverse proxy	—
HTTP/2 (Everywhere)	—
Map Remote	—
Slow-network emulation	—
`.saz`	—

Carrying sessions over as HAR

.saz is readable only by Fiddler, so HAR is the bridge.

In Fiddler Classic. File → Export Sessions → All Sessions (or Selected Sessions) → format HTTPArchive v1.2.

Take v1.2, not v1.1: v1.1 cannot store non-textual response bodies. And know about Classic's second limit: a .har is not compressed, so by default it stores non-textual content only up to 32 kB. Larger images and files will not be in the export — that is the exporter's setting, not Solpuga's.

In Fiddler Everywhere. Export sessions as HAR from the File menu.

In Solpuga. Tools → import HAR (Cmd/Ctrl + Shift + I), or open the file from your file manager. A separate read-only window; a live capture keeps running. Files over 500 MB are refused.

What comes across

Headers, bodies, statuses, timings. The imported window uses the same inspector as a live capture: JSON as a tree, images with dimensions, binary as hex; the raw message and the bodies can be written to files.

What is lost

AutoResponder and Rules. HAR describes traffic, not settings. They get recreated; from a captured request the rule is filled in with the response that actually arrived.
FiddlerScript. Not in HAR, and nowhere to carry it to — see below.
Non-textual bodies over 32 kB — if the export came out of Classic with default settings.
WebSocket. HAR has nowhere to put it.
Double decompression. Bodies in Solpuga's HAR are decompressed while the response headers are kept as they arrived; an importer that trusts Content-Encoding will try again.

What you get instead

Coming from Classic: builds for macOS and Linux, not Windows only, and no restriction on commercial use.

An interface in English and Russian, and a free tier with no time limit.

Download for free