OpenReq vs Requestly
OpenReq
openreq.app
Requestly
requestly.comSide by side
| Figure | OpenReq | Requestly |
|---|---|---|
| Price from | Free | $10/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 4 |
| Spec score · API clients | 8.7 (#12) | 8.9 (#8) |
| API documentation | Yes | Yes |
| Automated test runs | Yes | Yes |
| Free plan | Yes | No |
| GraphQL support | Yes | Yes |
| gRPC support | No | Yes |
| Integrations | Integrates with Ollama, Postman, OpenAPI, raw cURL, Chrome, and Electron. | Two-way synchronization is available with GitHub and GitLab. |
| Available platforms | web_and_desktop | Available for macOS, Windows, and Linux. |
| Pricing Model | Free and open source with no subscription tiers. | Flat per-user pricing with no hidden add-ons. |
| Team Workspaces | The server-connected client is intended for teams and shared workspaces. | Yes |
| WebSocket support | Yes | Yes |
Plans
Requestly
- Team$10 a month
- Team Pro$15 a month
- EnterprisePriced on request
- 30-day trialFree
In their own words
OpenReq
OpenReq is a free, community-driven API testing application released under the MIT License. It runs as a self-hosted web application, a standalone desktop application, and a Windows client. HTTP, WebSocket, and GraphQL requests are supported as first-class request types, with visual test flows, collection runs, assertions, scripts, delays, conditions, loops, and reports. Automated test runs and API documentation are included, and API testing has no stated usage limits. Collections can become read-only public documentation links, optionally protected by passwords; viewers do not need accounts. OpenReq generates request code for cURL, Python, JavaScript, Go, Java, C#, and PHP. Integrations include Ollama, Postman, OpenAPI, raw cURL, Chrome, and Electron. Ollama can provide local AI features without a cloud API key or sending data away from the machine. The Windows desktop client is frontend-only and needs a separately hosted backend. Most endpoints use JWT bearer authentication, while local proxy setup uses HMAC-signed tokens.