Install

Supported platforms

Platform	Engine (`ventstream`)	Cloud CLI (`ventstreamctl`)
macOS (Apple Silicon / Intel)	✅	✅
Linux (arm64 / amd64)	✅	✅
Windows (amd64)	✅ native (engine v0.1.28+; no Kafka source)	✅ (CLI v0.2.27+)

On Windows every source and sink is available except the Kafka source (its native library has no supported Windows build) — use WSL2 or the container image for Kafka pipelines.

Engine

macOS / Linux
Windows
Container

One line — detects your OS and architecture, verifies checksums, installs to ~/.local/bin:

curl -fsSL https://ventstream.dev/install.sh | sh

Pin a version or change the location with env vars:

VENTSTREAM_VERSION=0.1.43 VENTSTREAM_INSTALL_DIR=/usr/local/bin \
  curl -fsSL https://ventstream.dev/install.sh | sh

PowerShell — verifies the SHA256 checksum against the release manifest before extracting, installs to %LOCALAPPDATA%\Programs\ventstream, and adds it to your user PATH:

irm https://ventstream.dev/install.ps1 | iex

Pin a version with an env var:

$env:VENTSTREAM_VERSION = "0.1.43"; irm https://ventstream.dev/install.ps1 | iex

The Kafka source is not included in the Windows build — use WSL2 or the container image for Kafka pipelines.

One public image runs standalone or managed depending only on whether an agent key is present:

docker run ghcr.io/ventstream/ventstream:0.1.43

See Deploy for Kubernetes.

Specific platform builds are on the releases page.

VentStream Cloud CLI (managed users)

macOS / Linux
Windows

curl -fsSL https://ventstream.dev/install-cli.sh | sh

irm https://ventstream.dev/install-cli.ps1 | iex

Installs ventstreamctl.exe to %LOCALAPPDATA%\Programs\ventstream after verifying its checksum, and adds it to your user PATH.

Every artifact ships with SHA256SUMS and per-platform SBOMs; the installer scripts verify checksums before installing.

Verify

ventstream --version
ventstreamctl version

The engine and ventstreamctl version independently — the engine follows the 0.1.x release train and the CLI the 0.2.x train, so their versions are not expected to match.

Try it

This is all it takes to stream CDC from MongoDB into Elasticsearch or OpenSearch — every insert, update, and delete, snapshot-bootstrapped and then live from the change stream:

VS_ROLES=cdc VS_CDC_SOURCE=mongodb \
VS_MONGO_URI='mongodb+srv://user:pass@cluster.example.net/?retryWrites=true' \
VS_MONGO_DATABASE=shop \
VS_MONGO_STATE_DIR=./state \
VS_MONGO_BOOTSTRAP_MODE=snapshot \
VS_OS_ENDPOINT=http://localhost:9200 \
VS_INDEX_TEMPLATE='${header:ventstream.cdc.relation}' \
ventstream

One index per collection, deterministic document ids, deletes propagate. Swap the source for Postgres, MySQL, or Neo4j, or the sink for Meilisearch or Redis — same binary. For a full guided run with seeded data, take the Quickstart.

Get started

Concepts

Connectors

Real-time

Deploy

Guides

Deep dives

Reference

Supported platforms

Engine

VentStream Cloud CLI (managed users)

Verify

Try it

​Supported platforms

​Engine

​VentStream Cloud CLI (managed users)

​Verify

​Try it

Supported platforms

Engine

VentStream Cloud CLI (managed users)

Verify

Try it