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 Proxyman

A map of Proxyman's tools onto Solpuga's and carrying a session over as HAR: what travels, what is lost, and the limits.

What maps to what

Proxyman and Solpuga both run on macOS, Windows and Linux. Where there is no equivalent, the cell is a dash.

Proxyman	Solpuga
Map Local	Map Local
Breakpoint	Breakpoints
Export → as HAR	HAR 1.2 export
Opening a HAR by dragging it in	HAR import, read-only
The host tree	Grouping by host and application
The inspector	Request and response inspector
The timeline	Per-phase timing
Block List	Partly: the exclusion list only
WebSocket	Partly: messages recorded, none sent
Map Remote	—
Scripting (Rewrite)	—
Protobuf	—
Diff	—
External Proxying	—
No Caching, Clear Cache	—
HTTP/2	—
Command line	—

Carrying sessions over as HAR

Proxyman both writes and reads HAR; so does Solpuga. Proxyman's own Proxyman Log has nowhere to go.

In Proxyman. Right-click a request → Export → as HAR (HTTP Archive). For a whole session, the same through the File menu. On macOS 5.20 and later there is also a command-line export, with a choice of format and domain.

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

What comes across

Headers, bodies, statuses and timings — everything HAR 1.2 describes. The imported window uses the same inspector as a live capture, and bodies and raw messages can be written out to files.

What is lost

Rules. Map Local, Breakpoint, the lists — HAR describes traffic, not settings. Rules get recreated, fastest from a captured request, where the rule is filled in with the response that actually arrived.
Scripts. Scripting is not in HAR, and there is nowhere to carry it to — see below.
WebSocket. HAR has nowhere to put it.
Protobuf. The decoded view does not travel, and there is no decoder here: application/protobuf shows as a binary body in hex.
Double decompression. Bodies in Solpuga's HAR are decompressed while the response headers are kept as they arrived, so some importers try to decompress again. Garbage instead of text is that.

What you get instead

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

Download for free