When teams resort to VPC peering or PrivateLink to expose Kafka, they're not solving the problem — they're managing it, one network topology decision at a time. Every new external consumer adds complexity: a new peering connection, new firewall rules, new IP space to coordinate, new potential for…
Agents are ultimately decision makers. They make those decisions by combining intelligence with context, ultimately meaning they are only ever as useful as the context they can access. An agent that can't check inventory levels, look up customer history, or verify pricing isn't autonomous — it's…
With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode. When using Kong Ingress Controller with Kubernetes Gateway API, Kubernetes serves as the authoritative source of…
Kong is excited to announce Solace as the newest member of our Premium Technology Partner Program, a program designed to deliver high-quality, reliable integrations that provide real business value for customers. Together, Kong and Solace unify API-driven and real-time data movement into a single,…
Stay ahead of API and AI Gateway trends. Get expert insights, technical guides, and best practices delivered to your inbox.
In today's digital landscape, APIs are the backbone of modern applications, and AI is the engine of innovation. As organizations increasingly rely on microservices and AI-powered features, the API gateway has become the critical control point for managing traffic. But as LLM/GenAI and MCP requests…
The goal of Integration Platform as a Service (iPaaS) is to simplify how companies connect their applications and data. The promise for the first wave of iPaaS platforms like Mulesoft and Boomi was straightforward: a central platform where APIs, systems, and workflows could be managed together…
MCP servers expose all tools by default. There are two problems with this: security (agents get capabilities they shouldn't have) and performance (too many tools degrade LLM tool selection). The solution? Put a gateway between agents and MCP servers that filters tools based on who's asking. Default…
This is the pitch to the board and the C-suite. It must be brutally concise, focused entirely on your business outcomes, not the technology. If the first page doesn't articulate value, the strategy dies. It immediately frames the initiative in terms of shareholder value and competitive advantage.…
AI spending is exploding across the organization—but often not in the ways leadership approved or finance can track. Development teams spin up LLM connections to ship features faster. Data teams provision GPU clusters for experiments that get abandoned. Multiple teams solve the same problem three…
Let's be honest about what's happening inside most enterprises right now. Development teams are under intense pressure to ship AI features. The mandate from leadership is clear: move fast. And so they do. They spin up LLM connections, integrate third-party AI tools, and route data to models without…
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…
The report identifies a mindset trap that's holding most organizations back: "inside-out" integration thinking. Inside-out means viewing integration from the perspective of only prioritizing the reuse of legacy integrations and architecture (i.e., simply wrapping existing integrations with MCP and…
The first pillar is enablement. Developers need tools that reduce friction when building AI-powered applications and agents. This means providing: The goal isn't to replace existing development workflows but to extend them. Developers should be able to build agents using familiar paradigms while…
Explore our documentation, tutorials, and implementation guides to accelerate your API and AI Gateway projects.
The Kong MCP Registry acts as a central directory for AI agents and clients to access services that provide context or take action. For AI agents, think of it as a combination of a "Service Catalog" and a "Developer Portal." It offers the metadata, API endpoints, and capability definitions that…
The example below shows how an AI agent can be built using Volcano SDK with minimal code, while still interacting with backend services in a controlled way. The agent is created by first configuring an LLM, then defining an MCP (Model Context Protocol) endpoint that represents a promotions service.…
The evolution of AI agents and autonomous systems has created new challenges for enterprise organizations. While securing API endpoints is well-understood, controlling access to individual AI agent tools presents a unique authorization problem. Today, we're excited to announce a powerful solution…
In one of our posts, Kong AI/MCP Gateway and Kong MCP Server technical breakdown, we described the new capabilities added to Kong AI Gateway to support MCP (Model Context Protocol). The post focused exclusively on consuming MCP server and MCP tools through Kong MCP Gateway. Now, it's time to check…
Secure your AI infrastructure with prompt guards, PII sanitization, and centralized governance. Control LLM costs with token-based rate limiting and semantic routing across providers.