English
Syncthing Hosting
Sync files continuously between your own devices, with no third party holding a copy.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Syncthing’s official links and original website
Syncthing Website
More
Tech
- Docker image
- syncthing/syncthing:latest
- Default port
- 8384
How Syncthing works
Syncthing connects devices through cryptographic identities and shares only the folders that an administrator authorises. Each participating device keeps its own copy, and changes are exchanged when peers can communicate. Discovery and relay services can help devices find one another or traverse difficult networks, but file contents remain part of the device-to-device synchronisation process.
Folder modes control whether a device sends and receives changes, only sends, or only receives. File versioning is disabled by default; after an administrator selects a policy, it can retain replaced or deleted files. Conflict files may appear when incompatible edits happen on separate devices, so users still need clear ownership for frequently modified documents.
Key Syncthing features
The web interface manages device identities, folder paths, sharing relationships, transfer status, errors, and versioning settings. Ignore patterns exclude files that should not travel to another device, while bandwidth controls and scan intervals help tune behaviour for the connection and workload.
Syncthing is a synchronisation system, not a substitute for an independent backup. A deletion, encryption event, or unwanted edit can propagate to peers. Versioning reduces some risk, but important data still needs a separate backup that is protected from ordinary synchronisation actions.
Syncthing vs Resilio Sync
Syncthing is a community-developed peer-to-peer file synchronisation application with a local web interface and open device-sharing model. Resilio Sync uses peer-to-peer transfer technology in commercial products that include managed plans and centralised administration options for business use.
Resilio Sync may suit organisations that want vendor support, policy management, and commercial deployment tooling. Syncthing is a strong fit when participants want a self-hosted, community-maintained synchronisation service and are comfortable managing device approval, folder topology, versioning, and recovery procedures themselves.
Who uses Syncthing
Individuals use Syncthing to keep working folders consistent across desktops, laptops, and home servers. Small teams replicate project files between trusted systems, while administrators use receive-only targets to collect copies from selected devices.
The tool is less suitable for browser-first document collaboration or public file sharing. Every useful participant normally runs a Syncthing client and maintains a local folder copy. Storage planning must therefore account for what the hosted node is expected to retain, not just the metadata shown in the interface.
Self-hosting Syncthing: requirements and cost
Storage volume is the dominant plan constraint, followed by file count, database indexing, hashing, scanning, transfer activity, version history, and simultaneous peers. PostgreSQL and MariaDB are Not required. The catalogue publishes the management interface on port 8384, while direct Syncthing traffic normally uses TCP or QUIC port 22000. Because that dedicated sync port is not published by the template, direct inbound reachability must be tested and relay connections may be used.
The mapped minimum is Plan 1 at €2. Storage is the real limit here — 50 GB on Plan 3 is a realistic starting point for an active shared folder, while 100 GB on Plan 4 better suits a larger retained copy or version history. AvaHost includes one-click deployment, custom-domain HTTPS for the web interface, automatic application updates, and scheduled backups.
F.A.Q
Syncthing starts at €2 on Plan 1, which is appropriate for testing or a small replicated folder. The amount of retained data is usually more important than interface traffic. File count, hashing, scans, transfer volume, peers, versioning, and temporary changes should be measured before deciding whether the node needs more processing or storage.
Plan for the full folder copy the AvaHost device will retain, plus version history and temporary overhead. Plan 3 supplies 50 GB as a practical starting point for an active folder, while Plan 4 supplies 100 GB for a larger copy. Other devices also keep their own data, so total replicated capacity exists in several places.
The custom domain and automated HTTPS apply to the Syncthing management interface on published port 8384. Device synchronisation normally uses TCP or QUIC port 22000 rather than the browser hostname alone. Because the template does not publish that dedicated sync port, verify direct connectivity, relay status, folder health, and transfer performance separately before depending on the hosted node.
Synchronisation and backup solve different problems. Deletions, unwanted edits, or encrypted files can propagate between peers, so a healthy sync status does not prove a recoverable historical copy exists. Syncthing versioning can retain selected older files, while AvaHost scheduled backups add another recovery layer; important data still needs a tested restoration plan.