Systems | Development | Analytics | API | Testing

We have big news for platform and AI infra teams: *Kong AI Gateway 2.0 is available today in private beta*. It runs on its own dedicated runtime, ships on its own release cadence, and carries a completely reimagined user experience designed around the way teams actually build with AI: models, MCP servers, and agents as first-class citizens, not plugins bolted onto an API gateway.

We're thrilled to announce a strategic technology partnership between **Kong** and **ModelOp**. As enterprises rapidly transition into the agentic era, they face a critical challenge: how to deploy AI fast enough to stay competitive without taking on unacceptable regulatory or security risks. Together, **ModelOp** and **Kong** are solving the "last mile" problem of enterprise AI delivery.

Reaching a milestone is always exciting. Some milestones carry a deeper meaning. Today, we're proud to share that the N|Solid Runtime has surpassed 2 million downloads. The milestone reflects growing momentum, with downloads accelerating and putting us on track to nearly double last year's total. To us, this isn't simply a download count.

Open a brokerage’s CRM instance a few years in, and it rarely looks like a sales tool anymore. Somewhere along the way, it picked up MLS feeds, transaction history, integration logic, reporting dashboards, and lately, the raw data behind a first AI pilot. None of that was the plan. Each piece got bolted on because the CRM was the system already sitting there. A CRM was built for a narrower job than that: logging a call, tracking a pipeline, managing the relationship an agent owns.

An effective Java debugging strategy lets us pause execution, inspect data, and observe real execution rather than relying on vague assumptions. The complexity of the Java Virtual Machine creates unique challenges, but a focused approach will turn this complexity to our advantage. This guide will equip you with the tools to do this, looking at: By the end, you’ll have a practical workflow to debug Java reliably across local and remote environments.

Running Apache Kafka on Amazon Managed Streaming for Apache Kafka (MSK) gives you a managed broker with no ZooKeeper to operate, automated patching, and multi-AZ replication handled by the service. What it doesn't give you is a safe, governed way to expose Kafka access beyond your VPC boundary. That problem looks simple on the surface. It isn't. And how you solve it has significant implications for security posture, operational complexity, and monthly cost.