Altair GraphQL Client vs OpenReq

Altair GraphQL Client is an IDE for running and debugging GraphQL queries, mutations and subscriptions. It formats queries, supports file uploads using the multipart specification, and can export query collections. Users can set environment variables for endpoints, headers and queries, then browse schema types and operations in a documentation explorer. Pre-request and post-request scripts and an extensible plugin system add customization options. Altair GraphQL Cloud provides centralized query management, collections, query versioning and shareable query URLs. Official integration packages include Express middleware, Koa middleware, a static build and a Gatsby plugin. The free Basic plan lists up to two team members and 20 queries; Pro costs $7.99 a month per user and lists unlimited team members, teams and queries. The client is available as a web app and on desktop platforms, including Linux, macOS and Windows, with extension and self-hosted options. The maker says the web app is for quick or one-time use, not full development, because it has limitations. Documentation warns that introspection can expose an API schema and that Content Security Policy support is beta.

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.