Mock Service Worker vs Hoverfly

Free and open source

Free and open source

Free and open source. You pay in engineering time and CI minutes.

Free and open source. You pay in engineering time and CI minutes.

Everything, self-hosted

Everything, self-hosted

Category standard

OSS community · since 2020

Emerging

SpectoLabs · since 2016

• One set of handlers reused across unit, component, E2E and local development.
• Application code is completely unaware it is being mocked — no test-only branches.
• Supports REST and GraphQL with the same model.

• Capture mode produces a realistic simulation from live traffic with no authoring.
• Latency injection makes it useful for performance and resilience testing too.
• Small footprint — a single Go binary.

• JavaScript ecosystem only.
• Service Worker registration adds a setup step and occasional caching confusion.
• Handlers can drift from the real API without contract verification.

• Smaller community and slower development than WireMock.
• Proxy configuration in complex networks takes effort.
• Captured simulations need periodic refresh.

Front-end teams that want one mocking approach across every kind of test.

Teams needing lightweight service virtualisation against real recorded traffic.