Operations | Monitoring | ITSM | DevOps | Cloud

Instant Java Client SDK, no spec required!

Learn how to generate a client SDK for a production service when you have no documentation, no OpenAPI spec, and no remaining team knowledge of the original Ruby code. This demo shows you how to capture real production data from a running app and transform it into a functional Java client library in minutes. Visit proxymock.io OR speedscale.com to learn more.

WireMock alternatives: pick the one that fits your problem

Picture this. You’re standing up a new service. Cursor or Claude Code wrote most of the controller, and it calls a payment API your team doesn’t own. Now you need tests. The agent is gamely inventing the response shape from whatever OpenAPI doc you fed it (which is a year stale), and the WireMock stubs it just generated are guesses dressed up as JSON. Three weeks later production breaks, the test suite was green the whole time, and nobody knows where to start looking.

From Traffic Context to Confirmed Fix in 3 Minutes

We’ve been building an AI agent that can take a production bug, find the root cause in captured traffic, write a fix, and validate it before a human reviews it. We call it Agent Factory. Last week we ran it on ourselves, against a real bug in our own production service. The first thing we did was get the workflow wrong.

Anatomy of the AI Software Factory: The Context Layer

This is Part 2 of the AI Software Factory series. In Part 1, we established that the Agile methodology is buckling under the weight of “elastic code.” When AI agents can generate functionality in seconds, two-week sprints and manual task management become organizational bottlenecks. We introduced the concept of the AI Software Factory: a shift from managing human tasks to managing business intent through a “Funnel of Increasing Trust.” But a factory requires infrastructure.