Current 2026: Why Confluent's Streamhouse Could Solve AI's Real-Time Data Problem

What happens when an AI agent makes a business decision using information that's already out of date? It's a question I wanted to put to Stephen Deasy, CTO of Confluent, when we met at Current 2026 in San Francisco. After attending more than 20 technology conferences this year, I've heard countless promises about what AI agents will eventually achieve. But there's a growing problem behind those ambitions. Businesses are still struggling to get accurate, current information out of the systems they already own.

Confluent has introduced Streamhouse, a data architecture designed to address that problem. Stephen explains why the company believes existing approaches can leave applications working with delayed or incomplete information, and how the new architecture brings streaming, processing, governance, and querying together. We also discuss Lightning Tables, one of Confluent's major announcements at the event, and what direct access to current Kafka data could mean for developers and their businesses.

I was particularly interested in what this means for companies that have already invested heavily in data warehouses and lakehouses. Stephen makes the distinction between analyzing past performance and running business operations using current information. He explains why Confluent sees these approaches working together, and why existing technology investments can provide the foundation for introducing Streamhouse.

We also discuss the experiences of Instacart and Citizens Bank. Stephen recalls how Instacart faced a sudden increase in demand during the pandemic, when accurate information about orders, inventory, and deliveries became especially important. He also describes how Citizens Bank improved loan fulfillment processes through real-time data streaming. Both examples help explain why the speed at which information moves between business systems can affect customers directly.

The conversation also covers IBM's relationship with Confluent, open technologies including Kafka and Flink, and the announcement that Tableflow is now generally available on Google Cloud. Stephen shares his thoughts on model evaluation, human oversight, and how companies should measure returns from their technology spending.

One of my final questions concerns the misconceptions surrounding Streamhouse. Stephen explains that the architecture brings together approaches many organizations have already been working toward, and that its value lies partly in making those capabilities ea