01
Register the devices you trust
Install the Yavisynker Windows app on each PC, sign in to the same account, name each computer, and pick where its YaviSynker folder should be created.
How it works
A direct path from one trusted device to another.
Yavisynker coordinates the introduction, then gets out of the file path. Your desktops compare verified manifests and move the missing file pieces directly.
Direct transfer
After authenticated setup
Work PC
Home PC
project.psd2 blocks changed
Direct
File transfer path
Encrypted
WebRTC data channel
None
Server copies of your files
From setup to sync
Three stages, one clear trust boundary
The account service knows which devices belong together. The devices know the files.
02
Devices establish a direct path
The control service exchanges short-lived, signed connection setup messages. The desktops authenticate one another before opening an encrypted WebRTC data channel.
03
Only the needed pieces move
Files are split into content-addressed blocks. After a small edit, the receiving device usually requests only blocks it does not already hold.
Control service
What the server handles
- Account authentication and registered devices
- Short-lived presence and signed connection setup
- Free access, licenses, referrals, and installer access
- Bounded security and administrative records
Direct device channel
What stays between devices
- Current filenames and file manifests
- Requests for the blocks a peer is missing
- Verified file content blocks
- Small wake-up and progress messages
Truthful edge cases
Predictable behavior when conditions are not perfect
Direct sync should make waiting and conflicts visible, not hide them behind an imaginary cloud copy.
When another device is offline
Sync waits safely and retries. Local files stay in place until another device becomes reachable. Yavisynker uses STUN only and never relays your files through a server, so a few restrictive network pairs will not connect until the two devices share a more permissive network.
When both copies changed
Yavisynker keeps a deterministic main copy and preserves the other edit as a conflict copy instead of silently discarding it.
When identity changes unexpectedly
A previously pinned device identity is not silently replaced. The connection is blocked so the change can be investigated.
Sync is not backup.
Changes and deletions can propagate. Keep a separate, tested backup for files you cannot replace.
Start free, forever