Nextcloud vs ownCloud

Nextcloud and ownCloud look like near-twins for a reason: they are literally descended from the same codebase. If you are choosing one to self-host, the interesting question is not "which forked from which" — it is which of two increasingly different roadmaps fits how you want to run your own cloud.

They start from the same code

ownCloud came first, in 2010. In 2016 its original founder, Frank Karlitschek, left with much of the core team and started Nextcloud as a fork. That shared ancestry is why the two still feel alike: the classic server on each side is a PHP application backed by MariaDB or MySQL, both are open source under the AGPL, and both give you file sync, sharing links, and desktop and mobile clients that work the same way. On a single small VPS, either one will happily hold your files and sync them across devices.

The similarities mostly end at that baseline. Since the split, the two projects have spent the better part of a decade pulling in different directions.

Two different roadmaps

Nextcloud: the all-in-one platform

Nextcloud has grown well past file sync into a full collaboration suite. Its Hub releases bundle files with calendar, contacts, mail, Deck (kanban boards), and Talk for chat plus audio and video calls. On top of that sits a built-in office suite — Nextcloud Office, powered by Collabora — so you can edit documents and spreadsheets in the browser without a third-party service. Beyond the bundle, an app store of 200+ community apps lets you bolt on everything from full-text search to two-factor providers to external storage backends.

The trade-off for that breadth is more moving parts. A production Nextcloud usually wants PHP tuning, a real database, Redis for caching and locking, and a background cron job to stay fast. It is entirely doable on a modest server, but it rewards a bit of care.

ownCloud: the file-focused rewrite (Infinite Scale)

ownCloud has taken the opposite bet. Its flagship is now Infinite Scale (oCIS) — a ground-up rewrite in Go rather than PHP. oCIS ships as a cloud-native set of services (in the simplest case, a single self-contained binary) with no PHP runtime and no MariaDB to babysit. The design goal is a lean, horizontally scalable file platform: storage-spaces, a modern web UI, and a much smaller operational surface than a classic PHP stack.

The flip side is focus. ownCloud deliberately stays close to files, sharing, and sync. There is no sprawling built-in groupware suite and no 200-app marketplace — an office suite is an add-on rather than a first-class bundle. If "a fast, reliable file server and nothing I did not ask for" is the goal, that focus is the feature.

Feature and app ecosystem

• Files, sync, sharing — a genuine tie. Both do versioned files, share links with passwords and expiry, and solid desktop and mobile clients.
• Groupware (calendar, contacts, mail) — built in on Nextcloud; not the focus on ownCloud.
• Office / document editing — Nextcloud bundles it (Collabora-based); ownCloud treats it as an integration you add.
• Chat and calls — Nextcloud Talk is first-class; ownCloud has no direct equivalent in the box.
• Extensibility — Nextcloud's 200+ app store versus ownCloud's smaller, more curated set. More apps means more capability but also more configuration choices to make.

Resources and performance

Because Nextcloud does more, it asks for a little more: plan for 1 GB of RAM as a realistic floor, and give it Redis and a proper database once real people start using it. A classic ownCloud server is lighter (around 512 MB), and oCIS in particular is frugal — a compiled Go service with no PHP-FPM pool to size. Neither is heavy by modern VPS standards; the difference is more about how many services you are keeping healthy than raw horsepower.

Community, funding, and governance

This is where the projects have quietly diverged the most. Nextcloud has the larger and more active community, a fast release cadence, and significant adoption across European public-sector and enterprise deployments, which funds steady development. ownCloud, the company, was acquired by Kiteworks in late 2023, and its engineering energy is concentrated on Infinite Scale rather than the classic PHP server. Both remain open source, but Nextcloud carries more day-to-day community momentum, while ownCloud's story is increasingly the oCIS rewrite.

Which should you self-host?

Pick Nextcloud if…

• You want one platform for files and calendar, contacts, office documents, and calls — a self-hosted Google Workspace or Microsoft 365 replacement.
• You value a large app ecosystem and are comfortable running a PHP plus database plus Redis stack.
• Community momentum and frequent feature releases matter to you.

Pick ownCloud if…

• You want a lean, file-focused server with fewer moving parts to operate.
• The Go-based Infinite Scale architecture appeals — no PHP or MariaDB, and a smaller operational footprint that scales out cleanly.
• You would rather add the one or two extras you actually need than manage a suite you mostly will not use.

Running either on a VPS

Both run comfortably on a single small server — the resource gap between them is minor next to the difference in what they do. Give Nextcloud a touch more headroom for its extra services, keep an eye on backups for whichever you pick, and either will serve a household or a small team without trouble. The step-by-step setups are linked below, and any of the VPS options here has plenty of room for the app plus its database.