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.
Posts about developer tools
Browse 51 posts in this category
Your AI agent is fixing the wrong service
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%.
The Kubeshark Workflow That Doesn't Stop at the Dashboard
A Kubeshark alternative that goes beyond observability. Stream live cluster traffic into proxymock, then replay or mock it locally from your laptop.
WireMock alternatives: pick the one that fits your problem
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.
Anatomy of the AI Software Factory: The Context Layer
Explore the technical architecture of the AI Software Factory, focusing on tool convergence and the Unified Context Layer.
Conway's Law 2.0: The VP's Playbook
Learn how VPs of Engineering must adapt org charts, engineering roles, and performance metrics to lead in the era of the AI Software Factory.
Agile is dead. AI is the culprit.
Discover why AI coding agents are breaking Agile workflows and driving the shift to an intent-based AI Software Factory.
From Traffic Context to Confirmed Fix in 3 Minutes
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.
The DIY Traffic Replay Trap: Why AI Scripts Fail at Scale
AI-generated scripts seem like a quick win, but DIY traffic replay tools become a maintenance nightmare at scale. Here's why Speedscale beats the prompt.