A full copy on every device, or a folder you open.
Syncthing keeps a full copy of the folder on every device, so every machine needs room for all of it. KEIBIDROP mounts the folder instead and a read pulls only the bytes it touches, so a large project costs nothing on disk until you open something in it.
| KEIBIDROP | Syncthing | |
|---|---|---|
| Disk used on the second machine | Only what you open | A full copy |
| Time before you can work | Immediate, it mounts | After the sync finishes |
| Open a file without copying the folder | Yes | No |
| Both peers online | Required | Not required |
| Many devices | Two per share | A fleet |
| Account | None | None |
| Encryption | End to end, X25519 with ML-KEM-1024 | End to end, TLS |
| Source code | Open, MPL-2.0 | Open, MPL-2.0 |
KEIBIDROP mounts the other machine's folder as a folder on yours, and a read pulls only the bytes it touches, so a whole shoot takes no disk on the second machine until someone opens a take. Syncthing replicates the folder to every device that joins it.
The mount appears and the tree is browsable straight away, so there is no wait for a first sync to finish before anyone can open anything.
The mount is a real filesystem, so Premiere, Resolve, Blender, grep and git open a path on it the way they open a local one.
No. It mounts the folder and a read pulls only the bytes it touches, so disk on the second machine grows with what you open. Syncthing keeps a full copy on every device.
Yes. A KeibiDrop share joins two machines that are both running, where Syncthing catches up whenever a device comes back.
A share joins two machines. Syncthing is built for a fleet of them.
Compared with Blip · Compared with LocalSend · Compared with croc · Install