Self-hosted file sync and share in 2026: revisit Nextcloud, Seafile and OpenCloud before you move another shared drive

Most Indian companies of a few hundred people have the same file story: an old Windows file server with mapped drives that only work in the office, personal Google Drive accounts used by the sales team on phones, and pen drives and large email attachments that nobody can track. Then one day somebody says, “Let us host our own Dropbox, Nextcloud is free”, and a test server appears on a spare VM. Nobody has asked how the files will be backed up, who can create public links, or what happens when the person who set it up leaves.

This post is written for that day. A file sync server looks like a folder in the browser, but underneath it is a storage layout, a metadata store, a sync protocol, sharing rules, a search index, previews, mobile apps and an upgrade path. The software decides how many of those parts you own. It does not decide who is allowed to share what. That part is yours.

We revisit three self-hosted options in 2026: Nextcloud (a PHP application on MySQL, MariaDB or PostgreSQL, which has grown from file sync into a full collaboration suite), Seafile (a C and Go file server with a Django web front end, built around libraries and a Git-like storage model) and OpenCloud (a Go server with no database, forked in 2025 from ownCloud Infinite Scale, that keeps files and metadata on a POSIX filesystem). We also look at where ownCloud itself stands, because many old installations still run it. The aim is not to pick a winner but to see what each asks of you over five years.

There is plenty of news this autumn. Nextcloud released Hub 26 Summer, which is server version 35, on 16 September 2026, with a new Teams app, redesigned Photos and an office app now powered by Euro-Office; maintenance releases 35.0.2, 34.0.5 and 33.0.10 followed on 15 October. Seafile Community Edition 13.0.28 came on 18 September 2026 with a fix for a permission problem in read-only library API tokens, and a 14.0 beta is in testing. OpenCloud shipped rolling release 9.0.0 on 27 October 2026 with passwordless guest access by email, after adding end-to-end encrypted “vaults” in 7.5.0 in August; its current production line is 7.2, and its lifecycle page dates the next production release for 17 November 2026. On the ownCloud side, the classic PHP server reached 11.0.0 on 30 July 2026, and ownCloud Infinite Scale shipped 8.2.2 on 21 October with a 9.0 release candidate in testing. ownCloud has been part of Kiteworks since the acquisition closed in December 2023.

This post stays with file sync and share for a company’s own staff and its partners. For the pieces around it, see Keycloak and its alternatives for single sign-on, reverse proxies in 2026 for the front door, and backups in 2026 for the copy you will need on a bad day. If your real problem is object storage for applications, MinIO and its alternatives is the better starting point.

A scenario to keep us honest

We will use one invented company through the post. Bhavani Riverside Home Textiles is an invented example, not a real business: an Erode company that designs and exports bed linen, towels and kitchen textiles to buyers in Europe and Australia, with its own weaving and a network of job-work units around Erode and Karur. The company has about 210 people. About 70 work in the office: design, merchandising, export documentation, accounts and purchase. About 25 merchandisers and quality staff travel to job-work units and buyer meetings and work mostly from phones. The rest are on the shop floor and do not need file access. IT is two people, led by Karthikeyan, with an outside vendor for hardware.

What they use today:

  • A Windows file server in the office with mapped drives for Design, Merchandising, Export Docs and Accounts. The server is old, and the operating system is past its support date. Access works only inside the office or over a fragile VPN.
  • Company mail on Google Workspace, but merchandisers share tech packs, artwork and photographs with buyers from personal Google Drive accounts, some belonging to people who have left.
  • Large design files of a few hundred megabytes each, with many versions, copied to pen drives to work from home.
  • A Proxmox host with spare capacity, a 200 Mbps fibre line with a static IP, a smaller backup line, and a NAS with nightly copies of the file server.

What triggered the review: a large European buyer sent a supplier security questionnaire asking where design and order files are stored, who can access them, how access is removed when staff leave, and whether shared links expire. In the same month, a nearby company lost a week of work to ransomware on its file server. A young developer suggested Nextcloud because “it does everything, even chat and calendars”. The merchandising head asked for “something like Google Drive, but ours”.

Karthikeyan’s questions: which server, what do free editions allow for about 95 users, how do sync and phones work for large files, how do we control links to buyers, and can two of us own it for five years?

The short version

  • Decide folder structure, sharing rules and backups before software. A sync server makes files easier to reach from anywhere. If today’s permissions are messy, it makes the mess reachable from anywhere too.
  • Nextcloud is the broadest: files plus calendars, contacts, Talk, office editing, Tables, an AI assistant and hundreds of apps. Major versions arrive every four months and each gets one year of maintenance. It needs the most care: PHP, a database, Redis, background jobs and app compatibility at every upgrade. Push through Nextcloud’s servers is free only up to 500 users.
  • Seafile is the most focused on fast, reliable sync of many and large files. Files are split into blocks and stored in a Git-like model with library history, which is efficient but means the files on disk are not plain files. Community Edition 13 is AGPL and Docker only. Full-text search, audit logs, fine-grained folder permissions, clustering and S3 storage are listed as Professional Edition capabilities, and Pro is free for up to three users.
  • OpenCloud is the newest and lightest to run: one Go binary, no database, files kept as plain files on a POSIX filesystem with metadata in extended attributes, OpenID Connect built in. It moves fast, with rolling releases every three weeks and production releases about every six months. Some of its newest features, such as encrypted vaults and guest access, are so far only in rolling releases.
  • ownCloud still ships both the classic PHP server and Infinite Scale under Kiteworks. If you run it today, it is patched, but plan your next move with eyes open.
  • For Bhavani Riverside, our plan is: clean up shares and write link rules first, then pilot Seafile Community Edition 13.0 with 40 users from design and merchandising on a VM with 4 vCPU and 8 GB of RAM, with sign-in through company Google accounts and a tested restore. If the buyer questionnaire needs audit logs or subfolder permissions, get a Seafile Pro quote for the full user count. Nextcloud is the choice only if they also want calendars, office editing and chat in one place. OpenCloud goes on a watch list for 2027, to evaluate on a production release.

Where things stand on 2 November 2026

Nextcloud

  • Current releases: 35.0.2, 34.0.5 and 33.0.10 on 15 October 2026. Version 35 is Hub 26 Summer, released 16 September 2026, with end of life planned for September 2027. Versions 34 and 33 are supported to June 2027 and February 2027. Version 32 reached end of life in September 2026 with 32.0.15 as its last release. The next maintenance release, 35.0.3, is scheduled for 12 November 2026.
  • Release rhythm: the release schedule says new major versions are published every four months and supported for one year through monthly maintenance releases. Version 36 is planned for 17 February 2027. The system requirements page says a premium subscription offers five years of long-term support.
  • What is new in 35: a Teams app with team-owned storage, redesigned Photos, channels in Talk, and an office app now powered by Euro-Office, with Collabora still available as an integration.
  • Requirements for 35: PHP 8.3, 8.4 or 8.5 (8.5 recommended); MySQL 8.4 or 9.7, MariaDB 10.11 to 12.3, or PostgreSQL 14 to 18; SQLite only for testing; Oracle only with an enterprise subscription. The upgrade notes for 35 drop PHP 8.2, MariaDB 10.6 and MySQL 8.0.
  • Licence: the server is AGPL-3.0; the desktop client is GPL-2.0.

Seafile

  • Current releases: Community Edition 13.0.28 on 18 September 2026 is the latest stable release. It fixed a vulnerability where a read-only library API token could perform batch writes. Version 14.0 is in beta (14.0.9 beta on 14 October 2026), with SeaDoc 3.0, SeaSearch as the default search engine, utf8mb4 database encoding, webhooks and an AI chat feature. Face recognition is removed in 14.0.
  • Version 13 changes: the first stable 13.0 was 13.0.12 on 24 October 2025. Version 13 added a thumbnail server, a metadata server and a notification server, recommended Redis as the cache, and stopped supporting binary package deployment for Community Edition, which now runs in Docker only. WebDAV no longer accepts LDAP account logins; LDAP users must create a WebDAV token.
  • Requirements: Community Edition needs at least 2 cores, 2 GB of RAM and 10 GB of disk, with 50 GB or more recommended. The Docker stack includes Seafile, MariaDB, Redis, SeaDoc and Caddy. Professional Edition needs 4 cores and 4 GB with the default Elasticsearch, or 2 cores and 2 GB with SeaSearch or an external Elasticsearch.
  • Licence: the server is AGPLv3 with an OpenSSL exception, the seahub web front end Apache 2.0, and the clients GPLv2 and Apache 2.0. Professional Edition is commercial; its Docker page says it can be used without a paid licence with up to three users.

OpenCloud

  • Current releases: rolling release 9.0.0 on 27 October 2026, after 8.1.0 on 5 October, 8.0.0 on 15 September and 7.5.0 on 25 August. The production line is 7.2, from 7.2.0 on 25 June 2026 to 7.2.4 on 21 August 2026. An older production line, 4.0, started on 1 December 2025 and reached 4.0.8 on 25 June 2026. The lifecycle page dates the next production release for 17 November 2026.
  • Release model: rolling releases every three weeks with community support; production releases about every six months with full QA and professional support; long-term support with backports for two years, available only with a professional or premium subscription. Versions follow semantic versioning.
  • What is new in rolling: 9.0.0 adds passwordless guest access by email (single-use links valid for 30 minutes, 24-hour sessions renewed with a PIN, web only), tags in search and HEIC and AVIF previews. It also brings breaking changes that need the upgrade instructions. Version 8.0.0 added collaborative Markdown notes and 7.5.0 added encrypted vaults.
  • Requirements: production on Linux, no database, a POSIX filesystem such as ext4, XFS or ZFS (or CephFS, GPFS or NFS 4.2 and later with specific mount options). The documented minimum is a 1 GHz single core with 512 MB of RAM for up to 10 users; the medium example is a 2 GHz dual core with 8 GB of RAM for up to 1,000 users.
  • Licence: the server is Apache 2.0; the web front end is AGPL-3.0.

ownCloud

  • Ownership: ownCloud announced a definitive agreement to merge with Kiteworks on 21 November 2023, and Kiteworks announced that it had closed the acquisition on 7 December 2023. ownCloud said at the time that its open source position and licences would stay the same.
  • Classic server: owncloud/core, AGPL-3.0, released 11.0.0 on 30 July 2026 with 11 security fixes, PHP 8.3 as the minimum and a new code-signing setup, and 11.0.1 on 25 September 2026. The 10.16 line still gets patches; 10.16.6 came on 6 October 2026.
  • Infinite Scale (oCIS): Apache 2.0, 8.2.2 on 21 October 2026 with security dependency updates and 8.0.9 on 2 October; 9.0.0-rc.1 on 12 October 2026.
  • The fork: Heinlein Group announced OpenCloud on 22 January 2025, saying OpenCloud GmbH was founded in September 2024 and builds on Infinite Scale. heise reported at the time that more than a dozen former ownCloud developers had joined and that Kiteworks had threatened legal action.

The first questions to ask

  1. What are you replacing? A mapped drive, personal cloud accounts, an email attachment habit, or all three?
  2. How many users, and of what kind? Count laptop users, phone-only users, and outside people such as buyers or auditors who only receive links.
  3. What is the shape of the data? Total size, number of files, largest files, and how often big files change.
  4. Who can share outside, and how? Passwords, expiry dates, upload-only links, guest accounts. Write it down before the first install.
  5. How do people sign in? Local accounts, LDAP, or Google or Microsoft through OpenID Connect or SAML. Leaver handling depends on this.
  6. Do you need end-to-end encryption, or a well-run server? Most companies need the second. End-to-end encryption removes search, previews and online editing for that data.
  7. What else do you want on the same server? If office editing, calendars and chat matter, Nextcloud’s breadth counts. If not, a focused server may serve you better.
  8. Who owns it in year three? Upgrades, certificates, backups, restore tests and client rollout.

How each one works

File sync in one minute

A sync server keeps a copy of each user’s files on the server and on each device. Desktop clients upload local changes and download others’ changes; conflicts happen when two people change the same file before sync completes. Modern clients also offer “virtual files” that download content only when opened. Around this core sit sharing, versions, a trash bin, previews, search and the web interface.

Nextcloud: a PHP application platform with files at its core

Nextcloud runs as a PHP application behind Apache or nginx with PHP-FPM. Metadata about files, shares, users and apps lives in a relational database; file contents live on a local filesystem, or on external or object storage. Redis is commonly used for caching and file locking. Background work, such as cleaning up, sending notifications, generating previews in some setups and running migrations, is done by background jobs that you trigger with cron.

Files on local storage are kept as normal files in per-user folders, which makes them readable on disk, though you should always change them through Nextcloud so the database stays in step. Most features are apps: the files app itself, versions, sharing, the end-to-end encryption app, Talk, calendars, office integrations and many community apps. This is Nextcloud’s strength and its main cost: each app is another thing that must be compatible with the next major version.

Seafile: libraries, blocks and commits

Seafile organises data into libraries. Each library has its own history, and syncing happens at library level, with the option to sync selected folders. The data model documentation describes a design similar to Git: each change creates a commit, folders and files are content-addressed objects, and file contents are split into blocks of variable length using content defined chunking, with an average block size of around 8 MB. Unchanged objects are reused across commits, so snapshots and history are cheap and versions of a frequently updated file can share blocks.

The file server is written in C, with a Go file server added in version 9.0, and the web interface, seahub, is a Django application. A relational database (MariaDB or MySQL) holds users, groups and a small amount of library metadata in three databases; the objects and blocks live on disk or, in Pro, on object storage. Two consequences matter. First, sync is efficient for large files that change in parts. Second, the files on the server disk are blocks, not your folder tree, so you cannot browse them directly; you need Seafile’s tools to read them.

OpenCloud: one Go binary, spaces, and no database

OpenCloud is a set of Go services compiled into one binary, which you can run as one process or split into separate services. Internally, an embedded NATS server carries events, a built-in LDAP-like identity store (IDM) holds users for small setups, a minimal OpenID Connect provider handles sign-in, and Bleve provides search by default, with OpenSearch as an option. Files are organised into personal spaces and project spaces, which are shared areas with their own members and quota.

There is no relational database. Since 2.0.0, the default storage driver, PosixFS, keeps files as plain files in the folder tree on a POSIX filesystem, with metadata such as IDs, parent IDs and checksums stored in extended attributes. The documentation is clear about limits: there is no migration from the older DecomposedFS layout, you should not spread storage across filesystems, and a “collaborative” mode that accepts changes made outside OpenCloud needs more resources. Clients talk WebDAV and the LibreGraph API, with uploads through the resumable TUS protocol.

Sync clients and mobile

The server matters less to users than the clients. Test the clients on your real laptops and phones before anything else.

Nextcloud

  • Desktop: the desktop client 35.0.1 was released on 29 October 2026 for Windows 10 and later, macOS 12 and later, and Linux as an AppImage. It supports virtual files, now labelled “File Provider” on macOS, and the 35.0.0 release fixed a data loss problem with folder moves or renames, a reminder to keep clients current.
  • Mobile: the Files apps need iOS 17 or later and Android 9 or later; Android stable-35.0.2 and iOS 35.2.2 came in late October 2026. Push notifications go through Nextcloud’s push proxy, with notification content encrypted with a device key, and the fair use policy limits Nextcloud’s infrastructure, including push, to 500 users. Above that, Nextcloud recommends Enterprise.

Seafile

  • Desktop: two clients. The sync client, 9.0.22 on 12 October 2026, syncs whole libraries or selected folders to local disk. SeaDrive presents libraries as a virtual drive that downloads on demand, which suits large libraries on small laptop disks.
  • Mobile: Seadroid 4.0.14 for Android (28 September 2026) and the iOS app 4.0.7 (9 October 2026). The security documentation notes that mobile clients stopped doing client-side encryption from version 3.0.0, which matters if you plan encrypted libraries.
  • Real-time updates: an optional notification server, a separate container since version 12, pushes library changes to clients and the web interface over websocket instead of polling.

OpenCloud

  • Desktop: the desktop client 4.0.0 came on 3 September 2026. It moved to Qt 6.11, which removes support for macOS 12, uses webfinger to discover sign-in settings, and fixed several sync reliability issues, including resuming interrupted TUS uploads and retrying single files after network errors. Virtual files with on-demand download are supported.
  • Mobile: when we checked, the Android repository on GitHub published tester builds only, and we did not find an iOS repository under the project on GitHub. Check the app stores for current apps, and test them on your staff’s actual phones before you promise mobile access.

What to decide

Pick full sync, virtual files or both, then test saving and re-syncing a 500 MB file over your worst line. Check operating system minimums against your fleet: a macOS 12 laptop works with Nextcloud’s client but not with OpenCloud’s client 4.0.

Security and accounts

Exposure

All three will face the internet, because the point is access from anywhere. Put them behind a reverse proxy with TLS, open only 443 and 80, keep admin pages and SSH behind a VPN, and turn on two-factor sign-in. Our mesh VPNs post covers the admin side.

Sign-in and leavers

  • Nextcloud supports LDAP and Active Directory, and OpenID Connect and SAML through apps. App passwords are used for sync clients and WebDAV. Note that server-side encryption in per-user key mode does not work with single sign-on or app passwords, which is one more reason to keep the default master key mode.
  • Seafile’s admin manual documents LDAP, OAuth sign-in with an external provider, SAML 2.0 with examples for Microsoft Entra ID, ADFS and Keycloak, and two-factor authentication. The Pro LDAP guide adds LDAP user and group sync, including deactivating users who leave the directory.
  • OpenCloud is built around OpenID Connect. The built-in identity provider is based on LibreGraph Connect and, in the project’s words, is mainly targeted at smaller installations; for larger setups it recommends an external provider. Keycloak is documented, with a shared directory mode and an autoprovisioning mode. Clients use the authorization code flow with PKCE.

Leaver handling is where file servers fail audits: test what happens to the files and links a departing person owned.

  • Nextcloud offers public links with passwords, expiry dates, upload-only “file drop” links and federated sharing between servers. Administrators can enforce passwords and default expiry. Check these settings on day one, because a wrong default means hundreds of permanent links later.
  • Seafile offers share links and upload links with passwords and expiry, and internal shares at library and folder level. Folder-level permissions inside a library are basic in Community Edition; fine-grained folder permissions are listed as a Pro capability.
  • OpenCloud shares at file, folder and space level, with public links whose roles range from viewer to uploader. In our drill, OpenCloud 7.2.4 refused to create a public link without a password, and the sharing service documentation lists password enforcement on all public shares as true by default. Version 9.0 adds guest access by email for outside people.

Encryption at rest and end-to-end encryption

  • Nextcloud server-side encryption encrypts file contents on storage with a master key by default. The documentation is clear that it does not encrypt file names and does not protect against a compromised server or administrator; it is mainly meant for external storage you do not control. Since version 25 the size overhead is about 1 percent. For protection against the server itself, Nextcloud offers the end-to-end encryption app (2.5.0 on 10 October 2026), which encrypts chosen folders on the desktop and mobile clients and in the browser. Server features cannot read those folders, so search, previews and office editing do not work there.
  • Seafile encrypted libraries are encrypted by the desktop client with a password that is not stored on the server. The security documentation is honest about the limits: file names, sizes and history are not encrypted, there is no integrity protection, web access sends the password to the server, which keeps it in memory for an hour, and libraries created in the web interface pass keys through the server. Since version 12, administrators can choose PBKDF2 or Argon2id for key derivation; the PBKDF2 default is 1,000 iterations, so raise it if you use this feature.
  • OpenCloud vaults, added in rolling release 7.5.0, are encrypted folders and spaces. Encryption happens in the browser, file names are encrypted, and the format is built on and compatible with rclone crypt. The release notes list limits: no Collabora or collaborative editing inside vaults, no thumbnails in the list, no sharing of single files out of a vault, and no passphrase recovery. As of 2 November 2026, vaults are in rolling releases only, not in the 7.2 production line.

For most companies, the right answer is full disk encryption on the server, a well-patched server, careful link rules and good backups. Use end-to-end encryption for a small set of truly sensitive folders, with a written plan for lost passphrases.

Performance and how to read benchmarks

What the projects publish

There is no recent, independent benchmark that compares these three on the same hardware, and we did not find one we could trust. What the projects publish is their own:

  • OpenCloud reported in its 8.0.0 notes that a community fix cut Bleve search memory for about 100,000 files from 1.1 GB to about 120 MB, and in 8.1.0 that the web interface loads about 40 percent faster, from 1.5 seconds to 0.9 seconds. Both are the project’s own measurements on its own setup.
  • Seafile explains its speed by design rather than by numbers: content defined chunking, block reuse across versions, and very little metadata in the database. That design is real, but how fast it feels on your data still needs a test.
  • Nextcloud publishes tuning guidance rather than headline figures: PHP memory per process (128 MB minimum, 512 MB recommended), OPcache, Redis for caching and locking, and system cron for background jobs.

What slows each one down in practice

  • Nextcloud: too few PHP-FPM workers, no Redis, AJAX background jobs instead of cron, and previews of large images on first view. PDF, Office and video previews are off by default and called unsupported in the documentation.
  • Seafile: very large libraries with millions of files, deep history with no limit, and storage that is slow for small random reads.
  • OpenCloud: storage with restricted IOPS, which the documentation warns against, and search indexing on large trees. Because metadata lives in extended attributes, the filesystem is the database, and its latency is your latency.

What to measure yourself

Copy one real department folder and measure: first full sync to a fresh laptop, re-sync of a 500 MB design file after a small change, listing a folder of 5,000 files in the web interface, and server memory and CPU throughout. Repeat over a branch line and a phone hotspot. Those numbers decide more than any vendor chart.

Licences and free-edition limits

Nextcloud: AGPL, one code base, paid Enterprise subscription

The server is AGPL-3.0 and the community version has all features. Nextcloud Enterprise is a subscription for the same software with support, staged releases, and long-term support for older versions. The limits that matter for the free version are not in the code but in Nextcloud’s own infrastructure: the fair use policy says services such as push notifications and the app store are limited and will not work for more than 500 users, and recommends Enterprise above that, with free licences possible for some NGOs and schools. Oracle database support needs a subscription. At about 95 users, Bhavani Riverside is well inside the limit.

Seafile: AGPL Community Edition, commercial Professional Edition

The server and web front end are open source under AGPLv3 and Apache 2.0. Professional Edition is commercial. Seafile’s on-premise page lists full-text search, granular folder permissions, audit logs, clustering for high availability and S3 storage integration as Professional capabilities. The admin manual also places audit logs and the virus scan integration in Pro, along with LDAP user and group sync. Pro is free for up to three users, which is useful for testing Pro features but not for a company. Ask for a quote for your real user count.

OpenCloud: Apache 2.0 server, AGPL web, paid support and LTS

The server is Apache 2.0 and the web front end AGPL-3.0, so the community edition has all features. What you pay for is support and the release model: production releases come with professional support, and long-term support with two years of backports is available only with a professional or premium subscription. Without a subscription, you live on rolling releases or move to each new production release on your own.

ownCloud

The classic server is AGPL-3.0 and Infinite Scale is Apache 2.0. Commercial support is sold under Kiteworks. Read the current terms directly with the vendor before you renew.

Operations and day two

Sizing and hosting

  • Nextcloud for about 100 users: 4 vCPU and 8 GB of RAM is a comfortable start for files only, with PHP, the database and Redis on the same VM. Add more for office editing, Talk or previews of large images. Follow the PHP and database versions listed for your major version.
  • Seafile Community Edition: the documented minimum is 2 cores and 2 GB; for 100 users with large files, 4 vCPU and 8 GB with fast disk leaves room for the thumbnail and notification servers and SeaDoc. Pro with the default Elasticsearch needs at least 4 cores and 4 GB, and the host needs vm.max_map_count set to 262144.
  • OpenCloud: the documentation gives 512 MB for up to 10 users and 8 GB with a dual core for up to 1,000 users. Disk speed matters more than CPU. The documentation says bare-metal binary installs are not officially supported and are meant for quick evaluation.

Backups

  • Nextcloud: put the server in maintenance mode, dump the database (mariadb-dump with –single-transaction, or pg_dump), and copy the config, data, theme and custom apps folders. Restore needs all of them from the same moment.
  • Seafile: back up the three databases first (ccnet_db, seafile_db and seahub_db), then the data directory. The manual explains why: database first avoids corrupted libraries, at the cost of possibly losing some of the newest writes. Keep a week or more of separate database dumps.
  • OpenCloud: stop the instance for a consistent backup, or use filesystem snapshots, which the documentation recommends. Back up the config, system data, metadata and file blobs together, keep a note of the exact binary or image version, and rebuild the search index after a restore if you did not back it up.

In all three, the sync server is not a backup. Versions and a trash bin help with mistakes. They do not help when the server, its disk or its admin account is lost. Copy the data to a separate system with its own credentials, such as restic or Kopia to another site, and test a restore every quarter.

Upgrades

  • Nextcloud: you cannot skip major versions. Move to the latest point release first, disable incompatible third-party apps, upgrade one major at a time, run cron a few times between majors so background migrations finish, then add missing database indices. Downgrades are not supported. Plan a major upgrade every four to eight months.
  • Seafile: follow the upgrade notes for each major version and move Community Edition to Docker if you have not. Version 13 changed configuration to environment variables, moved WebDAV for LDAP users to tokens and removed the old file tags. To move from Community to Pro, the manual asks you to be on the same major version first and not to combine a major upgrade with the edition change.
  • OpenCloud: rolling releases can include breaking changes, as 9.0.0 did with the thumbnailer and guest authentication, and 8.0.0 needed a search reindex. Production releases are the safer track. Read the notes for every release you skip.

Background work

  • Nextcloud: switch background jobs to system cron every 5 minutes, or a systemd timer. AJAX mode, the default, is the least reliable, and Webcron is meant only for very small installs. The maintenance window setting is in UTC, so 1 AM IST is 19:30 UTC the previous day. Decide on preview settings and consider pre-generating previews for photo-heavy folders.
  • Seafile: schedule garbage collection to reclaim blocks from deleted libraries and trimmed history, with a dry run first. Set history limits per library so storage does not grow without bound. Seafile fsck checks library integrity when something looks wrong.
  • OpenCloud: watch the search index size and the event system. Keep an eye on disk inodes and extended attribute support if you move storage.

Side by side

Architecture

  • Nextcloud: PHP on Apache or nginx, a relational database, Redis, files as plain files on disk or object storage.
  • Seafile: C and Go file server plus Django web front end, MariaDB or MySQL, files as content-addressed blocks.
  • OpenCloud: one Go binary with many services, no database, files as plain files with metadata in extended attributes.

Scope

  • Nextcloud: files plus a full collaboration suite and app store.
  • Seafile: files, libraries, wiki and SeaDoc documents, focused on sync.
  • OpenCloud: files and spaces, with web office through Collabora and newer collaborative notes and whiteboards.

Free edition at about 95 users

  • Nextcloud: all features; push and app store fine under 500 users.
  • Seafile: Community Edition with core sync and sharing; Pro features need a paid licence above three users.
  • OpenCloud: all features; support and LTS need a subscription.

Sign-in

  • Nextcloud: LDAP, OpenID Connect and SAML through apps.
  • Seafile: LDAP, OAuth and SAML; LDAP sync in Pro.
  • OpenCloud: OpenID Connect at the core; built-in provider for small setups, Keycloak or another provider for larger ones.

End-to-end encryption

  • Nextcloud: folder-based, in clients and browser, server features off for those folders.
  • Seafile: encrypted libraries by password, file names and sizes not encrypted.
  • OpenCloud: vaults with encrypted names, in rolling releases only so far.

Release and support rhythm

  • Nextcloud: major every four months, one year of community support each, longer with Enterprise.
  • Seafile: one major roughly every year, point releases often.
  • OpenCloud: rolling every three weeks, production about every six months, LTS by subscription.

Operational weight

  • Nextcloud: highest; many moving parts and frequent major upgrades.
  • Seafile: medium; Docker stack, garbage collection and careful backup order.
  • OpenCloud: lowest on paper; a younger project with faster change.

A worked plan for Erode

Month 1: rules before software

  • Map today’s shares on the Windows server to future libraries or spaces: Design, Merchandising per buyer group, Export Docs, Accounts. Remove old folders nobody owns.
  • Write link rules in one page: links to buyers must have a password and an expiry of 30 days or less; upload-only links for job-work units; no public links from Accounts.
  • Decide sign-in: company Google Workspace accounts through Seafile’s OAuth support, so leavers lose access in one place. Test it before the pilot.
  • Count data: total size, file count, the 20 largest files. Ask the hardware vendor for a separate data disk.
  • Move personal Google Drive files used for buyers into a company-owned location, starting with accounts of people who have left.

Month 2: Seafile pilot

  • One VM on the Proxmox host: 4 vCPU, 8 GB of RAM, a 100 GB system disk and a separate 2 TB data disk, Ubuntu 24.04, Seafile Community Edition 13.0 with the documented Docker stack. Only 443 and 80 open to the internet; SSH and the admin pages through the VPN.
  • 40 users: all designers and 15 merchandisers. Designers use SeaDrive for the big design library and the sync client for their working folders; merchandisers use the phone apps and the web.
  • Raise PBKDF2 iterations or choose Argon2id in case anyone creates an encrypted library, and decide whether to allow encrypted libraries at all.
  • Nightly: database dumps first, then the data directory, to the NAS, plus a weekly copy offsite with restic.

Month 3: measure and decide

  • Measure the tests from the performance section with real files, including a 500 MB design file over the backup line.
  • Do one full restore of the pilot to a scratch VM and open three libraries from it.
  • Fill in the buyer questionnaire with what Community Edition can show. If the buyer insists on access logs per file or subfolder permissions inside a library, get a Seafile Pro quote for about 95 users and compare it with Nextcloud Enterprise or plain Nextcloud.
  • Ask the merchandising head and two designers one question: would you go back? If the answer is yes, find out why before scaling.

Month 4 onwards: own it

  • Move the rest of the office in batches by department, with a two-week freeze on the old share for each batch, then make it read-only.
  • Garbage collection monthly, a dry run first. History limits of 180 days on large libraries, longer for Export Docs.
  • Two named admins with written runbooks for upgrade, restore and leaver handling. Plan the move to 14.0 only after its first stable release and a few point releases.
  • In early 2027, try an OpenCloud production release on a test VM with a copy of one library, mainly to compare operations and the plain-file layout.

When not to adopt each

Do not adopt Nextcloud if

  • You only need file sync and nobody will own PHP, the database, Redis and cron.
  • You cannot plan a major upgrade every four to eight months.
  • You will install many community apps and expect them all to survive each upgrade.

Do not adopt Seafile if

  • You need files on the server disk as a plain folder tree for other tools to read.
  • Your security review needs audit logs or subfolder permissions but you will not pay for Pro.
  • You need to run it outside Docker; Community Edition 13 no longer supports binary installs.

Do not adopt OpenCloud if

  • You need a long, quiet support line without paying for a subscription.
  • Your storage is a filesystem without solid extended attribute support or with restricted IOPS.
  • You need the newest features, such as vaults or guest access, on a production release today.

Do not self-host file sync at all if

  • You have no one who can own backups, restores and upgrades for five years.
  • Your company already pays for Microsoft 365 or Google Workspace with enough storage, and the real problem is policy, not the tool. Fix the sharing settings there first.

A short history

ownCloud started in 2010 as an open source project for self-hosted cloud storage. In 2016, its founder and several core developers left and started Nextcloud as a fork. Nextcloud then grew into a collaboration suite.

Seafile grew in parallel with a different design: libraries, blocks and a Git-like history. It added a Go file server in 9.0, SeaDoc and a new interface in 12.0, and moved Community Edition to Docker only in 13.0.

ownCloud began Infinite Scale as a Go rewrite without a database. ownCloud agreed to merge with Kiteworks in November 2023 and the deal closed in December 2023. OpenCloud GmbH was founded in September 2024, announced by Heinlein Group in January 2025, and released OpenCloud 1.0.0 on 24 February 2025, built on Infinite Scale.

Decision guide

You want one place for files, calendars, chat and office editing

Choose Nextcloud, and budget for its upkeep. Consider Enterprise if you are near 500 users or need long support.

You want fast, reliable sync of large files and a focused tool

Choose Seafile Community Edition, and price Pro early if audit logs, subfolder permissions or full-text search matter.

You want plain files on disk, no database and modern sign-in

Evaluate OpenCloud on a production release, and decide whether you will buy a subscription for long-term support.

You run ownCloud today

Read the current release and support status of your line, plan a move or a renewal with clear dates, and test the target on a copy of your data.

Checklist

  • Folder structure mapped to libraries or spaces, with an owner for each.
  • Written link rules: passwords, expiry, upload-only links, who can share outside.
  • Sign-in method chosen, two-factor on, leaver process tested.
  • Clients tested on real laptops and phones, including the oldest macOS in use.
  • Data on its own disk, sized for three years.
  • Backups in the documented order, one copy offsite, one restore tested.
  • Background jobs, garbage collection or index jobs scheduled and monitored.
  • Upgrade path written: current version, next version, date.
  • Release feed and security advisories subscribed by two people.
  • Exit plan: how you would export everything if you had to leave.

Common mistakes

  • Copying the old file server one to one. Old permissions and dead folders move with it. Clean first.
  • Leaving link defaults as they are. Permanent public links without passwords are the most common leak.
  • Treating sync as backup. A deleted or encrypted file syncs as well as a good one.
  • Turning on every preview type. PDF, Office and video previews cost CPU and are off in Nextcloud for a reason.
  • Using end-to-end encryption everywhere. It removes search, previews and editing, and lost passphrases mean lost data.
  • Running Nextcloud background jobs in AJAX mode. Use system cron.
  • Forgetting the phones. Test mobile apps and push before you promise them.

A small hands-on check

We ran a small, local drill on our box on 2 November 2026, around 2:26 AM IST. It used the OpenCloud 7.2.4 single binary for Linux x86_64 from the project’s GitHub release, with a checksum that matched the published SHA-256. It ran as an ordinary user inside an unprivileged network namespace with only loopback and no route outside. No packages were installed and no system services were touched. We did not run Nextcloud, which needs PHP, a database and a web server, or Seafile, whose Community Edition 13 is Docker only. What we saw:

  • The version command reported “Version: 7.2.4, Edition: rolling”, and the status endpoint also showed the edition as rolling, even though the lifecycle page lists 7.2 as the production line. If you rely on the production track, confirm with the project which builds are the production ones.
  • After init, the server answered its status endpoint in about 2 seconds. OpenID Connect discovery and webfinger worked out of the box with the built-in identity provider.
  • On the first run, every API call and WebDAV upload with a username and password returned 401. Basic authentication is off by default, as the proxy documentation says. We turned it on with an environment variable for the second run only, which is fine for a test and not something to copy to production.
  • With it on, we created a user (201), uploaded a 5 MB random file over WebDAV (201, about 0.08 seconds on loopback) and downloaded an identical copy.
  • Creating a public link without a password failed with “missing required password”. Password enforcement on public links is on by default. Anonymous WebDAV access returned 401.
  • The uploaded file was stored as a plain file named test.bin inside the user’s folder on disk, with extended attributes holding its ID, parent ID, size, modification time and SHA-1, MD5 and Adler-32 checksums.
  • One process opened 73 listening ports, all on 127.0.0.1, none on all interfaces. Its resident memory was about 280 MB on the first run and about 350 MB on the second, after the upload, measured about 20 seconds after the server came up. Real use will be higher; do not size from this.
  • The data folder held the embedded NATS store, identity provider keys, the built-in user store, the Bleve search index, the storage folders and a self-signed certificate; it was 6.2 MB after the upload. The log had 22 warnings, mostly about the generated TLS certificate and optional settings. The server stopped cleanly.

The point is not speed. The first minutes already show the defaults that matter: sign-in methods, link passwords and what lands on disk. It is easier to learn them on a test machine than in production.

Unlearn, re-learn

  • Unlearn “a sync server is a folder in the browser”. Re-learn that it is storage, metadata, clients, links, previews, search and upgrades, and you own all of them.
  • Unlearn “encrypted means safe from everyone”. Re-learn what each encryption mode protects, and what it leaves visible, such as file names and sizes.
  • Unlearn “more features is better”. Re-learn that each feature is something to upgrade and secure; pick the scope you will actually use.
  • Practise: take one real department folder, count its files and size, write its link rules in five lines, then sync it to a test server and restore it from backup. Do this before you choose.

Sources

Nextcloud

Seafile

OpenCloud

ownCloud and the fork

comments powered by Disqus

Releted Posts

Self-hosted team chat in 2026: revisit Mattermost, Rocket.Chat and Zulip before you move another team off Slack

Sooner or later, every growing Indian company has the same conversation about chat. The free plan of a hosted chat tool has started hiding old messages, or the renewal quote for a paid plan has arrived for a few hundred users, or a large customer has asked where the project discussions are stored.

Read more

Self-hosted email in 2026: revisit Stalwart, mailcow and Mailu before you run another mail server

Every few years, an Indian company with a few hundred people asks the same question about email. The hosted suite renewal has come in higher than last year, or the old mail server set up by a contractor in 2017 is running on an operating system that no longer gets updates, or invoices sent from the ERP have started landing in spam.

Read more

Virtualization platforms in 2026: revisit Proxmox VE, XCP-ng and Incus before you migrate another virtual machine

Most virtualization migrations in India over the last two years did not start with an architecture review. They started with a renewal quote.

Read more