Build WireMock mappings fast from real traffic
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Co-founder and CEO of Speedscale, passionate about performance engineering. • 9 posts published
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.
MSA clauses and contractual guarantees aren't an architecture. If your production traffic leaves your cloud, you're trusting a policy, not a system.
Capture production traffic and store it in your own Elasticsearch with Speedscale BYOC. Pull it locally with es-gather.py and reproduce bugs with proxymock.
I tested 100 bugs across 240 microservices the model has never seen. Alert only: 51% pass rate, wrong service 34% of the time. Traffic captures: 77%.
A 2026 take on WireMock alternatives. Keep WireMock for what it's good at; add Microcks (now CNCF Incubating) or proxymock for the gaps. The honest map.
Traffic Context is the missing piece in most debugging workflows. We ran our autonomous agent on a real production bug — it found the root cause, wrote a reproduce harness, applied the fix, and confirmed it. Here's what that looked like.
AI coding adoption is high and trust is dropping. A testing pyramid for agents, plus reproducible production context that grounds AI in real behavior.
Choose the desktop proxymock or the hosted cloud trial to get started.