Systems | Development | Analytics | API | Testing

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 numbers tell the story. Organizations using AI in at least one business function jumped from 55% to 78% in just one year. Generative AI usage specifically rose from 33% in 2023 to 71% in 2024.

KAi, the AI assistant inside Kong Konnect, just got significantly more capable. Today, we're announcing an enhanced beta version powered by the new Kong Konnect MCP Server — a shared infrastructure layer that also opens up your API platform to IDE copilots and custom agents. The result? KAi can now do things it couldn't before, and those same capabilities are available wherever you work. If you've used KAi before, you'll notice the difference immediately.

If you want to spin up a fast API solution, DreamFactory is a great way to do that with a Bitnami install. Within minutes you can have a fully documented and secure REST API to utilize. Just like any program bundle, there are lots of features to learn and interact with. Outside of a Docker Swarm or AWS ELB setup, it is pretty hard to find a way to spin up a DreamFactory instance faster. We are going to dive in a bit further to find out how to interact with the system database.

DreamFactory 2.5 now supports Apple Push Notification Service (APNs). This blog post will show you how easy it is configure DreamFactory as your iOS app’s push notification provider. Note that APNs support is a premium feature in DreamFactory's Silver and Gold products, not an open source feature. APNs is a native DreamFactory service that supports role-service-access, live API documentation, script access, etc.

Your first data integration took two weeks. The second took three weeks, because you had to refactor some code. Your third one is now in week five, and you’re realizing the architecture you built for two sources doesn’t scale to three. If this sounds familiar, you’re not alone. This isn’t because your team isn’t capable. It’s because data integration complexity doesn’t scale linearly. It compounds. It doesn’t have to be this way.

If you’re an SAP customer, you’ve probably heard the same pitch more than once: just wait a little longer. Your migration to S/4HANA will unlock the agility you need. Your SAP Business Technology Platform (BTP) investments will catch up soon. Your workflows will get faster. Your data will become more accessible. Just a little more time. But what if you can’t wait? What if your supply chain teams are buried under manual work?