XStream Runner
Execute a YAML Job locally using the streaming engine. The runner is included in the xstream-engine distribution.
Package: xstream-engine ZIP
Requires: JDK 17; Linux and Docker for isolated operator execution.
Status: Source build available.
cd xstream-engine
sbt Universal/packageBin
Output: target/universal/xstream-engine-*.zip. Bootstrap the development dependencies before building.
Check releases ↗ · Build & run
XStream Designer
Design Jobs in a browser, browse catalogs, inspect output structures and samples, and export YAML. Run the Scala service and access it from a modern browser.
Package: xstream-designer ZIP
Requires: JDK 17; Docker for local inference workers.
Status: Source build available.
cd xstream-designer
sbt Universal/packageBin
Output: target/universal/xstream-designer-*.zip. Configure catalogs, connections and the operator repository before use.
Check releases ↗ · Configuration & guide ↗
Build and verify
Follow the development bootstrap instructions first. Run each packaging command from its module directory in the XStream checkout. ZIP distributions include launch scripts and application libraries; Java is installed separately. These are development snapshots, and interfaces may change.
For published binaries, use the version, platform requirements, file size and SHA-256 checksum attached to the corresponding GitHub release. No release versions, binary sizes or checksums are advertised before artifacts are published.
Developer libraries
The data SDK, operator SDK and inference module are development libraries. Their dependency and installation instructions belong in the developer documentation.
Related project
The independent Operator Repository maintains its own service, website and distributions.