Your rows take the short path. Control plane stays out of it.
Agents resolve secrets locally and send rows directly to your destinations. Burst Load distributes table work across those agents; CDC captures changes into a durable spool and advances each sink independently. The control plane coordinates both capabilities without receiving rows or plaintext database credentials.
Burst Load and CDC share the same placement model
Put workers close to the source and target, resolve secrets inside your environment, and scale out across Windows or Linux agents. Burst Load uses the agents for parallel table movement; CDC uses them for capture, durable spooling, and independent target apply.
Rows travel from your agent to your destinations
Place the agent near the source, or use separate compute for broker-backed direct-log capture. The agent reads changes, writes the durable spool, and sends rows directly to the destinations you configured. Captured data never detours through the control plane.
Secrets resolve locally; TLS is the default
Database credentials stay in the agent’s local secret provider. The agent initiates control traffic outbound, and TLS is required unless an operator deliberately selects the insecure development posture.
Privilege stops at four read operations
SQL Server Streaming and Sybase DirectDevice can leave a tiny, fully auditable broker beside the database while the unprivileged agent runs elsewhere. The broker exposes allowlisted open, read, length, and close operations. It exposes no write, SQL, exec, directory listing, or decode path. Oracle DirectRedo does not use this broker because the agent needs reachable redo files.
One captured stream, independent sink progress
Omni Loader decodes each source once. Every destination advances from its own checkpointed spool cursor and can pause or resume independently. Bounded storage turns an unsustainable backlog into visible back-pressure instead of silently discarding changes.
The control plane coordinates without relaying rows
Use the web control plane or CLI to enroll agents, configure connections, and create, start, pause, stop, or inspect pipelines. It receives configuration, health, and status. It is not a row-data proxy.
Measure capture before target apply enters the test
Monitor mode runs a source-only pipeline so you can inspect capture rate and lag without target apply in the measurement. Validate reader access and capture behavior first, then add destination performance.
Place each responsibility once
Show each reviewer exactly what runs where.
Source boundary
Keep the database here and, for SQL Server Streaming or Sybase DirectDevice, add the tiny read-only broker. Decode, transaction assembly, spool, and target apply can all run elsewhere.
Agent compute
Place local secrets, parallel decode, transaction assembly, compression, the durable spool, and sink clients here. A high-load database server can use a separate machine connected to the broker.
Control tier
Desired configuration, agent enrollment, pipeline lifecycle, health, and status. No captured row stream and no plaintext database credentials.
Each destination
A shipped sink connector applies or publishes from its own durable cursor, with sink-specific batching and independent pause/resume.
Draw the trust boundaries before deployment.
Show us the source host, allowed outbound routes, secret provider, log access, and destinations. We will map agent and broker placement, the row-data path, and the control traffic your reviewers need to approve.