Skip to main content
Start the UI from a project directory or point it at a project explicitly:
Open http://127.0.0.1:8000. The server compiles the selected project, connects to its resolved ClickHouse target, and combines authored definitions with live warehouse evidence. The header shows the project and target, connection state, and the time of the current warehouse snapshot. StreamBuild refreshes live state periodically, and the refresh button requests a new snapshot immediately.
StreamBuild development UI overview with source, model, quality, and warehouse state

​
Find the right view

StreamBuild lineage view showing sources, pipelines, models, and dependency edges

​
Operating model

The UI serves one resolved project and target per stb dev process. Configuration remains owned by streambuild_project.toml and streambuild_local.toml; Settings displays the effective values but does not edit them. The Plan workflow can execute direct-mode builds through the same StreamBuild command path used by the CLI. Virtual deployment inventory, audit, diff, promotion, rollback, repair, and cleanup remain explicit CLI operations. See Virtual Environments. stb dev is a local development surface, not a multi-user control plane. Keep the default loopback binding unless you intentionally provide network access controls.

​
Next steps

Sources and messages

Trace ingestion, lag, topics, and retained records.

Plans and runs

Preview changes, launch builds, and inspect execution.

Quality

Run tests and audits and understand scheduler state.