Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | Hurl | Lychee |
|---|---|---|---|
| Platforms | Universal | Universal | Universal |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | Apache-2.0 | MIT OR Apache-2.0 |
| Stars | 25761 | 19288 | 4065 |
| Last activity | October 11, 2026 | October 17, 2026 | October 26, 2026 |
| Install complexity | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. | Easy; API and CLI knowledge required | — |
| Category | Workflow, UI | Testing, DevOps | Testing, Workflow |
| Best use | 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. | 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 documentation authors and small teams checking references locally or in CI. Start with a specific file and interpret findings; it does not establish complete site or login functionality. |