Skip to main content
VentStream has two Kubernetes operating modes. Both run the same public engine image (ghcr.io/ventstream/ventstream); the mode is decided at runtime by the presence of a deployment agent key. Choose the mode before creating workloads because configuration ownership differs — an agent key alongside local source/sink configuration is a hard startup error.

​
Standalone

Use standalone mode when each workload should be entirely self-contained and restart-based lifecycle control is sufficient. The standalone guide provides a current canonical-config StatefulSet for CDC. Use the ventstream-gateway chart for replicated native WebSocket and GraphQL subscription roles.

​
Cloud-managed

Use managed mode when operators need organization-scoped inventory, immutable configuration, agent health, audit events, and CLI pause, resume, drain, reconcile, or rebootstrap operations.
  1. Create or join a VentStream Cloud organization.
  2. Mint a deployment agent key and deploy a managed engine into your Kubernetes cluster.
  3. Administer it with ventstreamctl or the dashboard.
VentStream Cloud never enters the CDC or realtime data path. Managed engines connect outbound to the Cloud agent gateway over mTLS; source records, sink writes, broker events, WebSocket connections, and GraphQL subscriptions remain inside the workload environment.

​
Common production requirements

  • Pin container images by digest and promote the same digest between environments.
  • Keep connector credentials and private keys in a managed secret provider.
  • Persist source cursors, join state, managed identity, and applied configuration.
  • Give every CDC pipeline its own replication slot or cursor and exactly one active engine instance.
  • Run helm lint and helm template against production values in CI.
  • Never delete managed-agent PVCs during routine upgrades.