YadoriLink 日本語

local-first · peer-to-peer · open source

Folder sync that keeps file contents off central storage.

YadoriLink keeps folders in sync across your own devices. Files travel directly between devices over an encrypted tunnel; the service only ever learns who you are and which of your devices hold which folder — never what’s in your files.

Read the source ↗ Download

● pre-1.0 — under active development · Rust · Linux / macOS / Windows

coordination plane accounts · device identity · folder membership — never file contents — identity only identity only your laptop ~/work/design your desktop ~/work/design file contents — direct, encrypted, peer-to-peer across NATs by hole punching — the plane signals, never relays coordination plane accounts · devices · membership — never file contents — identity only your laptop ~/work/design your desktop ~/work/design file contents: direct, encrypted hole-punched through NATs, never relayed
The split is the design: contents stay between your devices; the service only knows who’s who.
01

Why YadoriLink?

Your files take the direct path

Contents move straight between your devices over an encrypted WireGuard-protocol tunnel — no detour through someone else’s storage, and no relay in the middle. On the same network, devices find each other locally and sync without touching the internet; across the internet, they punch through home routers and connect directly.

Nobody can read your files — including us

The hosted service only knows who you are and which of your devices hold which folders. It never receives file contents, so a breach, subpoena, or curious operator has nothing to read. Every line that touches your files, keys, and the wire protocol is open source, so you can check.

Store everything, or only what you open

Give a folder every byte on a device, or keep it on-demand — placeholders that fetch the real file the moment you open it and can be evicted to reclaim space. Chosen per folder, per device.

The same sync everywhere

macOS, Windows, or Linux — it’s the same engine making the same decisions, so two machines never disagree about how a conflict resolves just because they run different operating systems.

Automate anything

Everything the app does can also be scripted — link a folder from a cron job, check status in CI, drive it headless on a NAS. The GUI is for everyday; the CLI is there when you want it.

Tested against data loss

The sync engine is exercised by deterministic simulation testing — seeded chaos runs that check no edit is ever silently lost — because losing your edit is the one unforgivable sync bug.

02

How is this different?

Peer-to-peer sync isn’t new — Syncthing and Resilio already replicate folders with no cloud storage of contents, and Dropbox already does frictionless account and device management with cloud storage. YadoriLink aims at the combination:

YadoriLinkDropboxSyncthing
Easy account and device management✓ Yes✓ Yes— No
File contents never stored on a server✓ Yes— No✓ Yes
On-demand files that fetch on open✓ Yes✓ Yes— No
Open-source sync, transport, and encryption stack✓ Yes— No✓ Yes
03

Trade-offs, by design

no cloud copy
If every device in a share is offline, syncing waits until one comes back. There is no third place holding your files — that’s the point, and it’s also the constraint.
your bandwidth
First syncs move real bytes between your machines, so speed depends on your devices’ connections — not a datacenter’s.
no relay
Devices connect directly, punching through most home and office NATs. A few strict networks — both peers behind symmetric NAT — may never form a direct path; there is no operator relay to fall back on, so those two wait for a friendlier network instead.
04

Status

YadoriLink is pre-1.0. What works, and what’s missing:

  • CLI + daemon are the longest-exercised core; the app drives the same daemon the CLI does.
  • Desktop app takes you from sign-in to your first linked folder entirely in a GUI wizard; day-to-day status and controls live in the tray.
  • Builds are unsigned. Expect Gatekeeper and SmartScreen warnings; the macOS Finder integration ships as raw binaries. Signed & notarized installers are on the beta path.
  • Windows Explorer integration runs on x86_64; arm64 is untested.
  • Toward beta — signed installers, a versioned beta channel with staged rollout and a remote kill-switch, account deletion & data export, a public status page, and crash reporting. The designs are settled; implementation lands in that order.
05

Get started

1. Download and install — prebuilt from GitHub Releases (nightly):

linux .deb package yadorilink-linux-amd64.deb windows installer yadorilink-setup.exe macos binary tarball yadorilink-macos.tar.gz

These builds are for testing and early feedback. Windows builds are unsigned, so SmartScreen warnings are expected; macOS builds are unsigned and not notarized. Checksums (SHA256SUMS) ship alongside the artifacts.

2. Open the app and sign in — the setup wizard walks you from Google sign-in through device registration to your first share: a folder kept in sync across your devices. Create one, or join an existing one from a new device. Install and sign in on a second machine the same way, and syncing begins.

Prefer a terminal? The same setup is five commands (the installer puts yadorilink on your PATH):

$ yadorilink daemon start
$ yadorilink login
$ yadorilink device register --name "my-device"
$ yadorilink share create my-share --path ~/some/folder
$ yadorilink status

Prefer building from source? cargo build --workspace --release — see the README.