SQL Flow ships as native Windows and Linux archives. Run one process for a standalone migration or coordinate agents across machines for more capacity and network locality.
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.
Run SqlFlow.exe on Windows or SqlFlow on Linux and bind the web server to the selected port. A standalone process is enough for local evaluation and migrations that fit one machine.
Why this path matters
Run SqlFlow.exe on Windows or SqlFlow on Linux and bind the web server to the selected port. A standalone process is enough for local evaluation and migrations that fit one machine.
What changes for you
Start SQL Flow with --cluster, then point Windows or Linux agents at the orchestrator address. Place agents on separate machines when additional compute, source locality, or target locality improves the real path. SQL Flow handles one orchestrator; agents on separate machines; explicit listen and advertised endpoints; burst Load and CDC on shared deployment foundations.
The outcome
Tell us the source and target networks, operating systems, and available machines. We will map standalone or clustered placement for Burst Load and CDC.
The payoff
Use the operating system already approved for the migration environment.
Launch the built-in web interface and worker from one runtime.
Add machines where more workers or network locality help.
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.
Standalone mode
Run SqlFlow.exe on Windows or SqlFlow on Linux and bind the web server to the selected port. A standalone process is enough for local evaluation and migrations that fit one machine.
Cluster mode
Start SQL Flow with --cluster, then point Windows or Linux agents at the orchestrator address. Place agents on separate machines when additional compute, source locality, or target locality improves the real path.
SQL Flow handles one orchestrator; agents on separate machines; explicit listen and advertised endpoints; burst Load and CDC on shared deployment foundations.
Console mode
Pass a JSON job with --job for scheduled and CI/CD migrations. Structured logs record the automated run while secrets and network placement stay inside the environment you control.
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.
Run SqlFlow.exe on Windows or SqlFlow on Linux and bind the web server to the selected port. A standalone process is enough for local evaluation and migrations that fit one machine.
Start SQL Flow with --cluster, then point Windows or Linux agents at the orchestrator address. Place agents on separate machines when additional compute, source locality, or target locality improves the real path. SQL Flow handles one orchestrator; agents on separate machines; explicit listen and advertised endpoints; burst Load and CDC on shared deployment foundations.
Pass a JSON job with --job for scheduled and CI/CD migrations. Structured logs record the automated run while secrets and network placement stay inside the environment you control.
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
Tell us the source and target networks, operating systems, and available machines. We will map standalone or clustered placement for Burst Load and CDC.
Talk through my use case