Build a Streamhouse on Confluent Cloud

A Streamhouse is a category of data architecture, like a lakehouse, that keeps one current, trusted picture of your business for every consumer to read from. A consumer can be a person, a service, or an AI agent.

Diagram of a Streamhouse: databases, apps, and devices feed one current picture that agents, apps, and analytics read.

A Streamhouse captures change from every source into one current, trusted picture of your business, and every consumer reads from that picture.

On Confluent Cloud, you assemble a Streamhouse from the capabilities you already use, such as streaming, connectors, stream processing, governance, and queries, rather than buying it as a product.

These properties define a Streamhouse:

  • Real-time: State is continuously maintained as events arrive, rather than rebuilt on a batch schedule.

  • Always-on: A Streamhouse runs the business, so it’s engineered to production service levels rather than to reporting schedules.

  • Decentralized: A change is relayed everywhere it’s needed, in each consumer’s own interface, instead of forcing everyone to a single database.

Solutions you can build with a Streamhouse

A Streamhouse powers eight solutions, in two domains.

  • The first domain is the data and trust layer: a Streamhouse builds and protects one trusted picture of your business.

  • The second domain is the consumption layer: the Streamhouse turns this trusted picture of your business into outcomes.

Capture and maintain your business

Build and protect one current, trusted picture of your business:

Run your business

Turn current state into outcomes:

Where you start: one always-current table

The entry point into a Streamhouse is a single continuously maintained table that you define once and serve to every consumer. To learn how you build and serve it, see Start here: the always-current table.

Next steps