Systems | Development | Analytics | API | Testing

Document-centric workflows have been difficult to automate and required human intervention. Attempts to automate document handling often failed or did not scale, because legacy intelligent document processing (IDP) systems were fragile. They often required manually retraining models on dozens of documents just to identify specific fields—only to repeat the process whenever a format changes. The result was a costly cycle of maintenance and manual data entry.

Since its inception, agentic AI has felt like a distant aspiration. Today, agents are here, and enterprise adoption is accelerating. Gartner predicts that by 2028, the average global Fortune 500 enterprise will have more than 150,000 AI agents in use, up from fewer than 15 in 2025. Agents arrive with incredible, broad intelligence, but lack the knowledge of your operating model: your customers, policies, approvals, exceptions, business rules, systems, and operational history.

Shadow AI detection is the practice of finding and governing unsanctioned AI tools, models, and API integrations that employees deploy without security approval. It has become urgent because these tools route live enterprise data to external models in real time, and traditional security stacks cannot see them. The 2026 Cordyceps disclosure, which exposed identical AI-generated vulnerabilities across 300+ GitHub repositories, showed how fast ungoverned AI can turn into a supply-chain crisis.

‍Build Cache can meaningfully shorten CI feedback loops, but only if it’s connected to workflows where it’ll actually make a difference. So how do you figure out which workflows will benefit? That’s the part that’s been easy to get wrong — until now. Quick Connect is a new feature that takes the guesswork out of estimating time savings: it looks at your last 30 days of build data and surfaces the workflows that will benefit themost from caching.

Debug logging is a particular form of logging that records detailed information about how an application behaves during execution, so we can identify, understand, and fix issues. This guide will give you a rookie-to-pro guide to debug logging, showing you: By the end, you will have a clear, practical approach to using debug logs effectively in real applications.

*Kong makes every MCP client and server work with Enterprise-Managed Authorization, whether they speak the protocol or not.* The MCP demo impressed the room. Then someone asked how 5,000 employees would connect to 40 MCP servers, and the answer was: one OAuth consent screen at a time. Per user. Per server. No central policy, no unified audit trail, and nothing stopping a personal account from getting wired into a work tool.

AI Transport v0.4.0 includes changes to optionally support database hydration. Some applications may wish to store AI conversation history in an external store, such as a database. AI Transport's support for database hydration allows applications to reconcile that stored history with the live activity in the AI session. When using database hydration, your application persists messages for completed runs to the database.