Why an always-on peer can help
Syncthing transfers data when the relevant devices can communicate. If a laptop and desktop are rarely online together, changes may wait. An always-on peer can receive a change from one device and later make it available when another device reconnects.
The always-on peer is still one device in the Syncthing topology. Folder types, device trust, versioning, discovery, relays, conflicts, and connectivity continue to determine behaviour.
How onboarding works
- Add the device: pair the managed node with your existing Syncthing setup and explicitly approve the relationship.
- Share selected folders: include the managed node only in folders where an always-on offsite peer helps.
- Keep the rest unchanged: Syncdingo keeps the node available while you continue to control device trust, folder membership, passwords, local peers, and backups.
The exact onboarding flow, capacity limits, recovery procedures, and support model will be documented for invited participants before beta access.
Choose folders instead of migrating everything
A Syncthing device participates only in folders shared with it. Syncdingo works within that existing boundary: important documents or configuration folders can include the managed node while bulk media or local-only folders stay elsewhere.
You can keep direct device connections, a NAS, or another VPS alongside Syncdingo. The managed node complements the topology you already control.
Syncthing encrypted-device mode
Syncthing lets a trusted device use a folder password when sharing with an untrusted device. Data sent to that device is encrypted using the password and folder ID. Syncthing currently labels encrypted devices beta/testing only.
According to the current Syncthing documentation, file data, file metadata including names, times and hashes, and directory structure are protected on the untrusted device. Folder ID, folder label, and file sizes are not protected. Network-level information can remain observable through discovery, relays, addresses, and traffic patterns.
Keep the folder password and folder ID securely and independently. The documented decryption process requires the password, and losing the necessary recovery material can make the encrypted copy unusable.
Receive-only folders and file versioning
A receive-only folder can help prevent ordinary local edits on a destination from being treated like normal synchronised changes, but it does not create immutable history.
Syncthing file versioning is configured per folder and per device and defaults to no versioning. When enabled, it can archive a file that is deleted or replaced because of a change received from another device. It does not archive an old version when that same device changes the file locally.
What remains your responsibility
- Approving device identities and choosing shared folders.
- Protecting Syncthing folder passwords and recovery material.
- Securing trusted local devices and their Syncthing configuration.
- Choosing folder types and understanding deletion and conflict behaviour.
- Keeping independent backups appropriate to the value of your data.
- Deciding whether a managed node or DIY infrastructure is the better trade-off for you.
Current private-beta scope
The initial private beta focuses on managed always-on peer behaviour, selective folder participation, encrypted-device operation, and day-to-day reliability. Syncdingo snapshots, point-in-time restore, and service-level guarantees are not part of the current scope. Pricing and access terms will be provided before invited participants choose whether to accept access.