Systems | Development | Analytics | API | Testing

We've been getting a lot of questions about how Rovo works with Zephyr, so Matt Bonner gives a quick look at a few of the capabilities teams are finding most valuable: Test case generation Test coverage insights Release Risk Analyzer.

Kong's AI Gateway applies the same architectural pattern as the API Gateway — now governing LLM, MCP, and agent traffic at the infrastructure layer. Just as API gateways abstracted rate limiting, auth, and caching across microservices, AI gateways do the same for large language models and agents — with token budgets, semantic caching, and semantic routing replacing their REST equivalents. Kong breaks this into three layers: LLM Gateway, MCP Gateway for tool calls, and Agents Gateway for agent-to-agent traffic.#Shorts.

Visit: speedscale.com/proxymock.

What did Atlassian Team ’26 reveal about the future of software quality and AI-powered delivery? In this recap from the event floor inside the Anaheim Convention Center, SmartBear shares key themes from the event, including Atlassian Rovo, the Teamwork Graph, AI-driven workflows, and how QA teams are adapting to faster, AI-assisted software delivery inside Jira. See quick highlights from the event floor, SmartBear’s latest Zephyr innovations, and how conversational AI and quality intelligence are becoming part of the modern software delivery workflow.

Most AI revenue will flow through tokens — and the two bottlenecks are tokens per watt (energy cost) and tokens per second (throughput). Tokens per watt determines how much output you can generate from a fixed energy supply — already constrained and getting tighter. Tokens per second sets the ceiling on how fast that revenue can flow. Kong's AI Gateway optimizes both at the connectivity layer: semantic caching and semantic routing increase token output without adding watts or latency.#Shorts.

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.

LLMs are absorbing the business logic of microservices for agentic use cases — but both patterns will coexist in enterprise infrastructure for a long time. Cloud-native infrastructure (microservices + APIs) keeps powering web and mobile experiences. The agentic layer — LLMs, MCP tool calls, and context traffic — runs in parallel, activating the same APIs and CRUD operations underneath. Kong manages both swim lanes: the API traffic between clients and microservices, and the context traffic flowing between agents and LLMs.#Shorts.