Systems | Development | Analytics | API | Testing

See how easily Konnect Metering & Billing transforms API and AI traffic management into new revenue streams. We've talked about why 2026 is the year of AI unit economics. There, we explored the "2025 hangover" where organizations realized that without financial governance, AI isn't just a science project but has become a margin-bleeding cost center. But "governance" and "monetization" shouldn't just be buzzwords in a resolution; they need to be part of your active infrastructure.

Today, we're excited to announce Kong Mesh 2.13. Kong Mesh 2.13 delivers full support for Mesh Identity for Kubernetes and Universal mode. Plus, it's been designated as a Long Term Support release, with support for a total of 2 years. But first, what's Kong Mesh for the uninitiated?

If you’ve recently upgraded to Debian 13 (“Trixie”) or a newer version of Ubuntu and suddenly started seeing security warnings when running apt update (or apt update --audit), don’t worry. You didn’t do anything wrong. This is a side effect of a broader security change across modern Linux distributions. SHA-1 signatures are being deprecated, and repositories that still rely on them may now trigger warnings or audits.

The recently released OWASP, “A Practical Guide for Securely Using Third-Party MCP Servers,” highlights a fundamental challenge in modern AI deployments: how do we govern, secure, and audit systems that are inherently non-deterministic? Unlike traditional, static software, AI agents dynamically adapt their execution paths, tool selection, and decisions based on context and real-time resources, allowing the same agent to achieve identical goals through entirely different approaches.

KAi, the AI assistant inside Kong Konnect, just got significantly more capable. Today, we're announcing an enhanced beta version powered by the new Kong Konnect MCP Server — a shared infrastructure layer that also opens up your API platform to IDE copilots and custom agents. The result? KAi can now do things it couldn't before, and those same capabilities are available wherever you work. If you've used KAi before, you'll notice the difference immediately.

AI agents are spreading across organizations rapidly. Each agent needs secure access to different Model Context Protocol (MCP) servers. Authentication becomes complex. Scaling creates bottlenecks. The dreaded "too many endpoints" problem emerges. You face a classic AI infrastructure headache. The numbers tell the story. Organizations using AI in at least one business function jumped from 55% to 78% in just one year. Generative AI usage specifically rose from 33% in 2023 to 71% in 2024.

If you’re an SAP customer, you’ve probably heard the same pitch more than once: just wait a little longer. Your migration to S/4HANA will unlock the agility you need. Your SAP Business Technology Platform (BTP) investments will catch up soon. Your workflows will get faster. Your data will become more accessible. Just a little more time. But what if you can’t wait? What if your supply chain teams are buried under manual work?

Start typing, change your mind, redirect the AI mid-response. It just works. That is the promise of realtime steering. Users expect to interrupt an answer, correct its direction, or inject new instructions on the fly without losing context or restarting the session. It feels simple, but delivering it requires low-latency control signals, reliable cancellation, and shared conversational state that survives disconnects and device switches.

Modern software systems are exposed to a constant stream of disclosed vulnerabilities. Thousands of new issues are published every year across operating systems, runtimes, libraries, and frameworks. Treating all of them as equally urgent is not realistic, and trying to do so often leads to ineffective security work. To manage this volume, the security community relies on two foundational mechanisms: CVE and CVSS.