How to Self-Host Syncthing
Syncthing continuous peer-to-peer file synchronization with encrypted transport, device approval, versioning, discovery, and no central cloud service. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Syncthing is a good fit
Choose Syncthing when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install Syncthing on each device, protect the administration interface, exchange device IDs deliberately, and choose send, receive, or two-way folder modes.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Enable file versioning where rollback matters and keep an offline backup because synchronization also propagates deletions and corruption.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Synchronization is not automatically a backup; validate folder direction and ignore rules before connecting a large existing tree.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
