Skip to main content
VentStream Cloud is the managed control plane for CDC and realtime engine workloads. It inventories deployments, attaches engines with agent keys, distributes desired state and configuration, records durable operations, and provides organization-scoped visibility. The management plane is hosted by VentStream. Managed agents run in your infrastructure and connect outbound to Cloud. Source records, sink writes, broker events, GraphQL subscriptions, and WebSocket traffic stay in the engine data path; they are not proxied through the control plane. Operators use the dashboard or ventstreamctl over HTTPS to set desired state in VentStream Cloud; the managed engine dials out over mTLS from the customer environment and applies it, while CDC and realtime data flow only between the engine and local sources, brokers, and sinks.

​
Administration surfaces

  • The dashboard provides onboarding, organization membership, pipeline creation, configuration editing, deployment guidance, observability, billing, and settings.
  • ventstreamctl provides repeatable pipeline, deployment, configuration, lifecycle, identity, status, and operation workflows.
  • Kubernetes, Docker Compose, or your scheduler creates the managed engine workload in your infrastructure. Cloud administers it after the agent-key handshake; it does not deploy directly into your cluster.

​
Managed and standalone modes

There is one public engine artifact — the same binary and image (ghcr.io/ventstream/ventstream) runs standalone or managed. Standalone engines run from local configuration with no Cloud dependency; without an agent key the engine makes zero platform connections. Presenting a deployment-scoped agent key at startup makes the engine managed: its built-in fleet client connects outbound to Cloud and runs the pipeline according to persisted desired state. Standalone engines are operated through their process manager, Kubernetes, or another scheduler. They cannot be paused, resumed, configured, or inspected with ventstreamctl because they are not attached to VentStream Cloud. Choose VentStream Cloud when you need centralized inventory, configuration history, runtime visibility, controlled pause/resume/drain operations, agent identity, or administration across organizations and environments.

Create a Cloud account

Start an organization or accept an invitation.

Administer with the CLI

Install ventstreamctl and manage attached pipelines.