Self-hosting Nextcloud in 2026 is genuinely simple: the official path is the Nextcloud All-in-One (AIO) Docker image, which spins up the full stack — files, database, cache, office editing, and encrypted backups — from a single command. You point a domain at your server, let it fetch an SSL certificate automatically, and you own your cloud.
Short answer
To self-host Nextcloud in 2026, install Docker on a Linux VM, run the official Nextcloud All-in-One (AIO) master container with one docker run command, open the AIO admin panel on port 8080, point a domain at the server for automatic Let's Encrypt SSL, then create users, add storage, enable apps, and schedule BorgBackup — all from the AIO web interface.
I am Manoj, an ERPNext implementation consultant at Mith Tech in Bengaluru. Self-hosting Nextcloud sits close to the work I do every week: helping Indian SMBs run their own open-source stack instead of renting it. I have deployed Nextcloud on the same VMs where clients run ERPNext, so this guide reflects a working setup, not a lab demo. My honest take: AIO removed almost all the pain that used to make people give up on self-hosting Nextcloud — the manual database, cache, and TLS wiring is now handled for you.
Why self-host Nextcloud instead of renting cloud storage?
Owning your file storage means your documents, contacts, and calendars live on infrastructure you control, under Indian data-residency terms you set. Nextcloud is open source under AGPLv3, so there is no per-user subscription and no cap on how much you store beyond your own disk. Pricing for managed alternatives varies by edition — check the vendor's official page.
For a growing SMB the trade is straightforward: rented cloud storage bills per user forever, while a self-hosted instance costs you a VM and some maintenance time. Nextcloud also does more than files — calendars, contacts, in-browser document editing, and video calls all run from one login. If you are weighing the models, my longer comparison in the open-source Dropbox alternative guide lays out where each approach fits.
Skimmable summary: Self-hosting gives data ownership and a no-per-user licence model; rented storage bills per seat indefinitely.
What do you need before installing Nextcloud?
A minimum viable setup is one Linux virtual machine with at least a couple of CPU cores, a few gigabytes of RAM, disk space sized to your files, and Docker installed. A registered domain name and open ports 80 and 8443 let AIO fetch a trusted SSL certificate automatically. Root or sudo access is required.
| Requirement | Recommended for a small team | Notes |
|---|---|---|
| OS | A current Linux distribution | Ubuntu, Debian, and similar all work |
| CPU / RAM | 2+ cores, 4 GB+ RAM | More if you enable office editing or antivirus |
| Storage | Sized to your data | Separate data volume is cleaner to back up |
| Docker | Official Docker Engine | Snap-based Docker is not supported |
| Domain | One domain or subdomain | Needed for automatic SSL |
| Ports | 80, 8080, 8443 | 80 and 8443 for certificates; 8080 for AIO admin |
Avoid the snap version of Docker
Nextcloud AIO does not support a snap-based Docker installation, which is a common default on Ubuntu. Install Docker Engine from Docker's official repository instead, or the master container will fail to manage its child containers.
Skimmable summary: You need a Linux VM, official Docker Engine (not snap), a domain, and open ports 80/8080/8443.
How do you install Nextcloud with Docker AIO?
Installation is a single docker run command that launches the AIO master container, followed by browser-based setup on port 8080. The master container then creates and manages every other container — Nextcloud, database, cache, and backups — for you. The whole process from a clean Docker install to a working instance typically takes around ten minutes.
Install Docker Engine
Install Docker from the official Docker documentation for your Linux distribution. Confirm it works with sudo docker run hello-world. Do not use the snap package.
Run the AIO master container
Launch the officially recommended command:
sudo docker run \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest
Open the AIO admin interface
Browse to https://your-server-ip:8080, accept the self-signed warning, and copy the passphrase AIO generates. Store it safely — it is your recovery key.
Enter your domain
Type the domain you have pointed at the server. With ports 80 and 8443 reachable, AIO validates the domain and provisions a Let's Encrypt certificate automatically.
Start the containers
Pick your optional services, then click to download and start the stack. AIO pulls the Nextcloud, database, cache, and backup containers and brings them online.
Always follow the current command from the official Nextcloud AIO repository, since flags occasionally change between releases.
Skimmable summary: One docker run command starts the AIO master container; the rest is done in the browser on port 8080.
How do you set up SSL and a domain?
SSL is handled for you when a public domain resolves to your server and ports 80 and 8443 are open through your firewall or router. During AIO setup you enter the domain, and the master container requests and installs a Let's Encrypt certificate without any manual OpenSSL or Certbot work. Renewal is automatic thereafter.
If your server sits behind an existing reverse proxy — Nginx, Caddy, or Traefik — AIO supports that too, but the configuration differs. In that case the reverse proxy terminates TLS and forwards to AIO's internal Apache container. For a first deployment, the direct method with open ports is simpler and the one I recommend to most SMB clients.
Point the domain first
Create the DNS A record for your domain before running AIO setup and give it time to propagate. Certificate issuance fails if the domain does not yet resolve to your server's public IP.
Skimmable summary: Open ports 80/8443, point a domain at the server, and AIO fetches and renews a Let's Encrypt certificate automatically.
How do you add users, storage, and apps?
User and app management all happen inside Nextcloud's own web interface after first login, not in the AIO panel. As administrator you create accounts under Users, set group memberships and quotas, then hand out credentials. Apps are enabled from the Apps section. External storage and data-directory sizing are configured through admin settings.
- Users: Add accounts individually or via bulk import, assign group quotas, and enable two-factor authentication for everyone.
- Storage: Grow the data volume on the host as files accumulate; a dedicated volume keeps backups and expansion clean. External S3-compatible or SMB storage can be mounted through the External Storage app.
- Apps: Enable Calendar, Contacts, Notes, Deck, and the office suite from the app store. Nextcloud Office (Collabora) and other document editors ship as optional AIO services.
For teams that also run business software, Nextcloud pairs well with an ERPNext deployment — document collaboration on one side, operations on the other. Our managed Nextcloud offering covers exactly this setup for SMBs that would rather not run it themselves.
Skimmable summary: Create users, set quotas, and enable apps inside Nextcloud's web UI; grow storage on the host volume as needed.
How do you back up a self-hosted Nextcloud?
Backups run through BorgBackup, which ships inside AIO and produces encrypted, deduplicated, incremental snapshots of your files, database, and configuration. From the AIO admin interface you set a backup target — a local mounted disk or a remote location — pick a schedule, and AIO handles the rest. Restoring is a single operation from the same panel.
Because only the first backup copies everything and later runs store only changes, backups stay fast and storage-efficient. My standard advice to clients: keep at least one backup off the host, test a restore before you rely on it, and note the AIO passphrase somewhere outside the server. A backup you have never restored is a hope, not a plan.
Keep a copy off the machine
Store at least one BorgBackup copy on separate hardware or a remote target. If the host disk fails, an on-disk-only backup fails with it.
Skimmable summary: BorgBackup inside AIO makes encrypted, incremental, scheduled backups; keep one copy off-host and test the restore.
Should you run Nextcloud on a VM or managed platform?
The decision comes down to how much operations work your team wants to own. A self-managed VM gives full control and the lowest running cost, at the price of your time for updates, monitoring, and security patching. A managed or platform-hosted deployment trades some control for someone else handling the maintenance, which suits teams without in-house sysadmin capacity.
| Approach | Control | Maintenance burden | Best for |
|---|---|---|---|
| Self-managed VM | Full | On you | Teams with sysadmin skills |
| Platform / managed | Shared | Mostly handled | Teams wanting to focus on their business |
Both are valid. Many SMBs start self-managed and move to a managed model as their data grows. If you would rather deploy Nextcloud on managed infrastructure alongside other open-source tools, our PaaS approach and the broader Frappe/ERPNext platform work follows the same self-hosted, no-lock-in philosophy.
Skimmable summary: A VM gives control and low cost but you own maintenance; managed hosting handles upkeep for teams without sysadmins.
Frequently asked questions
Is Nextcloud really free to self-host?
Yes. Nextcloud Server is free and open source under the AGPLv3 licence, with no per-user fees and no storage caps beyond your own disk. Your only costs are the server (a VM or your own hardware) and the time to maintain it. Optional paid support subscriptions exist, but they are not required to run Nextcloud.
Which install method should I use in 2026?
Use Nextcloud All-in-One (AIO), the officially recommended method. AIO packages the full stack — Nextcloud, database, cache, office editing, and backups — into containers managed by a single master container. It handles version upgrades and database migrations for you, which is why it has replaced the old manual LAMP-stack installs for most people.
Do I need Linux, or can I use Windows?
Linux is the cleanest host for Nextcloud AIO, and it is what I recommend. AIO can run on Windows and macOS via Docker Desktop for testing, and on some NAS devices, but production self-hosting is most reliable on a Linux VM with official Docker Engine installed. Avoid the snap-based Docker package on Ubuntu.
How much server does a small team need?
A small team can start with a modest VM: a couple of CPU cores, around 4 GB of RAM, and disk sized to your files. Enabling heavier optional services like in-browser office editing, full-text search, or antivirus scanning increases the requirement, so provision headroom if you plan to use them.
How do I keep Nextcloud updated and secure?
AIO manages Nextcloud and container updates from its admin panel, including database migrations, so you approve upgrades rather than performing them by hand. Beyond that, keep the host OS patched, enable two-factor authentication for users, restrict admin access, and run regular BorgBackups. Review the built-in security scan under admin settings periodically.
Can Nextcloud replace my business file-sharing tool?
For most SMB file sync, sharing, and document collaboration needs, yes. Nextcloud covers file storage, shared links, calendars, contacts, and in-browser editing from one open-source platform you control. Whether it fully replaces a specific tool depends on your workflows — the qualitative comparison in the open-source Dropbox alternative guide helps you decide.
About the author
I am Manoj, an ERPNext implementation consultant at Mith Tech, an independent open-source implementation studio in Bengaluru. I help Indian SMBs deploy and run open-source software — ERPNext, Frappe, and self-hosted tools like Nextcloud — on infrastructure they own, without per-user licensing or vendor lock-in. I write from real deployments, not theory.