Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened
Consider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud…
Read the full story on Kong BlogHave you worked with this?
The story is what was announced. Nobody has discussed it yet, so if it touches your team, a short post about what you’ve seen helps the next reader.
More from Kong
Recent updates from Kong, so you can tell whether this is a one-off or part of a pattern.
API & AI Summit 2026 Launch Recap
Standing up a production agent means taking it through six stages: At API & AI Summit, we announced the evolution of Kong Konnect into the AI Connectivity Platform and announced a slate of launches built around that idea. Here's what we launched, where…
Kong AI Gateway 2.2: Built for what comes next in AI
AI is not just producing different answers. It is starting to do different kinds of work. JEV introduces a different model for using AI: instead of generating text, it returns typed, probabilistic decisions that software can act on directly. By returning…
Introducing Kong AI Registry: Self-Service Discovery for Agents
API management solved a similar problem for developers. Instead of asking a platform team every time they needed an API, developers could go to a Developer Portal, discover what was available to them, and start building, within the governance boundaries…
More in Developer Tools
What other companies in Developer Tools are doing. The category page shows who’s active, side by side.
RustRover vs VS Code + rust-analyzer: What Changes in Your Rust Workflow
As the team behind a dedicated Rust IDE, we’re naturally curious to see how RustRover stacks up against other popular setups for Rust development and the strengths and trade-offs of each one. This article is the first in a series where we’ll look at different Rust workflows. We’re not unbiased, but we want to give […]
Scale without limits: Multigres, OrioleDB, and dbarena
The app your agent built in minutes stays on the same Postgres from prototype to petabyte.
Operate with confidence
More data, more tools and more control so your agent has what it needs to observe your project, investigate issues and propose fixes, autonomously.
Build anything: Supabase from code, and an MCP server for your app
Your agent sets up the backend from code, your users' agents work with your app through its own MCP server, and long-running tasks run in Supabase Compute.