Hoppscotch vs OpenReq

Hoppscotch is a collaborative, open-source platform for creating, testing, documenting and sharing APIs. Its client supports HTTP, GraphQL, WebSocket, Socket.IO, MQTT and Server-Sent Events. Testing tools include pre-request scripts, post-request tests, environment variables, request history and collection runners. Teams can use shared workspaces, access-level roles and real-time collaboration, and the platform can be deployed on their own servers. Users can migrate from Postman, Insomnia and cURL, then generate code snippets in various languages and frameworks. Hoppscotch describes its data storage as local-first and says it has no tracking, analytics or ads. The free plan includes REST, GraphQL and realtime API testing, a personal workspace, collections and environments, scripts and tests, a collection runner and community support. Organization is $6 a month when billed annually. Business is $6 per user/month billed annually, while Enterprise is $11 per user/month billed annually. Enterprise includes identity and access management, audit logs and priority Slack Connect support. Hoppscotch supports more than 30 languages and is listed for API, Linux, macOS, self-hosted, web and Windows.

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.