Reqable pairs a MITM proxy with an API client, and it is not open source
Reqable issue track repo
At a glance
- What is it?
- Reqable is a closed-source API debugging and testing tool for five platforms that merges traffic capture and request composition into one Flutter and C++ client. The GitHub repository is an issue tracker, not the code.
- Who is it for?
- Reqable suits developers and QA engineers who want capture and testing in one window and who are comfortable installing closed-source binaries and, on desktop, granting a system proxy and trusting its certificate authority. It does not suit anyone who needs to audit the implementation, build it themselves, or script gRPC today, since gRPC is marked coming soon.
- 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 3 days 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
- reqable/reqable-app6,960 ★ · +183
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| reqable/reqable-app | 6.8k | 7k |
183 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The GitHub repository holds issues, not source
The first thing to settle is what this repository is. The README opens with a warning that Reqable is not an open-source project and that this repository is used solely for issue tracking, feature requests, and user feedback.
That single line reframes everything else. There is no build from source, no code to audit, and no licence file in the tree. The top level holds nine READMEs (English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish, French, German, Russian), an arts directory, and a .github directory. No source directory, no manifest, no test suite.
So this is where you file a bug, not where you get the product. The releases published here are version-numbered and dated (3.3.9 on 2026-10-30, 3.3.8 on 2026-10-28, 3.3.7 on 2026-10-28), which makes it easy to assume you can install a build from here. The installation table instead points to downloads on app.reqable.com and the app stores. The repository description says it plainly, an issue track repo.
For an engineer deciding whether to adopt a traffic interceptor, that distinction is not a footnote. It decides whether your security review can read the code that handles every request on the machine.
Capture is MITM everywhere, but the transport differs by platform
The interception strategy is the classic man-in-the-middle approach to HTTP(S), and it is the same everywhere; only the plumbing changes.
On desktop platforms, Reqable captures traffic through system-level proxy configuration. On mobile, it uses a local VPN. That second choice matters more than it sounds: a local VPN on a phone has to be granted a permission Android and iOS treat as sensitive, so the mobile path asks for more from the user than the desktop one.
Once traffic is captured, the debugging primitives are the usual set: request replay, inline editing, breakpoints, URL rewriting, and custom scripting. Replay and inline editing are table stakes for any interceptor; breakpoints, rewriting and scripting are the parts that turn a passive viewer into a test harness, and they are also the parts with the most ways to get a request wrong.
Those primitives are desktop and mobile, with one carve-out stated further down: breakpoint, rewrite, and scripting features are currently unavailable on mobile platforms due to platform-level security policies. So the mobile app inspects, and the desktop app manipulates.
The client covers HTTP, WebSocket, SSE and a pending gRPC
The testing half of Reqable is a full API client rather than a capture viewer with a replay button. It composes, sends and organises HTTP, WebSocket, SSE, and gRPC requests, with gRPC marked as coming soon.
That parenthetical is the honest limit of the protocol coverage today. HTTP, WebSocket and server-sent events are real; gRPC is a promise. Anyone whose service surface is gRPC-heavy should treat the client as incomplete rather than assume parity.
Around the request editor, the features are the ones that decide whether a team can live in the tool daily. API collections with folder-based organisation keep a large surface navigable. Environment variables with scoped resolution let the same request run against different targets without editing URLs by hand. Built-in API documentation authoring means the documentation lives next to the traffic that produced it, and cloud synchronisation carries collections across devices.
Cloud sync is also the one place where the login-free architecture gives ground, and the README is candid about it: with an optional account login, synchronisation can be enabled. Login-free is the default state, not a permanent property.
Five platforms, four version floors, and no Linux build for ARM
Installation is a table of twelve rows, and the constraints live in the Notes column rather than the download links.
Windows comes as an installer or a portable zip, both x86_64, both supporting Windows 7 and later. macOS offers a universal build through Homebrew plus separate Intel and Apple Silicon dmg files, each requiring macOS 11.0 or later. Linux is x86_64 only, as either a deb or an AppImage, supporting Ubuntu, Debian and other distributions and requiring GTK 3.0. Android is on Google Play plus three apk architectures (arm64-v8a, armeabi-v7a, x86_64) at Android 5.0 or later. iOS is arm64 from the App Store at iOS 13.0 or later.
Two gaps are visible without inference. There is no Linux ARM build, which matters on Apple Silicon Linux machines and on ARM servers. And the macOS floor is much higher than the Android one, so an old macOS host is out regardless of how old the Android requirement is.
The macOS row is the only one with a package manager entry, and it is the shortest install of the set:
brew install reqableLinux users get no such convenience from the project; they pick between two file formats and install GTK 3.0 themselves.
Flutter and C++ replace an embedded browser runtime
The stated architectural decision is that Reqable is engineered with Flutter and C++ and deliberately avoids an embedded browser runtime.
The claimed benefit is twofold. Avoiding a browser runtime reduces the attack surface, which is a reasonable argument for a tool that sits on every request your machine makes. And the same choice is said to yield performance gains over Electron-based alternatives.
The numbers attached to that claim are specific: millisecond-level cold-start time, an installation footprint under 100 MB, and typical memory consumption under 300 MB during active use. The benchmark sections are labelled as benchmarks, with the caveat that they were conducted on an Apple MacBook Pro with the M5 chip, and the README asserts that on lower-specification hardware the performance delta is more pronounced.
Treat that as a claim from the vendor about its own product, published without the raw numbers in this repository. The same reasoning that made the README say this repository is for issue tracking applies to the benchmarks: you cannot reproduce them from here.
The MCP server is the one open-source piece, in another repository
Reqable ships with a built-in MCP server, which lets AI assistants such as Claude and GitHub Copilot interact with it directly. The stated uses are AI-driven workflows for API debugging, traffic inspection, rule authoring, and automated testing.
The interesting part is where the openness sits. The MCP server implementation is fully open source, in a separate repository (reqable/reqable-mcp-server), while the application that hosts it is not. So the bridge to assistants is auditable and the thing being bridged is not.
That split has a practical consequence for anyone writing automation. If your interest is letting an assistant inspect traffic and propose rules, the open repository is where the contract lives. If your interest is changing how Reqable itself behaves, you are reading release notes and filing issues, not contributing code.
Free tier, premium tier, and what the README does not price
The commercial structure is described in two sentences: the majority of features are free of charge with no trial period, the Community edition covers the needs of most individual developers, and power users and teams may benefit from upgrading to Premium.
Notice the care in the wording. Most, not all. Covers the needs of most, not all. May benefit from, not should buy. No price is stated anywhere in this repository, and no feature-by-feature comparison between Community and Premium appears either. Both live on reqable.com, alongside the documentation at the docs introduction page.
For an engineer evaluating this, that means the licensing question cannot be answered from the source you have. You are being asked to make a decision on two paragraphs of hedged prose plus a website.
The acknowledgements section, meanwhile, is a list of GitHub users with issue counts, which tells you something about where the feedback has come from but nothing about the product.
The other commercial detail worth knowing before a rollout is what login-free actually costs you. Without an account you keep the traffic on the machine and skip the synchronisation that carries collections between a desktop and a phone. With an account you get that replication and give up the login-free property. Neither choice is documented here in terms of what synchronisation stores, so the decision belongs with whoever owns the data policy rather than with the engineer doing the install.
Editorial conclusion
Reqable suits developers and QA engineers who want capture and testing in one window and who are comfortable installing closed-source binaries and, on desktop, granting a system proxy and trusting its certificate authority. It does not suit anyone who needs to audit the implementation, build it themselves, or script gRPC today, since gRPC is marked coming soon. Before installing, check whether your organisation permits a closed-source traffic interceptor on the machine, confirm your platform version clears the stated floor, and read the licensing and pricing pages on reqable.com for the split between the free Community edition and Premium.
Frequently asked questions
What is Reqable?
Reqable is a next-generation, all-in-one API debugging and testing platform supporting Windows, macOS, Linux, Android and iOS. It combines an API traffic capture tool with a full-featured API testing client in one environment, so capture-and-test workflows replace several standalone tools.
Is Reqable open source?
No. The README states that Reqable is not an open-source project and that this GitHub repository is used solely for issue tracking, feature requests, and user feedback. The one open-source piece is the separate MCP server repository, reqable/reqable-mcp-server.
How does Reqable capture traffic on desktop and mobile?
On desktop platforms Reqable captures HTTP(S) traffic via system-level proxy configuration, and on mobile it leverages a local VPN. Captured traffic can then be replayed, edited inline, breakpointed, rewritten, or scripted.
Which platforms can I install Reqable on?
Windows x86_64 (installer or portable zip, Windows 7+), macOS universal or Intel or Apple Silicon (macOS 11.0+, or brew install reqable), Linux x86_64 as deb or AppImage requiring GTK 3.0, Android 5.0+ via Google Play or apk, and iOS 13.0+ from the App Store.
Does Reqable support gRPC requests yet?
Not yet. The API client composes and sends HTTP, WebSocket, SSE, and gRPC requests, with gRPC explicitly marked as coming soon. Breakpoint, rewrite and scripting features are also unavailable on mobile platforms due to platform-level security policies.
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/reqable-reqable-app)Star history chart for your README
[](https://hysenlabs.com/projects/reqable-reqable-app)Was this useful?