Aiven, Confluent, Redpanda, StreamNative, and Ververica are forming the Streamhouse Working Group—publishing an open, vendor-neutral definition of Streamhouse, a data architecture designed to keep the current state of a business continuously available to production applications, analytics, and AI agents.
Under the binding Trademark Commitment published with the definition, anyone may use the Streamhouse name to refer to the category or architecture, permanently and free of charge, according to the companies.
Organizations are beginning to deploy applications and AI agents that do more than analyze what happened in the past: they make decisions and act as business events unfold. To act reliably, these systems need fresh, governed business context delivered continuously and at production service levels.
The five founding companies aim to approach this challenge from different technological perspectives. They formed the Streamhouse Working Group because they see organizations converging on a common architectural pattern. Streaming technologies are foundational to that pattern, but no single project, component, or vendor portfolio constitutes a Streamhouse on its own, the companies said.
A Streamhouse architecture enables organizations to capture, transport, transform, govern, and serve the current state of their business continuously so that production applications and AI agents can act on it.
The architecture is defined by three attributes:
- Real-time: Data remains continuously current as business events occur, rather than being refreshed only through periodic batch processes.
- Production-native: The architecture is engineered to production service levels because business-critical applications, analytics, and agents depend on it continuously.
- Decentralized: It meets data where it already lives rather than requiring all enterprise data to be consolidated into a single system first.
Change data capture, event streams, stream processing, open table formats, catalogs, and low-latency serving exemplify this approach. Organizations can build a Streamhouse with open-source technologies, commercial products, or both.
Lakehouse architectures expanded the ability to store and analyze large volumes of historical data for business intelligence. A Streamhouse is designed to help applications and agents run the business as events happen. These two architectures coexist in many of the world's leading organizations, each serving their intended workloads and exchanging data through open formats, said the vendors.
The Streamhouse Working Group will work to:
- Maintain and evolve the Streamhouse definition publicly through a versioned repository.
- Advance the technologies, open standards, and interoperability practices needed to build Streamhouse architectures.
- Encourage participation from customers, practitioners, technology providers, and the broader data community.
- Preserve Streamhouse as an open, vendor-neutral category that no single company controls.
“Applications and agents increasingly need fresh, governed data as events happen,” the five founding members of the Streamhouse Working Group said in a joint statement. “An open definition gives the industry shared language for this architecture and a common starting point for advancing the technologies and standards behind it.”
For more information about this news, visit streamhouse.com.