Logs told me something broke. Traffic showed me what.
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.
Co-founder and CEO of Speedscale, passionate about performance engineering. • 9 posts published
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.
Learn a practical workflow to convert Datadog metrics, traces, and incidents into CI tests that catch regressions before deploy.
LLMs have collapsed the cost of custom internal tools. Here's the startup distribution problem I've watched kill companies — and how I vibe-coded my way out.
Record real LLM traffic from a FastAPI app, mock it locally, and replay it in CI with proxymock.
Production AI spend gets attention. Non-prod LLM calls in development, CI, and load tests often do not. Simulation fixes that.
Choose the desktop proxymock or the hosted cloud trial to get started.