ownCloud and Nextcloud share a code ancestry and a purpose, and anyone choosing a self-hosted file platform ends up comparing them. The honest difference is not features per se but direction: one has stayed a file sync and share server, the other has become a collaboration suite. This post follows an IT manager choosing between them on MassiveGRID PaaS, which is built on Virtuozzo Application Platform, formerly Jelastic, for a firm whose needs are specific.
The firm is an architecture practice we will call Stonefield Studio: 120 staff across two offices and many building sites, working with large drawing and model files that must sync reliably to laptops and be shared with clients and contractors by link. The ownCloud package installs the classic PHP-based ownCloud Server with a PHP application server, a MariaDB database and expandable data storage; the Nextcloud package installs its counterpart.
Same origin, different destinations
Nextcloud forked from ownCloud in 2016. Since then Nextcloud has added Talk for chat and calls, groupware (mail, calendar, contacts), collaborative office editing integrations, and a large app store, positioning itself as a self-hosted alternative to Google Workspace or Microsoft 365. ownCloud Server, the PHP edition the package installs, has stayed focused on file sync and share with enterprise integrations, while ownCloud's company built Infinite Scale, a separate Go-based platform, as its future. For a firm choosing today, the question is whether it wants a file server or a workspace.
What Stonefield actually needs
The IT manager's requirements list was short and file-shaped. Reliable desktop sync for very large files, including partial-file changes to multi-gigabyte models. Selective sync so a laptop does not hold every project. Public and password-protected share links with expiry for clients and contractors. External storage connectors for the studio's existing NAS. LDAP authentication. A mobile app for site visits. Nothing about chat, mail or collaborative document editing, which the studio does in other tools it is not about to replace.
| Requirement | ownCloud Server | Nextcloud |
|---|---|---|
| Desktop sync with large files, selective sync | Yes, mature client | Yes, mature client |
| Share links with password and expiry | Yes | Yes |
| External storage (SMB, S3, etc.) | Yes | Yes |
| LDAP or SAML authentication | Yes | Yes |
| Mobile apps | Yes | Yes |
| Chat, video, groupware, office editing | Not the focus | Yes, built in or one click |
| App ecosystem size | Smaller | Large |
| Product direction | Server maintained; company's future is Infinite Scale | Actively expanding the suite |
On the file requirements the two are equivalent. The decision is therefore about what the firm does not need and about direction.
The argument for ownCloud, and the argument against
For: a smaller surface. A file server that is only a file server has fewer apps to update, fewer features for staff to misuse, and a simpler security story for the practice's client confidentiality obligations. The ownCloud desktop client's handling of large files is what the studio's power users tested and liked. Against: direction. ownCloud's development energy is in Infinite Scale, which the package does not install and which has different deployment requirements. The manager's view is that ownCloud Server is stable and maintained, that the studio wants a file server for the next several years, and that if it ever wants a collaboration suite the migration to Nextcloud is a known path in either direction because the data model is files and a database.
He chose ownCloud, and wrote down the condition for revisiting: the day the studio wants its file platform to also be its chat or document editor.
Running it for large files on the platform
An architecture firm's data grows fast. The package's expandable data storage is the point: the data directory lives on a persistent disk that the manager enlarges from the dashboard as projects accumulate, with a disk load alert at 80% as the prompt. PHP upload and memory limits for large files are already raised by the package. The PHP node scales vertically in cloudlets (128 MiB of RAM plus 400 MHz of CPU) as sync clients hammer it at 09:00 when 120 laptops come online, and settles down by mid-morning. For the busiest hours the manager added a Redis node for ownCloud's file locking and memory cache, which is ownCloud's own recommendation once concurrency rises, and pointed the configuration at it over the internal network.
Backups are the Database Backup/Restore add-on nightly for MariaDB and platform snapshots plus an rsync to a backup storage node for the data directory; the two must be from the same point in time to restore consistently, so the file job runs immediately after the database dump. For a second copy of the files with replication rather than a single disk, the manager noted the GlusterFS Replicated Volume as the upgrade if the practice's tolerance for restore time shrinks.
Migration from the NAS and the old sync tool
Staff files came off the studio's NAS via ownCloud's external storage connector at first, so nothing had to be copied on day one; the NAS appeared as a folder. Over three months the manager moved active projects into ownCloud's own storage and left the archive on the NAS as a mounted external share. The previous consumer sync tool's shared folders were recreated as ownCloud group folders, and the 120 desktop clients were rolled out with the studio's device-management tool pointing at files.stonefield.example, secured by the Let's Encrypt add-on.
Cost and outcome
The PHP node averages about 14 cloudlets an hour, MariaDB about 6 and Redis about 2, roughly $54 a month before discounts at MassiveGRID's published $0.003372 per cloudlet-hour; the data disk is the larger line and grows with the practice's work. The consumer sync tool the studio left had been per user per month for 120 users with a storage cap the firm kept hitting. The IT manager's review after six months recorded two support tickets about sync, both resolved by the client's own conflict handling, and a client-side comment from a contractor that the share link had a password and an expiry date, which they had not seen from an architecture firm before.
Frequently Asked Questions
Can I move from ownCloud Server to Nextcloud later, or the other way?
Yes. Both store files as plain files in a data directory and metadata in a database, and each has documented migration paths for the other. On the platform, install the target package, restore the database and copy the data directory, run the target's upgrade or migration command, then repoint the desktop clients.
Does the package install ownCloud Infinite Scale?
No. It installs the classic PHP-based ownCloud Server. Infinite Scale is a different Go-based platform with its own deployment model; it can be run on the platform as custom containers if you need it, but it is not what the one-click package provides.
How much storage should I start with?
Add up active project data and give yourself a year of growth; storage expands from the dashboard without moving data, so starting smaller and growing on the disk alert is normal. The data disk is billed on its allocated size, so oversizing on day one costs money for nothing.
A file server that is only a file server
The ownCloud package installs ownCloud Server with expandable storage, a PHP server and MariaDB in one click on MassiveGRID PaaS, in the region you choose, billed per cloudlet-hour. Free 14-day trial, no credit card.
ownCloud on MassiveGRID PaaS