Nextcloud vs Syncthing: when a central server is the right choice
Nextcloud suits organizations that need a central server with web access, sharing links, directory sign-in and apps, while Syncthing suits a small set of trusted devices that sync directly with no server. The question for a team deciding where shared files live is not which tool is better in the abstract. It is whether the files need a place that people outside the device group can reach, and whether someone in the organization must administer who has access and what happened to it.
The decision turns on three requirements. First, whether external users such as partners, customers or auditors need to receive files through sharing links, which Syncthing does not provide for external sharing. Second, whether central audit and administration are required, meaning one place to see accounts, shares and activity and to disable a user without touching every laptop. Third, whether identity integration is required, such as LDAP or Active Directory users signing in with their directory credentials, which the Nextcloud LDAP documentation covers. If none of these apply, a peer-to-peer model may be enough.
The last question is whether the team will run a server at all. Nextcloud needs a web server, PHP, a supported database and a regular upgrade routine, and the upgrade docs require moving one major version at a time with a backup before each step. Syncthing has no central server to patch, but every device must be kept online or reachable and managed individually. Confirm who will own patching, backups and device enrollment before choosing, because that ownership, not the feature list, usually decides the outcome.
Nextcloud vs Syncthing by scenario: which fits which team
This table maps common team situations to the platform that usually fits better, based on how each one stores, shares and secures files. Read each row as a starting point, then confirm the points marked for checking against your own identity, network and compliance requirements.
| Scenario | Better fit | Reason tied to supplied facts |
|---|---|---|
| Staff across several sites who need browser access | Nextcloud | Nextcloud is a central server with a web interface, so staff can reach files from any browser. Syncthing is managed through its own web interface on each device and has no central place to browse files. |
| Sharing files with outside partners | Nextcloud | Nextcloud supports sharing links for people outside the organization. Syncthing only connects devices a user has explicitly allowed, so it cannot serve external partners who do not run Syncthing on their own machines. |
| Small group syncing their own laptops and phones | Syncthing | Syncthing keeps data only on the user's own computers, uses TLS with perfect forward secrecy between approved devices, and needs no server to run. For a small peer group this removes a server to operate. |
| Regulated team needing central administration and sign-in control | Nextcloud | Nextcloud documents LDAP and Active Directory login, plus OpenID Connect and SAML authentication backends. Syncthing has no central server for administrators to manage users, so confirm whether device approval and key handling meet your access review needs. |
| Field or offline-heavy team that syncs between devices | Syncthing | Syncthing syncs directly between devices over a LAN or the internet without IP configuration. Confirm that each device stays online often enough for changes to reach its peers, since no central server holds a copy. |
| Teams that need an audit trail of who accessed a shared file | Nextcloud | Central server placement lets administrators review sharing and access in one place. Syncthing has no central record of access, so confirm what logging each device provides before relying on it. |
| Organization that needs both browser access and device-level sync | Both | Teams often run Nextcloud as the shared, browsable and externally shareable store, and Syncthing for direct device-to-device sync of working folders. Confirm the folder mapping and which copy is the authoritative version. |
How each platform is built and what that means for operations
Nextcloud is a central server that your team runs, patches and backs up, with users reaching it through a browser, apps and sharing links. Syncthing has no server at all: files move directly between approved devices, so the operational burden shifts to device management and to confirming that copies exist where you need them.
Nextcloud as a central PHP service
Nextcloud Server is a PHP application that needs a web server (Apache 2.4 or nginx with php-fpm), a supported database and, optionally, caching and office integrations. Nextcloud 35 supports PHP 8.3 to 8.5 and databases including MariaDB, PostgreSQL and MySQL. Each of these components is a version your team must match and keep current. Confirm which database and cache your team can operate before choosing a layout.
Syncthing's peer-to-peer design
Syncthing keeps no central copy of your data. Each device syncs directly with the other devices you have approved, and all communication is protected with TLS, including perfect forward secrecy. There is no server to patch, but there is also no central place to check whether every device has a current copy. Plan for that gap in your own monitoring.
Device identity and access control
In Syncthing, every device is identified by a strong cryptographic certificate, and only devices you have explicitly allowed can connect. Adding a laptop, replacing a phone or removing a departing employee means changing trust on each device that shares a folder. Nextcloud instead ties access to user accounts and directory integrations such as LDAP. Ask who will own device enrollment and revocation in your team.
Upgrades and maintenance workload
Nextcloud requires one major version at a time and backups before every upgrade, and third-party apps should be disabled until confirmed compatible. Nextcloud 35 was released on 16 September 2026 with support until September 2027. Syncthing has no server upgrade path, but each device runs its own client, so version drift across laptops and phones is the risk to track.
Backups and recovery responsibility
Syncthing states that none of your data is stored anywhere other than your own computers, so a copy on every device is not a backup policy. Deleting or corrupting a file can propagate to other devices. Confirm with your team how versioning, offline archives and restore testing will work. For Nextcloud, confirm how the database and the data directory are backed up together so they stay consistent.
Where data lives in each model
With Nextcloud, data sits on the server you operate, in its data directory and database, and users read it through the web or sync clients. With Syncthing, data sits on each approved computer, and no third party holds a copy. This determines where you must place backup targets, how you respond to a lost laptop and which regulated data may sit on endpoints. Confirm your data classification rules before deciding.
Nextcloud vs Syncthing feature by feature
This table compares how Nextcloud and Syncthing differ on licensing, architecture, access, security and release cadence. Read each row as a question about your own requirements, and treat the rows on external sharing and identity as items to confirm with the vendor before you decide.
| Capability | Nextcloud | Syncthing |
|---|---|---|
| License | AGPL-3.0 for the server, with Nextcloud GmbH selling an Enterprise subscription | Mozilla Public License 2.0 for all of its code |
| Server requirement | A central server running PHP with a supported database such as PostgreSQL, MariaDB or MySQL | No central server; devices sync directly with each other |
| Web access | Browser interface served by the Nextcloud instance | Managed through a web interface on each device |
| Sharing links for external people | Supported as a core server capability; confirm the exact link and expiry options in your version | Not covered by the supplied facts; confirm with the Syncthing project before relying on it |
| Identity integration | LDAP and Active Directory login, plus OpenID Connect and SAML backends documented | No user accounts; trust is set by device certificates, so confirm any directory integration with the project |
| Transport security | Served over the web stack you configure for your server | All communication secured with TLS, including perfect forward secrecy |
| Device trust model | Users and sessions authenticate against the server | Each device has a cryptographic certificate and only explicitly allowed devices can connect |
| Apps and extensibility | Large app ecosystem for files, office, chat, calendar and more | Focused on file synchronization; extend through its configuration and Docker deployment |
| Supported platforms | Server runs on Linux stacks with PHP; clients for desktop and mobile | macOS, Windows, Linux, FreeBSD, Solaris and OpenBSD, plus a Docker image |
| Current release | Nextcloud 35.0.2, 34.0.5 and 33.0.10 published on October 15, 2026 | Syncthing v2.1.6, published October 6, 2026 |
Licensing and editions: what is free and what is paid
Nextcloud Server is licensed under AGPL-3.0, so a team can run the community server without a license fee. Contributions from 16 June 2016 onward are offered under AGPLv3 or any later version, and the Nextcloud server repository is where the license and contributor terms are published. Nextcloud GmbH sells Nextcloud Enterprise alongside that community code. The subscription adds support and maintenance terms, and the code stays AGPL either way.
- Community server: No per-user fee applies to running the AGPL server. Your costs are infrastructure, administrator time and any outside help you buy.
- Enterprise tiers: Standard, Premium and Ultimate are sold per user per year. The Nextcloud pricing page lists starting rates of 71.29, 104.99 and 204.75 euros for 100 or more users.
- 100-user minimum: The Enterprise subscription carries a 100-user minimum, so smaller teams cannot buy it on the same terms.
- Tier differences: Standard includes 1-year maintenance. Premium adds a maintenance lifecycle of 5 or more years, extended support hours and clustered instance support. Ultimate adds support up to 24/7 with response times down to 1 hour.
- Volume rates: Lower per-user rates apply from 200 users.
Check the current prices, currency and tier terms on the pricing page before budgeting, since list prices can change and negotiated quotes may differ.
Syncthing's code is licensed under the Mozilla Public License 2.0, as stated in its GitHub README. The supplied material does not name a paid edition, an enterprise tier or a per-user subscription for Syncthing, so the licensing picture is the open-source project itself. Official project information is on the Syncthing website, and any commercial arrangement you consider should be confirmed with its provider in writing.
- License terms: MPL 2.0 applies to Syncthing's code. It is a file-level copyleft license, so changes you make to Syncthing's own files carry obligations to share those files. Have counsel confirm how this applies to any modifications you plan.
- No named paid edition: The facts available do not identify an Enterprise edition, a subscription or a license fee for Syncthing.
- Commercial support: Whether support contracts exist, and what they cover, is not established here. Ask any provider for response commitments, covered versions and the scope of work.
- Cost components: Without a license fee, cost is the devices you run, the time your staff spend on rollout and any support contract you negotiate.
- Recurring costs: Device upkeep and operator time recur. A support contract, if you buy one, also recurs.
Before approval, confirm in writing whether any support or enterprise arrangement exists and what it covers, and do not assume one exists.
The two options price differently. Nextcloud's community server costs nothing to license, but a subscription is priced per user, so the quote depends on tier, user count and term. Syncthing has no license line to quote, so the comparable budget is the operating cost around it. Build both estimates on the same basis so the decision compares like with like.
- Seat count: Confirm whether your user count clears the 100-user minimum and how the vendor counts users across tiers.
- Term and currency: Ask whether euro list prices convert to your billing currency and which term the quote covers.
- Lifecycle dates: For Nextcloud, ask for the maintenance end date of the tier and the major version it covers, and check it against the Nextcloud release schedule.
- Hosting and staff: Budget infrastructure and administrator time for both products, since neither option removes those costs.
- Support scope: For Nextcloud, confirm response times per tier. For Syncthing, obtain written scope from any provider you consider.
Request each quote in writing with the tier, users, term and covered support named, so both options are costed on the same basis.
What Syncthing cannot do for external sharing
Syncthing has no concept of a sharing link for someone outside the organization. It replicates folders between devices that a user has explicitly approved, and every device is identified by its cryptographic certificate. An external partner, customer or contractor who has no approved device has nothing to connect to, and Syncthing offers no public URL, password-protected link or guest account that would let them retrieve a file without that device exchange. If external access is a requirement, confirm that the people who need files can each run an approved Syncthing device, and ask who will manage those device IDs over the life of the engagement. Nextcloud, by contrast, is built around a central server with web access and sharing links, which is the capability Syncthing is designed to leave out.
Audit is the second consequence. Syncthing keeps data on the computers that hold it and replicates changes between them, but it is not a central record of who opened or downloaded which file. Each peer can see that a device connected and that files changed, yet a regulated team that must show access history for a file shared with an outside party should not assume that a peer-to-peer model produces that evidence. Before rollout, write down the access-evidence questions your auditors or customers will ask, then test what each device actually logs in your environment. Confirm the answers with the vendor's current documentation rather than relying on assumptions about what a peer records.
User lifecycle is the third. Access in Syncthing is granted device by device, so offboarding a person means removing their devices from every shared folder on every peer that trusts them, and confirming that no copy remains on a device you no longer control. There is no single directory-backed account to disable. Teams that pair Syncthing with a server platform for external work usually keep Syncthing for internal replication between their own machines and let the server handle outside accounts, expiring links and central revocation. Plan that split at the start, and note that these conditions only matter when external access is required. For teams with purely internal sync, Syncthing's device model may be the simpler fit.
Moving from one to the other or running both
This sequence shows a team how to move files between Syncthing and Nextcloud, or run both, without losing data or trust boundaries. Each step ends with a check that confirms the previous step held before the next one starts.
Inventory folders, devices and users before moving anything
The team lead and the platform owner list every synced folder, which devices hold a copy, who owns each folder, and which people need access after the move. For Syncthing, record each device ID and the folder IDs it shares. For Nextcloud, record the users, groups and any external sharing links that exist today. Keep this list in a document the security team can review. The step is done when every folder has a named owner, a size estimate taken from the devices themselves, and a decision on whether it moves, stays in Syncthing, or is retired.
Confirm the Nextcloud target and upgrade path
The platform owner checks the Nextcloud version to deploy against the current system requirements and the release schedule, then confirms the database and PHP versions the target supports. If the team plans to load data into an older major line, the owner must confirm that it can reach the target version one major release at a time, because Nextcloud does not allow skipping major releases during upgrades. Ask the vendor or your partner to confirm this path for your environment. The step is done when a written version plan exists and the owner has confirmed it against the official documentation.
Build the Nextcloud instance and identity links
The platform owner deploys Nextcloud in the team's own infrastructure and connects it to the directory or identity provider the organization uses. If sign-in will use LDAP or Active Directory, the administrator configures the LDAP app so directory users can log in with their existing credentials. Groups and quotas are set up before any data arrives. The step is done when a pilot user can sign in with directory credentials, and an administrator confirms that group membership and quotas match the inventory.
Copy files and rebuild folder structure
Files transfer as ordinary data, so the team copies each approved folder from a Syncthing device into a Nextcloud folder or shared space, keeping the folder tree the same. Syncthing does not hold permissions, so every share, group assignment and link must be created again in Nextcloud. Run a checksum or file count comparison between the source device and the target. The step is done when the comparison matches for every folder in scope, and the exceptions list is written down with an owner for each one.
Rebuild shares, permissions and sync rules
Syncthing trust does not carry over. Each Syncthing device the team wants to keep, such as a laptop or a server, must be paired again with a Nextcloud sync client account. The owner sets folder-level permissions, share targets and any external sharing links in Nextcloud, since Syncthing cannot provide external sharing. Ignore patterns from Syncthing are reviewed and recreated as client-side exclusions where needed. The step is done when a test user on each device can see the expected folders and cannot see restricted ones.
Cut over users and retire peer links in stages
The team moves one group at a time. For each group, users stop writing to the Syncthing folder, the final sync is confirmed, and users start using Nextcloud. Syncthing folders are paused, not deleted, for a fixed observation window that the team sets. Remove a device from Syncthing only after its owner confirms the data is present in Nextcloud. The step is done when each group has signed off and the device list in Syncthing matches the approved set.
Plan backups and confirm the upgrade routine
Before any future Nextcloud upgrade, the platform owner takes a backup and disables third-party apps until each is confirmed compatible, following the upgrade manual. The backup covers both the database and the data directory. Syncthing copies kept for recovery are documented as a separate tier. The step is done when a restore test has been run on a non-production copy and the upgrade runbook has been reviewed by someone other than its author.
Run both platforms with a written boundary
Teams that keep both tools set a written rule for which data lives where, such as personal peer-synced working folders in Syncthing and shared or externally shared content in Nextcloud. The owner reviews the boundary at a set interval and records who can add a device to Syncthing. The step is done when the rule is in the team's documentation, every synced folder is mapped to exactly one owner, and the review date is on the team calendar.
What implementing each involves and where projects run long
A Nextcloud rollout is a set of linked decisions, and most of the delay comes from making them in the wrong order. The server build and the database choice come first: Nextcloud 35 supports MySQL 8.4 or 9.7, MariaDB 10.11 to 12.3 and PostgreSQL 14 to 18, and the official recommendation is MariaDB 11.8 or PostgreSQL 18. Directory integration follows, usually through the LDAP app for Active Directory, with OpenID Connect or SAML as alternatives. Storage, backups, the choice of web server and the app set complete the design. Confirm with your identity team how group membership maps to Nextcloud groups before pilot users log in, because changing that mapping later touches permissions on every share.
Upgrade planning is the element teams most often skip. Nextcloud does not allow skipping major releases, so each upgrade must go one major version at a time, with a backup taken first and third-party apps disabled until they are confirmed compatible. Build a test instance from a recent backup and run the upgrade there before production. A Syncthing rollout is different in kind: the work sits on endpoints rather than a server. Folder design, meaning which directories become shared folders and which devices hold them, determines who can see what, so decide it before enrolling laptops. Each device must be added and trusted on every peer it should sync with, and the device ID exchange is a manual step your support desk must own.
Syncthing's own model creates the hardest operational questions. Because there is no central server, a device that is offline holds changes that other peers cannot see until it returns, and conflicting edits produce conflict copies that someone must resolve. Plan for laptops that stay asleep for weeks, for replacement devices that need new trust, and for a departing employee whose device still holds a copy of shared data. Ask whether any deployment will run an always-on Syncthing node for coverage, and who administers it. Projects also run long when the team discovers that users need external sharing, which Syncthing does not provide, and the Nextcloud rollout starts late. Settle that requirement with the business before either project begins.
Nextcloud vs Syncthing: questions buyers ask before hiring help
What does implementation work cost, and what drives the price up?
The cost depends on the written scope, which DeployOpen agrees with you before work starts, so there is no public price list and no figure to quote here. The main cost drivers are the number of users and devices, whether Nextcloud must join Active Directory or another identity provider, how many external sharing and office integration requirements you have, the storage design, backup and restore testing, and whether you need hardening or compliance evidence. Ask for a quote that separates one-time work (design, installation, integration, migration, documentation) from recurring work (upgrades, monitoring, retained testing). If you also license Nextcloud Enterprise, that subscription is a separate, recurring cost paid to Nextcloud GmbH. Syncthing itself carries no license fee because it is open source under MPL 2.0.
How long does a typical Nextcloud rollout take?
No duration figure is supplied for this comparison, so confirm timelines against a written scope rather than a generic estimate. The timeline is set by the number of user groups, the directory and SSO work, the size of any data migration from existing shares, how many apps you enable, and the backup and recovery tests you require before go-live. A Nextcloud major release also has a lifecycle to plan around: Nextcloud 35 was released on 16 September 2026 with end of life in September 2027, and Nextcloud 36 is scheduled for 17 February 2027 (Nextcloud maintenance and release schedule). Upgrades must go one major version at a time, so plan the upgrade cadence into the timeline from the start.
What does our team need to provide before implementation starts?
Plan to supply four things: people, directory access, storage and backup targets. People means a named business owner, an administrator who will receive handover, and a network or DNS contact for the public hostname and TLS certificates. Directory access means a service account and LDAP or Active Directory details if users should sign in with existing credentials, which Nextcloud's LDAP app supports (Nextcloud LDAP docs). Storage means a sized volume or object store for user data, plus a database platform from the supported list in the Nextcloud 35 system requirements. Backup targets mean a location and retention policy that you own, tested with a restore before go-live. Confirm the exact sizing and database choice with your own environment.
Can our own team run Nextcloud or Syncthing without outside help?
Yes, many teams run both without an implementation partner, and the question is whether your staff have capacity for the work that recurs. Syncthing is lighter to operate because each device runs the software and there is no central server to patch, though you still manage device approvals, folder sharing and client versions. Nextcloud is a server platform, so it needs ongoing web server, PHP, database and backup operations, plus upgrades that move one major version at a time with a backup before each step and third-party apps disabled until confirmed compatible (Nextcloud upgrade manual). If your team has no one who will own those upgrades, a retainer or a handover plan should be part of the scope.
Can Syncthing replace a file server for external partners?
Not on its own. Syncthing is peer-to-peer and syncs folders only between devices you have explicitly approved, so an outside partner would need to run Syncthing and be added as a device. Syncthing has no central server, no web sharing links and no per-partner web access, so it cannot issue a link to a file or give an external user a browser-based workspace. Use Nextcloud for external sharing with links, guest access and web use, and keep Syncthing for trusted devices that need to replicate folders. Confirm any partner requirement, such as revocation or audit logging of external access, against the feature set in your own tests.
Is it sensible to run Nextcloud and Syncthing together?
Yes, when the two tools cover different jobs. A common pattern, illustrative only, is to keep Nextcloud as the central record for shared documents, sharing links and web access, while a small group of trusted workstations uses Syncthing to keep a working folder in step between their own machines. The risk is two copies of the same data with no clear owner, so define which location is authoritative and what happens to conflicting edits. Syncthing's design keeps data only on your own devices, which helps with data residency, but it does not replace Nextcloud backups. Both tools need their own backup thinking, and the combined design should be written down before rollout.
Does Syncthing's security model satisfy our compliance or data handling review?
Syncthing's security model is well described, but a model description is not a compliance result. Syncthing states that all communication is secured with TLS including perfect forward secrecy, that every device has a strong cryptographic certificate, and that only devices you explicitly allow can connect (syncthing.net). It also states that no data is stored anywhere other than your own computers. Those points help with a review, but they do not replace evidence from your own environment, such as device inventory, access approvals, encryption at rest on each endpoint and logs. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports or certifications, so independent auditors or certification bodies make the final determination.
How DeployOpen helps you choose, implement or migrate
DeployOpen works through Nextcloud vs Syncthing as a written, fixed-scope engagement inside your own infrastructure. We start from the data, devices and external sharing needs that decide between a central server and peer-to-peer sync, then build, document and hand over only what the agreed scope covers.
How we scope
- Map which folders need sync only between your own approved devices and which need links for external users.
- Record the device inventory, operating systems and user count that determine whether Syncthing alone is enough.
- Agree in writing whether a Nextcloud server, a Syncthing deployment or both are in scope before any work starts.
How we build
- Install and configure a self-hosted Nextcloud server in your cloud account, data center or air-gapped network, with your chosen database.
- Set up Syncthing device pairing, folder rules and TLS-secured device identities on the endpoints you approve.
- Test sharing links, sync behavior and access controls against the requirements recorded during scoping.
How we hand over
- Deliver written documentation covering configuration, device approval steps, backup approach and the upgrade path for each platform.
- Walk your administrators through daily operations, user onboarding and the limits of peer-to-peer sync for external sharing.
- Provide the evidence and configuration records your internal or independent assessors need for review.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Retainers can cover Nextcloud major-version upgrades, which must be taken one major version at a time with backups first.
- Ask us to confirm the support scope, response expectations and upgrade responsibilities in the written quote before work begins.
