What it does
Hoverfly is a command-line API simulation framework for development and testing. It can capture requests and responses into reusable simulation data, then return those recorded responses to clients in simulate mode instead of forwarding calls to the real API. This gives a test or local development environment a way to replace slow, unavailable, or unpredictable dependencies. The project consists of the Hoverfly runtime and the hoverctl command-line controller and has no graphical interface.
Record a dependency, then replay it
A typical documented workflow is to install both Hoverfly binaries, start the proxy, capture a request through it, and export the resulting simulation file. Later, start Hoverfly in simulate mode and import that file so a test client receives the saved response without reaching the real external API. The tutorial illustrates the exchange with a sample HTTP request; the commands are documentation examples. The simulation file can be edited, reused, or shared, and the official repository lists a REST API and language bindings. This makes Hoverfly useful when an integration test needs repeatable responses or when a team wants to explore error cases without repeatedly depending on a third-party service. The basic setup is operational rather than visual: users install hoverfly and hoverctl, start the local service, and route the test client through the proxy or call the simulation server. This entry covers the open-source self-hosted framework, which the official repository licenses under Apache 2.0. Hoverfly Cloud is a separate hosted product built on top of it. The local framework has no GUI, and the pages reviewed do not establish pricing or account terms for that self-hosted tool.
Strengths
- Capture and simulate modes let teams save API interactions and replay them without contacting the live dependency.
- The official repository documents a REST API and native language bindings in addition to the CLI.
- Simulation data can be reused to exercise external-service behavior consistently across development and testing.
Watch out for
- The open-source tool has no graphical interface and uses separate Hoverfly and hoverctl binaries.
- A test client must be routed through the proxy or use the simulation server, so the workflow requires client or environment configuration.
Best for
- Integration tests that need stable responses from external HTTP APIs
- Developers replacing unavailable services during local development
- Teams simulating recorded API responses rather than consuming live service quotas
Sources
- Hoverfly open source API simulation from Hoverfly Cloud (Oct 25, 2026)
- Getting Started: Hoverfly v1.12.16 documentation (Oct 25, 2026)
- Simulate mode: Hoverfly v1.12.16 documentation (Oct 25, 2026)
- Running Hoverfly as a webserver: Hoverfly v1.12.16 documentation (Oct 25, 2026)
- SpectoLabs/hoverfly: API simulations for development and testing (Oct 25, 2026)
- Apache License, Version 2.0 (Oct 25, 2026)