Self-host your own cloud: a practical Nextcloud guide

Moving your files off a public cloud is less about ideology and more about control: who can read your data, where it physically lives, and what happens if a provider changes its terms. Nextcloud gives you the same core experience — sync, share, calendars, contacts — on hardware you own.

**Size it for your data, not just your users.** Nextcloud's RAM needs scale with concurrent users, but its disk needs scale with your files. Decide your storage target first and attach enough disk; growing later is easier if user files live on a separate volume from the application code.

**Use the right database and cache.** MariaDB or PostgreSQL plus Redis. The Redis cache is not optional if you care about performance — it also prevents the notorious file-locking errors that appear on busy instances.

**Plan your backups before you migrate.** You need both the database (metadata) and the file directory. Back up the two together, and keep a copy off the server. Test a restore at least once; an untested backup is a hope, not a plan.

**Think about document editing.** If you want to edit Office files in the browser, add a Collabora Online container. That raises the RAM requirement, so size accordingly.

**Secure it properly.** Force HTTPS, enable two-factor authentication for accounts, and keep the server patched. Because your data is concentrated here, this server deserves more care than a throwaway test box.

Done well, a self-hosted Nextcloud is invisible in daily use — files sync, calendars update, shares work — except that you know exactly where everything lives.