
- Direct mode is the default.
stb buildrebuilds selected models at their ordinary names and replays retained history without a publish step. - Virtual environments are an explicit opt-in.
stb buildcreates deployment-specific tables,stb deployment auditassesses them, promotion switches stable views, and retained publications can be compared or rolled back as a complete graph. - Mixed builds stage selected virtual pipelines first, then apply selected direct pipelines in the same CLI invocation. Relationships cannot cross the mode boundary.
What StreamBuild manages
- Strict, explicitly typed
MODEL()SQL - Managed Kafka landing through ClickHouse’s Kafka engine
- Adopted ClickHouse stream tables that StreamBuild does not own
- Materialized-view dependency graphs with driving and side-reference edges
- Inclusive, at-least-once replay across offset, timestamp, landed-at, and cursor boundaries
- SQL-native model tests, macro tests, and data-quality audits
- Single-process scheduled audits using the warehouse clock
- A local UI for plans, runs, deployments, lineage, Kafka lag, topics, and retained source messages
- Offline compile artifacts for review and automation
Choose a workflow
Direct-mode quickstart
Build a small adopted-source pipeline against local ClickHouse.
Direct mode
Understand destructive rebuilds, replay, failure, and rerun behavior.
Virtual environments
Stage, inspect, assess, compare, promote, roll back, diagnose, and clean deployments.
Development UI
Explore lineage, sources, messages, plans, quality, and durable runs.
Orders demo
Run the checked-in Kafka-to-ClickHouse direct-mode example.
Core loop
--project-dir explicitly.
stb build already runs applicable audits. Use the separate stb audit command when you want to
rerun live checks later without rebuilding.
