This looks most useful when you want more than a plain copy, especially receiving files on a laptop without running an SSH server and driving transfers from scripts. The tradeoff is that compatibility details matter a lot, because the project already asks people not to treat it as a drop in rsync replacement.

syq
Screenshots haven’t been added yet. Visit the product to take a look.
syq is a command-line tool for fast, programmable file operations including copying, reorganizing, and removing files locally or across machines. It supports resuming interrupted transfers, remote command execution, and scripting via JSON API or Python SDK without requiring an SSH server on the laptop.
Ratings & Reviews
Write a reviewInformation
Website checks
Automated checks of the public website by Google Lighthouse 13.5.0. Scores can vary between runs.
Checked Oct 22, 2026
Test this website on PageSpeedWebsite checks refresh automatically each week.
- Performance
- 93 out of 100, Good
- Accessibility
- 100 out of 100, Good
- Best Practices
- 81 out of 100, Needs improvement
- SEO
- 100 out of 100, Good
Around the Web
I'm eager to replace battle-tested rsync with a new half-baked tool that no one uses for a tiny speed improvement. I'm also going to enable automatic updates of that tool too.
cynicalsecurity · Imported from Show HN
I thought I'd share a more positive comment. I work on a tool in a similar area (moving stuff around) but on a higher level. I currently use rsync or rclone for the file moving parts. So to me your tool looks interesting and promising, thanks for sharing it :) Some suggestions for improvement for your website/Github: - I wanted to understand how it differs from rsync. A comparison page would be helpful. - A comparison to rclone would also be interesting, as it also uses multiple parallel connections. - As it target more advanced users I think it would be helpful to provide more advanced technical insights on how your transfers exactly work. Also how are edge cases handled, what tests are done? Moving and copying files is critical, and you need to inspire trust in your project among users.
hxseven · Imported from Show HN
> I also added cool features like the ability to maintain a persistent ssh connection to the server for fast one-offs rsync already supports this via OpenSSH's ControlMaster directive. Bonus, it speeds up every connection to that server rather then a single tool's. > the ability to do direct remote-remote transfers without forwarding your ssh agent (by using restricted ssh keys on the receiver that will only execute a specific request signed with the key on your laptop). You can control your agent forwarding in your local ssh client configuration. And with modern ProxyJump, you don't need to forward your agent at all regardless of how many bastion hops are between you and your final target.
unsnap_biceps · Imported from Show HN
Thank you for showing this. I'll echo what some others say: if you're claiming to be faster than rsync, you should demonstrate why front-and-center. There have been decades of documentation on how rsync optimizes transfers, so it's a lot to live up to. As an aside, It's perhaps an indictment of our networking landscape that multiple parallel connections between 2 specific machines would accelerate a transfer. I would've expected a single TCP connection to be able to saturate a line. Or perhaps the parallel connections seeks to amortize the per-file setup overhead?
AceJohnny2 · Imported from Show HN
rclone has been the real fully featured ultra power alternative to rsync over the past 4-5 years. How do you compare Syq to rclone ?
QuiCasseRien · Imported from Show HN