Nextcloud is the default answer to "how do I self-host my files", and for good reason. It's AGPL-3.0, it has a huge app store, and it covers files, calendar, contacts, talk and office integration in one install.

That breadth is also the reason people go looking for a Nextcloud alternative. This post is for the cases where Nextcloud is either too much to maintain or simply the wrong shape for the job.

Why do people move off Nextcloud?

The common complaints fall into three buckets.

App sprawl. Much of Nextcloud's functionality lives in apps, some maintained by Nextcloud GmbH and some by the community. The upgrade docs tell you to review third-party apps for compatibility before each release. On an instance with a dozen apps, that check is real work.

The PHP stack. Nextcloud is a PHP application backed by a database, typically with Redis for caching, plus cron jobs and a web server. None of this is exotic, but tuning it (OPcache, memory limits, background jobs, file locking) is a recurring theme on the forums.

Upgrade cadence. The docs are blunt: "You cannot skip major releases." Fall behind for a year and you're stepping through each major version in turn.

If none of that bothers you, stay on Nextcloud. If it does, the right replacement depends on what you actually use it for.

What shape of tool do you need?

Before comparing products, decide which of these you need:

  • File sync and share only. You want a Dropbox replacement and nothing else.
  • Device sync without a server. You want folders mirrored across your own machines.
  • Private document editing. You want collaborative docs where the server can't read the content.
  • A team workspace. Files plus the conversation, tasks and meetings around them.

Nextcloud tries to be all four. The options below each pick one or two.

ownCloud Infinite Scale and OpenCloud: the Go rewrite, now in two flavours

The ownCloud story needs a short recap because it confuses a lot of people.

So in 2026 you have two maintained descendants of the same Go codebase. OpenCloud's server repo is Apache-2.0 and is maintained by OpenCloud GmbH. oCIS is Apache-2.0 and maintained by Kiteworks/ownCloud.

Why pick either: a single Go service instead of a PHP stack. OpenCloud's README says there's no database, and all data is stored in the filesystem. That's a very different operational profile from Nextcloud.

Trade-offs: a narrower scope than Nextcloud, a much smaller app ecosystem, and a recent governance split that you should watch before committing. If you choose between the two, check how often each one releases and how active its community is, not only the feature list.

Seafile: fast, focused file sync

Seafile is a long-running project that does one thing well: syncing libraries of files with good performance on large trees. The licensing is split by component: server core AGPLv3, the Seahub web UI Apache-2.0, and the desktop client GPLv2.

Why pick it: sync speed and reliability, plus encrypted libraries. The security docs explain that when you create and use these from the desktop client, encryption happens on the client and the library password isn't stored on the server.

Trade-offs: read the fine print on encrypted libraries. File and directory names, sizes and edit history are not encrypted, and creating a library through the web UI sends the password through the server. Features like SAML, clustering and virus scanning are marked as Pro in the manual. The Pro edition is free for up to three users, and larger teams need a paid licence. That's an open-core model, so keep it in mind.

Syncthing: sync, not collaboration

Syncthing (MPL-2.0) keeps folders in step across your own devices, peer-to-peer. There's no web UI for sharing with outsiders, no user accounts in the Nextcloud sense, and nothing to "log into".

Why pick it: if you used Nextcloud only to keep a laptop, a desktop and a NAS in sync, Syncthing removes a whole server from your life. It's light, mature and easy to reason about.

Trade-offs: it isn't a collaboration tool. No share links, no comments, no permissions UI for a team. Pair it with something else if you need those.

CryptPad: collaborative docs the server can't read

CryptPad (AGPL-3.0) is a suite of real-time collaborative editors (documents, sheets, presentations, forms, kanban, code, whiteboard) where content is encrypted end-to-end in the browser.

Why pick it: if the part of Nextcloud you valued was co-editing documents, and your threat model includes the server operator, CryptPad is built for exactly that.

Trade-offs: it isn't a sync client for your file system, and end-to-end encryption by design limits anything that would need the server to read your content. Treat it as a document suite, not a Dropbox replacement.

Drumee: files, chat, tasks and meetings in one workspace

Drumee is an AGPL-3.0 project (source under the drumee organisation on GitHub) from a European company. It takes a different angle from the tools above. Instead of a file server with chat bolted on as an app, the conversation lives on the files: chat threads are attached to folders and individual files.

Conversation that lives on the files

Why pick it: if your Nextcloud install had grown into files + Talk + Deck + a calendar app, and the problem is keeping those in sync with each other, Drumee puts files, chat, a task board and video meetings in one product. It has personal, internal and external (client) workspaces, guest access, a folder permissions matrix (view / chat / edit / admin), version history and a Google Drive migration tool. You can use Drumee's hosted plans or self-host it as a "Sovereign Node".

Trade-offs: it's younger, with a much smaller ecosystem and fewer integrations than Nextcloud. Its chat is less deep than a dedicated chat server like Matrix or Mattermost, its task features are lighter than a dedicated project management tool, and it doesn't claim real-time co-editing of office documents. If you need an office suite, you'd still pair it with something else.

Side-by-side

Comparison table: OpenCloud / oCIS, Seafile, Syncthing, CryptPad, Drumee

Which Nextcloud alternative should you pick?

Which Nextcloud alternative fits the job

  • You only need file sync and share, and want less to operate: OpenCloud or oCIS. Pick based on whose governance and release cadence you trust more after the 2025 split.
  • You want proven sync performance and some client-side encryption: Seafile, keeping the open-core line and the metadata caveat in mind.
  • You were syncing your own devices and nothing else: Syncthing. Drop the server entirely.
  • Your priority is private collaborative documents: CryptPad.
  • Your pain is scattered context (files in one app, discussion in another, tasks in a third): Drumee is worth a look, as long as you accept a smaller ecosystem.
  • You actually use most of Nextcloud's breadth: stay. Put the effort into automating upgrades rather than migrating.

Whatever you choose, test a restore from backup and a major upgrade on a staging copy before you move real data. That tells you more about the next five years than any feature list.

For a longer look at the Drumee-specific trade-offs against Nextcloud, there's a write-up on the Drumee blog.

Disclosure: this post is written by the Drumee team, and Drumee is one of the tools covered. We've tried to keep it fair. Corrections welcome in the comments.