Projection-aware CDC
Recompose affected parent documents when related rows change, without rebuilding an entire index.
One self-hosted Rust data plane for projection-aware CDC and durable realtime delivery, with an optional Fleet control plane for every agent you operate.
12:42:08.114 change received relation=orders 12:42:08.117 projection composed children=4 12:42:08.120 sink acknowledged version=94821 12:42:08.120 checkpoint advanced lag=0
VentStream treats correctness, recovery, delivery, and administration as parts of the product, not work left for every application team.
Recompose affected parent documents when related rows change, without rebuilding an entire index.
Bootstrap, checkpoint, tail, pause, resume, drain, reconcile, and recover through one runtime contract.
Version fencing keeps delayed events from overwriting or resurrecting newer search documents.
Fan out NATS JetStream or Redis Streams events through GraphQL subscriptions and native WebSockets.
Enroll agents with renewable mTLS identities and keep source credentials inside the customer data plane.
Publish immutable configuration revisions only after source, projection, sink, and secret references validate.
The engine owns the data path. Fleet owns desired state and bounded operational metadata. Customer records never need to transit the control plane.
Turn normalized operational records into denormalized OpenSearch or Elasticsearch documents. When an order item, customer, or related record changes, VentStream resolves and recomposes the correct parent document.
Publish from many backend services through NATS JetStream or Redis Streams. VentStream handles operation matching, tenant-aware routing, fan-out, slow consumers, disconnects, and replay cursors.
Scope pipelines by organization and environment, publish revisioned configuration, inspect agent health, and issue lifecycle commands from ventstreamctl while data remains in customer infrastructure.
The same engine supports local evaluation, standalone production deployment, and centrally managed Kubernetes fleets.
Download one binary, point it at validated configuration, and run directly beside the source.
Package a standalone role or managed agent with deployment-owned environment secrets.
Deploy independent CDC and realtime pods with Helm and Fleet reconciliation.
./ventstream --config ./config/ventstream.yamlSecrets resolve from the deployment environment.Run the engine standalone with your own configuration, then use Fleet when the workload needs centralized administration.