Quick answer up front: if Nextcloud feels sluggish for you, that’s almost never a Nextcloud problem — it’s an operations problem, usually missing caching, no cron set up, and overloaded budget hosting.
Last year a managing director called me, pretty annoyed. Nextcloud was “unusably slow,” he said, and he was thinking about switching back to a US solution. I looked at the setup. Nextcloud was innocent.
What I found: a cheap shared-hosting package, no Redis, no cron set up, PHP limits still at factory defaults, the database sitting on the same overloaded box as everything else. That’s like driving a van with the handbrake on and then wondering why it burns so much fuel.
Open source isn’t “free”
This is the misconception I see most often. The license costs nothing — running it well costs skill. Software like Nextcloud needs to be operated:
- Caching via Redis, otherwise every single action grinds through the database.
- Background jobs via real cron, not whatever happens to run on the next page load.
- OPcache, sane PHP limits, a database that isn’t also carrying three other services on the side.
- For large file volumes: object storage instead of a single drive filling up.
None of this is rocket science. But it doesn’t happen by itself, and “installed once” isn’t the same as “operated.” In short:
| Left to itself | Run properly | |
|---|---|---|
| Caching | Every action grinds through the database | Redis handles the caching |
| Background jobs | Run randomly on the next page load | Real cron, reliably scheduled |
| PHP & database | Factory defaults, DB shares the box with everything else | OPcache on, dedicated DB resources |
| Large file volumes | A single drive eventually fills up | Object storage takes the load |
Switching tools doesn’t fix this
The bitter part: anyone who now flees back to Microsoft 365 and friends buys back speed with dependency — and the original problem (nobody’s competently running operations) is still there. It just becomes invisible, because now someone else does it and you pay per head for it. The third option: hand over the operations without handing over control — that’s exactly what selfhosting as a service is about.
That managing director, by the way, didn’t switch. We set the thing up properly. It’s fast now. It was never Nextcloud’s fault.
Got an open-source app that’s acting up and you’re not sure whether it’s the tool or the setup? I’ll take a look — or read what Hosting & operations means at my place.