Systems | Development | Analytics | API | Testing

Modern Kafka deployments struggle with a familiar tension. You want fine-grained access control per client, per team, and even per request. However, traditional ACLs force you into static, cluster-level configurations that are brittle, hard to scale, and painful to maintain. Administrators are often forced to manage massive, hardcoded lists of topics and users. But what if you could dynamically craft these ACLs using identity context?

Scaling LLM and agentic AI adoption from pilot programs to enterprise-wide deployments is a massive logistical rollout. As AI and agentic usage grow, so does a nagging question for leadership: **Are agents using the right tools to get the job done?** While raw infrastructure metrics might tell you if a server is "up," they fail to tell you if your AI investment is being leveraged.

Insomnia natively understands Postman's export format and can bring over your collections, environments, folder structures, and even pre-request scripts with most of the conversion handled automatically..

Digital agreements are at the heart of many critical business processes. As companies modernize their technology stacks and adopt API-driven architectures, integrating agreement workflows directly into applications has become increasingly important. Traditional agreement processes were slow and heavily manual. Documents were often created in office tools, shared through email, printed, signed physically, and stored across multiple systems.

How OAuth 2.0 Token Exchange Reshapes Trust Between Services — and Why the API Gateway Is Exactly the Right Place to Enforce It OAuth 2.0 Token Exchange fundamentally alters how services establish trust. And the API gateway is the ideal location to enforce this new model. Modern applications don’t run as a single monolithic.

How Kong Gateway 3.14 closes the consistency gap in IAM-based authentication across AWS, Azure and GCP — and what it means for your production deployments Enterprise security teams have clear requirements: no static credentials, no exceptions. Every service-to-service connection, whether it's Kong talking to databases, caches, or vaults, should authenticate using the same IAM-based identity model that governs the rest of their cloud infrastructure.

Modern API architectures are no longer linear. A single request can traverse multiple layers of authentication, transformation, enrichment, and observability. As these flows grow more dynamic, the need for fine-grained control over when plugins execute becomes critical. For years, the standard approach to API Gateway configuration followed a strict hierarchical model: you applied a plugin to a Service, a Route, or a Consumer.

The shift from single-model AI features to multi-agent pipelines is no longer a future concern — it's running in production today. MCP has become the de facto protocol for tool-calling, agent-to-agent (A2A) communication patterns are proliferating, and enterprise teams are wiring together complex AI workflows that span multiple providers, services, and agents. Every hop in that data path is an opportunity for something to go wrong. The challenge is governance.

Kong Agent Gateway Is Here — And It Completes the AI Data Path You had a request going to a model, a response coming back, and a gateway in between to enforce policy. With the right solutions, this becomes manageable pretty quickly.. That world is over. Today's agentic architectures look nothing like that. Agents are delegating tasks to other agents via A2A. These other agents are producing and consuming event streams.

You whipped up a simple MCP server prototype over the weekend. It routed a single AI agent to a few internal tools, your demo impressed leadership, and the team asked the dreaded question: "When can we ship?" You smiled and said, "Give me two weeks." Fast-forward three months**.** You’re firefighting expired tokens at 2 AM. The compliance team is camped in your inbox. Your once-elegant codebase is now a distributed systems nightmare. Sound familiar?