Hoverfly vs LocalStack

Hoverfly Cloud is a hosted API simulation and mocking platform for testing without live API dependencies. It handles HTTP/S services including REST, SOAP, XML, JSON, and GraphQL. Users can capture and replay traffic, generate simulations from OpenAPI specifications, and match requests by methods, headers, parameters, and bodies. Simulations can delay responses, inject faults or errors, and modify replies. A command-line interface supports scripted configuration and testing pipelines. Hoverfly and hoverctl binaries run on macOS, Linux, and Windows, while documentation covers Docker and Kubernetes installation. The underlying Hoverfly framework is open source under Apache 2, has no GUI, and is generally run locally or in a user’s infrastructure. Cloud use cases include performance testing, functional testing, and development.

LocalStack simulates cloud environments on customer infrastructure so developers and AI agents can validate applications before deployment. It currently emulates AWS and Snowflake, with AWS coverage described as 120+ services; an Azure public preview is coming soon. A typical workflow deploys application code and infrastructure-as-code resources into a local container, where teams can inspect failures and validate fixes before changing the endpoint to ship. LocalStack can run in GitHub Actions, GitLab CI, CircleCI, and Jenkins through a Docker image. The listed infrastructure-as-code tools include CDK, Terraform, and Pulumi. LocalStack is designed for development and testing, not production customer-facing applications. Hobby is free, offers 30+ emulated services and one personal sandbox, and is restricted to non-commercial use. AWS Base costs $39 a year, billed at $39 per license per month annually, or $45 per license per month billed monthly. LocalStack supports API, Linux, macOS, self-hosted, web, and Windows environments.