01
FTP stays FTP
The source system connects to Sync Bridge just like it would to any other FTP or FTPS server.
Keep FTP and FTPS local.Use SFTP externally.
Existing systems keep sending over FTP or FTPS. Sync Bridge handles the SFTP connection to Sync Motion.
Windows · Linux · Docker · Outbound connection over port 22 · No internet-facing FTP server
Windows · Linux · Docker
Outbound connection over port 22
No internet-facing FTP server
The existing FTP/FTPS service stays.
If a machine controller, Plesk installation, or older application only supports FTP or FTPS as a storage target, Sync Bridge provides the matching endpoint on your local network.
Source systems
Plesk
Machines
Cameras
Legacy software
FTP or FTPS on the local network
Sync Bridge
On your local network
Secure over port 22
Managed SFTP
Sync Motion SFTP
Result
The source system continues to communicate over FTP or FTPS.
What stays unchanged
No rebuild of the source system.
02
No external FTP port
FTP and FTPS stop at the local network. Only the Bridge opens an encrypted SSH connection to external storage.
03
No second file copy
The Bridge works on the remote SFTP storage. The solution requires no scheduled synchronisation.
Setup
Install. Enter the target. Keep it running.
- 01
Start the Bridge on your local network
Sync Bridge runs on Windows, Linux, or as a Docker container.
- 02
Add the SFTP access
Enter the host, port, and credentials once.
- 03
Point the existing system to the Bridge
Change the server address and credentials to the Bridge in the source system.
Typical use cases
Systems using FTP or FTPS.
Machines and plants
The controller writes CSV files, XML data, or logs over FTP.
Cameras and recorders
Cameras and recorders send their exports over FTP to the local Bridge.
ERP and EDI
File-based ERP and EDI interfaces continue to use FTP or FTPS.
Backup software
For existing backup jobs, only change the destination address to the local Bridge.
Legacy software
Older applications connect to the local Bridge over FTP or FTPS.
Plesk backups
Plesk uses the local Bridge as its FTP(S) backup target.
Technical scope
What Sync Bridge supports.
Inbound
01- FTP
- Explicit FTPS (AUTH TLS)
- Passive FTP mode
- Configurable passive port range
Outbound
02- SFTP over SSH
- Port 22
- Password or SSH key
- SSH host key verification
Operation
03- Windows
- Linux
- Docker
- Operational logs plus health and readiness checks
File operations
04- Upload and download
- List and create directories
- Rename and delete files
- Resume interrupted transfers when supported by the client
FAQ
Questions about the FTP/FTPS Bridge.
01Do I need to change my system?
No. The system continues to send over FTP or FTPS. You only change the destination address and credentials to the locally running Bridge.
02Does the Bridge run at Sync Motion or on our network?
On your network. The Bridge runs on Windows, Linux, or as a Docker container. The source system reaches it locally, while the Bridge opens the outbound SFTP connection over port 22.
03Is FTP encrypted through the Bridge?
The connection from the Bridge to Sync Motion is always encrypted. Plain FTP on the local network is not. Use plain FTP only inside a restricted, trusted network and choose FTPS whenever the client supports it.
04Are files stored locally first?
No. The Bridge works on the remote SFTP file system. It does not run a synchronisation job or retain a permanent local copy.
05Does the Bridge work with Plesk?
Yes. Plesk keeps FTP(S) as its storage target. Enter the locally reachable Bridge as the server; the Sync Motion SFTP access sits behind it.
Next step
Check Sync Bridge for my system.
We will check by email whether the Bridge fits your client and network.
Available as a managed pilot.