Big thanks to the 37 people who joined us on the first-ever Kong Community Call! The inspiring demo, interesting discussion and enthusiastic participation have me looking forward to the monthly calls moving forward! As an evangelist for Kong, it makes me really happy to see such great participation from everyone who came to the call looking to learn or share their knowledge with the rest of the community.
Ross Sbriscia and Jeremy Justus gave a wonderful demo of the Spec Expose plugin that they built for Optum. They also had some insightful points of view about the evolving role of open source software in enterprises and the experience of working with open source vs. proprietary software.
Thibault Charbonnier, in addition to our planned conversation of Kong 1.0 changes, gave a great explainer of the debugging resources available for Kong plugins, both in Kong itself and in the Plugin Development Kit (PDK). The group also discussed the product announcements and sessions at Kong Summit.
All the community calls are recorded, so if you weren't able to join us for the first one, you can catch up with the recording below and ask any follow-up questions or continue the discussion on Kong Nation!
Our second call was on October 16 at 10 a.m. PT. In honor of Hacktoberfest, Cooper Marcus gave an introduction to contributing to the Kong docs, and we had another plugin demo — this time from a partner, Okta.
If you'd like to attend the meeting, get the latest schedule details, or propose a topic for a future call, visit our open Google doc agenda. To get a Google calendar invite for future calls, please add your email address to the very bottom section of the doc, and I will add you!
Hope to see you soon!
Meet Emily. She’s an API product manager at ACME, Inc., an ecommerce company that runs on dozens of APIs. One morning, her team lead asks a simple question: “Who’s our top API consumer, and which of your APIs are causing the most issues right now?”
This year, at our in-person API Summit , we’re excited to shine a light on the projects and people who aren’t just implementing Kong, but reinventing it. The Kong Innovator Awards recognize outstanding and future-facing projects from Kong custome
In the last two parts of this series, we discussed How to Strengthen a ReAct AI Agent with Kong AI Gateway and How to Build a Single-LLM AI Agent with Kong AI Gateway and LangGraph . In this third and final part, we're going to evolve the AI Agen
In my previous post, we discussed how we can implement a basic AI Agent with Kong AI Gateway. In part two of this series, we're going to review LangGraph fundamentals, rewrite the AI Agent and explore how Kong AI Gateway can be used to protect an LLM
This is part one of a series exploring how Kong AI Gateway can be used in an AI Agent development with LangGraph. The series comprises three parts: Basic ReAct AI Agent with Kong AI Gateway Single LLM ReAct AI Agent with Kong AI Gateway and LangGr
Update Includes Data Orchestration, CyberArk Support, Solace Integration, and Kafka Schema Validation We’re excited to bring you Kong Gateway Enterprise 3.11 with compelling new features to make your APIs and event streams even more powerful, includ
What Is RAG, and Why Should You Use It? RAG (Retrieval-Augmented Generation) is not a new concept in AI, and unsurprisingly, when talking to companies, everyone seems to have their own interpretation of how to implement it. So, let’s start with a r
