Control plane and observability
Operate the fleet from one place. Keep row data out of it.
The control plane stores desired state, dispatches lifecycle commands, and aggregates health. Outbound agents capture and apply locally.
Your environment 
Source databaseTransaction log
STREAM / LOG BYTES
A
Capture agentCredentials stay here
OUTTLS · outbound only
Control plane
OrchestrateControl + observe
Fleet
Pipelines and agents
Search, group, assign, and inspect every path.
Live
Lag and throughput
Separate capture, relay, apply, load, and backlog.
Audit
Operator evidence
Record mutations, denials, and resolutions.
Lifecycle control
Create, change, recover, and retire pipelines.
The web app and API manage table selection, agent assignment, destinations, reload, archive, restore, and deletion. Commands reconcile after reconnect.
✓ Start, pause, stop, resume, and confirmed reload
✓ Projects and reusable connections
✓ Agent enrollment, approval, and reassignment
✓ Target schema check and provisioning
Operational signal
See which phase owns the lag.
Fleet and pipeline views separate source capture, relay transfer, target apply, initial load, and spool backlog. Alerts can reach external webhooks.
✓ Events and bytes per second
✓ Capture lag, apply lag, backlog, and ETA
✓ Alerts, acknowledgement, and notifications
✓ Health, API scopes, logs, and audit
Keep exploring
See the connected parts of the platform.
Give operators the whole pipeline, not one green light.
Show us fleet size, alert channels, and operating model. We will map deployment and observability.