Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Bruno | Hurl | D2 |
|---|---|---|---|
| Platforms | Universal | Universal | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | Apache-2.0 | MPL-2.0 |
| Stars | 47971 | 19292 | 25774 |
| Last activity | October 30, 2026 | October 17, 2026 | October 11, 2026 |
| Install complexity | EASY | Easy; API and CLI knowledge required | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. |
| Category | Testing, Git | Testing, DevOps | Workflow, UI |
| Best use | Ideal for a solo developer or small team that wants API collections and tests beside the code with Git review. Use it for repeatable REST, GraphQL, gRPC, and WebSocket checks—not live cloud collaboration or load testing. | Best for a developer or small team that wants repeatable API checks with explicit conditions stored beside the code. It links request data and identifies failing assertions without repeating manual inspection. It does not replace browser tests or test-environment setup; curl may be enough for a one-off request. | For developers and small teams that want architecture and data-flow diagrams close to the repository and reviewable as text. Use it when relationships matter more than pixel-perfect placement; not for free-form marketing design or exact manual positioning. |