Change data capture

Joined projections that stay correct.

Capture native database changes, resolve affected parent records, and maintain versioned search documents without application dual-writes.

5source families

Nativechange streams

Versionedsink writes

System boundary

A focused runtime between inputs and outcomes.

Capture from

PostgreSQLWAL

MySQL / MariaDBBINLOG

MongoDBCHANGE STREAM

Neo4jCDC

Kafka / RedpandaRECORDS

Projection engine

Resolve · compose · fence · checkpoint

● healthy

Maintain

OpenSearchDOCUMENTS

ElasticsearchCOMPATIBLE

Joined projectionsRECOMPOSED

Checkpoint stateDURABLE

Built for operations

A child-table change resolves the affected primary key and rebuilds only the dependent document.

Version-aware writes prevent delayed events from overwriting or resurrecting newer state.

Bootstrap, tail, pause, resume, drain, reconcile, and restart from durable checkpoints.

Separate source, projection, sink, and secret references with control-plane validation.

Operating model

The runtime contract covers deployment, recovery, and administration rather than stopping at the happy-path data flow.

Bootstrap and tail

Build the initial projection, then transition to continuous CDC without changing the target contract.

Repair deliberately

Reconcile selected key ranges rather than rebuilding an entire search index after a localized issue.

Run standalone or managed

Use the open engine directly or enroll the same binary as a Fleet-managed agent.

Continue exploringRealtime delivery