developer tools, APIs and code utilities
Shortlists of developer tools and APIs
Codehurst publishes shortlists of developer tools, APIs and code utilities, written from each project's or vendor's official documentation. Our guides shortlist tools for a specific job or team, compare them side by side and explain the order in plain words — built only from what vendors document, with the check date on every page.
Latest guides
- Top 6 API client tools for keeping collections in Git and working offlineIf you want API request collections to live in your repository as diffable files and keep working without a cloud account, start with Bruno, Yaak and Hoppscotch.
- Top 5 open-source API gateway tools for Kubernetes microservicesFor platform teams running microservices on Kubernetes who want a self-managed, open-source gateway, Apache APISIX, Kong Gateway and KrakenD are the closest documented fits.
- Top 5 end-to-end testing tools for reliable browser tests in CIIf you are fighting flaky browser tests in CI, start with Playwright, Cypress and Selenium.
Categories
- API clients and testingTools for building, sending and testing API requests. · 1 guide
- API gateways and managementGateways, API management and developer portals. · 1 guide
- Testing frameworksUnit, integration and end-to-end testing tools. · 1 guide
- Code editors and IDEsEditors and integrated development environments.
- Version control and code hostingGit hosting, code review and repository tools.
- Logging and observabilityError tracking, logs, metrics and tracing for developers.
- Developer databasesDatabases and data platforms built for application developers.
- Package and dependency toolsPackage managers, registries and dependency tooling.
- API documentation toolsTools to write and publish API reference docs.
- Terminals and CLI toolsTerminal emulators and command-line utilities.
How Codehurst works
Each guide answers one question — which tools fit a particular job or team — and lists 5 to 12 options with what each is for, its documented key features and its documented limits. We read each vendor's official website and documentation, record what it states, and write only from those notes. The order is editorial fit for the use case, explained in words; we publish no stars, scores, ratings or reviews, and vendors cannot pay for a place.
Prices change often, so we point to each vendor's pricing page instead of quoting numbers. Spotted something out of date? Tell us and we will check it against the vendor's documentation.