The control plane stores desired state, dispatches lifecycle commands, and aggregates health. Outbound agents capture and apply locally.
The job to be done
A capability matters when it removes an operational decision, not when it adds another checkbox. SQL Flow connects source-aware capture, durable progress, target apply, and validation so the page you are reading leads to a usable operating path.
The web app and API manage table selection, agent assignment, destinations, reload, archive, restore, and deletion. Commands reconcile after reconnect. SQL Flow handles start, pause, stop, resume, and confirmed reload; projects and reusable connections; agent enrollment, approval, and reassignment; target schema check and provisioning.
Why this path matters
The web app and API manage table selection, agent assignment, destinations, reload, archive, restore, and deletion. Commands reconcile after reconnect. SQL Flow handles start, pause, stop, resume, and confirmed reload; projects and reusable connections; agent enrollment, approval, and reassignment; target schema check and provisioning.
What changes for you
Fleet and pipeline views separate source capture, relay transfer, target apply, initial load, and spool backlog. Alerts can reach external webhooks. SQL Flow handles events and bytes per second; capture lag, apply lag, backlog, and ETA; alerts, acknowledgement, and notifications; health, API scopes, logs, and audit.
The outcome
Show us fleet size, alert channels, and operating model. We will map deployment and observability.
The payoff
Search, group, assign, and inspect every path.
Separate capture, relay, apply, load, and backlog.
Record mutations, denials, and resolutions.
Where the work happens
Read each capability as part of the operating path. The important question is not whether a feature exists, but what work it removes and what evidence it leaves behind.
Lifecycle control
The web app and API manage table selection, agent assignment, destinations, reload, archive, restore, and deletion. Commands reconcile after reconnect.
SQL Flow handles start, pause, stop, resume, and confirmed reload; projects and reusable connections; agent enrollment, approval, and reassignment; target schema check and provisioning.
Operational signal
Fleet and pipeline views separate source capture, relay transfer, target apply, initial load, and spool backlog. Alerts can reach external webhooks.
SQL Flow handles events and bytes per second; capture lag, apply lag, backlog, and ETA; alerts, acknowledgement, and notifications; health, API scopes, logs, and audit.
Before you choose
Use the page-specific details below as a short discovery checklist. They are the conditions and work areas that shape the capability, not generic product promises.
The path to confidence
The page keeps the product detail close to the decision it supports. Your team can see what the software handles automatically, what it changes for the target, and what the result leaves ready to operate.
The web app and API manage table selection, agent assignment, destinations, reload, archive, restore, and deletion. Commands reconcile after reconnect. SQL Flow handles start, pause, stop, resume, and confirmed reload; projects and reusable connections; agent enrollment, approval, and reassignment; target schema check and provisioning.
Fleet and pipeline views separate source capture, relay transfer, target apply, initial load, and spool backlog. Alerts can reach external webhooks. SQL Flow handles events and bytes per second; capture lag, apply lag, backlog, and ETA; alerts, acknowledgement, and notifications; health, API scopes, logs, and audit.
Keep the plan connected
A capability becomes easier to operate when the next decision follows from the constraint you just uncovered. Explore the related work that completes this part of the path.
Your working set
Take the next step
Show us fleet size, alert channels, and operating model. We will map deployment and observability.
Talk through my use case