Agents need real access to do real work - but when MCP connects your AI to production systems like Kafka, who controls what it can touch? OAuth 2.1 is emerging as the answer.
What happens when a security intelligence company decides that data contracts aren't optional, they're the foundation? For SecurityScorecard, that decision changed everything: how teams share data, how pipelines are built, and how quickly a new engineer can ship production-grade work on day one.
45 million vehicles, 90 markets, 12+ iconic brands, each with its own data silos, standards, and infrastructures. In this episode, Chetan Alatagi, Solution Architect reveals how they transitioned from fragmented legacy ETL silos to a Unified Data Ecosystem—a global data streaming highway that turns vehicle telemetry into real-time value.
2025 was vibe coding. 2026 is Agentic Engineering - and the security rules haven't caught up. AI agents now have direct access to your databases, your APIs, your Kafka clusters. The protocol giving them that access is MCP. And most teams have no idea how exposed they are. We are fixing this problem with OAuth 2.1.
At Lenses, our goal has always been to help organizations get the most out of their streaming data. We started with visibility into the Apache Kafka, moving up to the part that drives value, the application layer and now the Agentic layer. Lenses 6 moved us into a multi-Kafka world, as increasing, our clients aren’t just running on one type of Kafka anymore, and as sovereign cloud becomes increasingly topical (no pun intended) this is only increasing.
Jonas Best & Patrick Polster Kafka migrations are one of the riskiest infrastructure projects a platform team can take on. Miss a dependency and a downstream app starts reprocessing events it already handled leading to breaking SLAs and eroding trust with application teams. Migrate without visibility and you risk a major production issue. The instinct is to reach for a replication tool and call it done. But replication is only one piece of the puzzle.
First in a 3-part series on self-service K2K replication. This post tackles how to give self-service access to deploy K2K without handing over the keys to your Kafka clusters. Lenses developed K2K (Kafka-to-Kafka) to solve two major problems: This includes making it as self-service as possible so developers can deploy without requiring a PhD in MirrorMaker2. One key design requirement: don’t force engineers to manage credentials to authenticate with Kafka.
In 2025, Model Context Protocol (MCP) captured the imagination of the AI engineering community. 2026 will be the year that everyone realises their prototypes need to run in production.
Queues for Kafka is now in General Availability (GA) on Confluent Cloud and is coming soon to Confluent Platform, coinciding with the Apache Kafka 4.2 release. This milestone brings production-ready queue semantics and elastic consumer scaling natively to Kafka through KIP-932, enabling organizations to consolidate their messaging infrastructures while gaining elastic consumer scaling and per-message processing controls. Get started.