Change data capture
Capture database changes as they happen.
Capture changes from supported databases, choose a delivery integration and monitor source, destination and runtime state.
- Insert
- Update
- Delete
Core capabilities
Continuous capture
Capture inserts, updates and deletes from supported transactional sources.
Landing or current state
Delivery behavior is explicit: some integrations maintain current-state relational tables, while warehouse and event destinations may preserve raw change evidence.
Recovery controls
Pause, resume, retry destination delivery and inspect checkpoint or offset evidence when supported by the pipeline state.
Workflow
01Check readiness before deployment.
PipePilot checks the connection, database prerequisites, capture scope and runtime. Source-specific prerequisites are reviewed before capture starts.
Table or schema scope where supported
Private Agent or enabled managed execution
Source and destination task status
Fresh capture identity when a deleted name is reused
Configuration and runtime evidence stay attached to the workflow.
Workflow
02Land changes at your destination.
A stream from a supported database can deliver selected table changes to an enabled destination integration. PipePilot shows runtime, task and delivery status; downstream final-table materialization remains a separate warehouse workflow.
Explicit destination schema
Landing behavior shown before deployment
Destination recovery without replacing source capture
Raw events do not automatically update final tables
Configuration and runtime evidence stay attached to the workflow.
Next step
Plan your data workflow.
Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.