Proxyman on macOS: the capture toolbox, the cask install and the closed repository
The best-in-class HTTP Debugger for macOS. Capture HTTP/HTTPS from macOS, iOS, Android with a few clicks ✅
At a glance
- What is it?
- Proxyman is a Swift HTTP debugger for macOS that captures browser, iOS and Android traffic and then rewrites it with breakpoints, Map Local and scripting. Its GitHub repository holds a README and screenshots rather than source code, and the Windows platform named in that README has no download listed.
- Who is it for?
- Proxyman suits a macOS developer who wants a native debugger that captures browser and mobile traffic automatically, and who will pay for a licence rather than read one. It does not suit anyone who needs the Windows build, an audit of what the app does with captured traffic, or a self hosted copy, because the repository contains no code and the download section covers macOS only.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ProxymanApp/Proxyman7,045 ★ · +55
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| ProxymanApp/Proxyman | 7k | 7k |
55 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A cask install, then the app arranges its own capture
Proxyman installs as a Homebrew cask, and that is the one command the project's documentation gives:
brew install --cask proxymanA second route is a disk image, currently labelled Proxyman 26.4.0. The app needs macOS 13 or later, is built for macOS 26 Tahoe, and runs natively on Apple silicon from M1 through M4, written in Swift on top of Apple SwiftNIO. First use is not a command line exercise. The app sets up capture for web browsers on its own, and separate setup guidelines cover the iOS simulator plus real iOS and Android devices. For backend work there is automatic capture of HTTP(S) traffic from NodeJS, Ruby and Python, which is the shortest path from install to a first captured request. A command palette opens requests, responses and scripts from the keyboard, so filtering a long capture does not mean clicking through rows.
The GitHub repository holds four entries, none of them code
Before planning anything around the GitHub repository, look at what is in it. There are four top level entries: .github/, .gitignore, README.md and screenshots/. No source tree, no build script, no LICENSE file, and no primary language recorded for the project. Proxyman is a product whose internals cannot be read from the place developers look first, and that has direct consequences. You cannot audit what happens to captured traffic, you cannot build your own copy, and you cannot point a security review at anything reviewable, because nothing reviewable lives there. Support is routed elsewhere: a GitHub ticket, a Discord server for technical issues, and the email addresses [email protected] and [email protected]. The version history, by contrast, is kept properly, with dated releases published on that same repository.
Version numbers jumped from 6.17.0 to 26.0.0, and HTTP/2 needed a hotfix
The release sequence shows a fast cadence. Version 26.2.0 arrived on 2026-10-18 with an Overview Dashboard, a redesigned Timing View and Script Templates. On 2026-10-26 came 26.3.0, titled as blazing fast with 100,000 requests and blocking the compromised eMudhra CA. Then on 2026-11-02, 26.4.0 added 27 new MCP tools that let AI agents control Proxyman. With releases about a week apart, pin the exact build you tested rather than tracking the newest one, and read the full changelog before upgrading. The default branch was last pushed on 2026-10-26, the same day as 26.3.0.
Map Local, Breakpoint and the rest of the rewriting box
The feature list is where Proxyman spends its effort, and it is long. At the basic end sit Compose, Repeat, wildcard and regex filters, multiple filters, customisable columns and a toolbar you can rearrange. The advanced list runs from Breakpoint, Map Local and Map Remote through Blocklist, External Proxying, No Caching, Protobuf, Clear Cache, Custom Certificates, Scripting, Network Conditions, Reverse Proxy, Diff, Access Control and DNS Spoofing. That range tells you the intended user: someone reproducing a request and then forcing a different answer back. One honest gap sits underneath the list. Every tool is named without any explanation of what it changes, and there are no stated limits, so the behaviour of any individual feature has to be established by trying it rather than by reading it.
Two mobile products, and the phone one is the smaller
Mobile capture is split across two products, and they are not equal. On macOS the app captures HTTP and HTTPS plus WebSocket traffic from web browsers, iOS and Android devices with a few clicks, with setup guidelines provided for the iOS simulator and for real devices. Separately, Proxyman for iOS is a native iOS app that captures HTTPS traffic from an iOS device directly, with no MacBook needed, and it is distributed through the App Store. Its stated feature set is narrower: Block List, Map Local and Breakpoint are the ones called ready. A tester should not assume the rest of the desktop toolbox is available on a phone, since the README calls only those three ready.
Team Workspace puts HAR files online behind three roles
Sharing is a subscription feature rather than a local one. Under Proxyman Team Workspace, described as available to Team Subscription only, you sign in to manage the workspace account and activate the PRO licence, then share Proxyman logs or HAR files with your team and review them online. Access is role based, with three named roles, Admin, Developers and Public, behind secure authentication. The consequence for an engineer is that a shared capture stops being a file on the laptop. Once a request log enters the workspace it is reviewed through a browser by someone whose role you have to think about, and a HAR file is the kind of artefact that carries tokens and cookies with it. Whether that trade suits a team is a decision about your own traffic rather than about Proxyman.
Windows is named in prose, and no licence file ships either
Two gaps deserve a decision before anyone buys. The first is Windows. The closing note says the team is dedicated to shipping Proxyman tailored for each platform, macOS, iOS and Windows, yet the download section offers a macOS disk image and a macOS Homebrew cask, and the repository contains nothing that builds or documents a Windows version. Read that sentence as a direction of travel rather than as a download. The second gap is licensing. The repository has no LICENSE file and the project metadata records no licence, so the terms you would be agreeing to are not published where developers normally look. The README asks you to purchase a licence to support a small engineering team, and routes anything shared through the Team Subscription. Settle the terms with the vendor directly, and keep the receipt with your procurement records.
Editorial conclusion
Proxyman suits a macOS developer who wants a native debugger that captures browser and mobile traffic automatically, and who will pay for a licence rather than read one. It does not suit anyone who needs the Windows build, an audit of what the app does with captured traffic, or a self hosted copy, because the repository contains no code and the download section covers macOS only. Before buying, install the cask on your own macOS version and confirm the app launches, read the full changelog on the releases page for the build you install, and settle the licence terms with the vendor directly, since no LICENSE file sits in the repository.
Frequently asked questions
How much does Proxyman cost?
The README lists no prices. What it does say is that Proxyman is developed by a small engineering team and asks buyers to purchase a licence to support the work, and that the Team Workspace features are available to Team Subscription only.
What are the key differences between Proxyman and Charles Proxy?
The README makes no comparison with Charles Proxy. It describes Proxyman as a native macOS app written in Swift, powered by Apple SwiftNIO, requiring macOS 13 or later, with tools including Breakpoint, Map Local, Map Remote, Scripting and Network Conditions.
Is Proxyman safe to use?
The README makes no security claim. The two statements closest to one are that the app can install custom certificates, and that Team Workspace shares logs and HAR files online with role based access control for Admin, Developers and Public roles.
How do I install Proxyman?
Homebrew installs it as a cask with brew install --cask proxyman. A disk image download is also offered, currently labelled Proxyman 26.4.0, and the app requires macOS 13 or later and runs on Apple silicon.
How do I use Proxyman with the iOS simulator?
The README points to setup guidelines for the iOS simulator and for iOS and Android devices instead of listing the steps itself. It also notes a separate native iOS app that captures HTTPS traffic from an iOS device with no MacBook needed.
What is a free alternative to Proxyman?
The README names no alternative product. It says Proxyman is built by a small engineering team, that the macOS build is offered as a Homebrew cask and a disk image, and that purchasing a licence supports the development.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/proxymanapp-proxyman)Star history chart for your README
[](https://hysenlabs.com/projects/proxymanapp-proxyman)Was this useful?