How to self-host Nextcloud (your own Dropbox and Google Drive)
If there's one app that made "run your own cloud" a real sentence, it's Nextcloud. It's the open-source answer to Dropbox and Google Drive — file sync and share across every device — and then it keeps going: calendars, contacts, notes, photos, collaborative documents. One server, and a surprising slice of Google's product line stops being Google's.
What Nextcloud actually is
At its core, Nextcloud is file sync and share. Desktop clients for Windows, Mac and Linux; mobile apps for iOS and Android; a clean web interface. Drop a file in your Nextcloud folder and it's on every device and shareable with a link — exactly the Dropbox muscle memory, pointed at a server you control.
The reason people fall for it is everything bolted around that core, via first-party apps you enable with a click:
- Calendar and Contacts (CalDAV/CardDAV) — a real replacement for Google Calendar and Contacts that syncs to your phone.
- Notes, Tasks, Bookmarks.
- Photos, with mobile auto-upload — a bonus Google Photos-lite if you already run Nextcloud.
- Collaborative documents via the Office add-ons, for real-time editing.
What to expect (the honest version)
We run Nextcloud for customers, so here's the straight talk. Nextcloud is powerful, which is the same word as "not tiny." It wants a proper database and a bit of RAM to feel snappy, and a fresh install has a few settings worth tuning for performance. It is not a 20-megabyte single binary; it's a full platform, and it behaves like one — brilliant when it's set up well, sluggish and noisy with warnings when it isn't.
The practical implication: the difference between "Nextcloud is amazing" and "Nextcloud is slow" is almost entirely in how it's hosted — the database, the caching, the background jobs, the reverse proxy. Get those right and it flies.
How to deploy it
A solid Nextcloud install is really a small stack: the Nextcloud app, a database (PostgreSQL or MySQL), a Redis cache for locking and performance, a volume for your files, a domain, and TLS in front. Roughly:
- Run the app plus its database and a Redis cache, with a persistent volume for data.
- Put a reverse proxy in front to terminate HTTPS with a real certificate.
- Configure background jobs (cron) so housekeeping actually runs — skip this and you'll wonder why things feel off.
- Tune the caching and a couple of config values the setup warns you about.
Do it yourself on a VPS and it's a genuinely educational afternoon — and then a standing job to keep the stack updated, backed up and tuned. Or deploy Nextcloud in one click with the database, cache, background jobs, TLS and IPv6 already wired up the way it wants — and skip straight to uploading files.
First steps once it's running
- Install the desktop and mobile clients and point them at your server. Your files start syncing everywhere.
- Add your calendar and contacts to your phone over CalDAV/CardDAV and quietly retire Google Calendar.
- Enable the apps you want — Photos, Notes, Office — from the built-in app store. Only turn on what you'll use; each one is more to keep happy.
- Confirm backups. This is now the home of your files. A backup you've tested is the difference between "self-hosted" and "single point of failure."
Nextcloud is the closest thing there is to lifting your whole personal cloud off Big Tech and setting it down somewhere you own. It asks for a little care in the hosting — and pays it back by turning "my files, my calendar, my contacts" into things that are actually yours.
Deploy Nextcloud now → — or browse the full app catalog for the rest of your cloud.