Nextcloud Server: What It Needs and What to Run It On

A Nextcloud server needs less hardware than most guides claim. Nextcloud’s manual asks for 128 MB of RAM per PHP process, and its guidance for a single server stops at 100 users and 10 TB of storage. What really decides the machine is disk space, backups and bandwidth.

This guide sums up what the official manual says. It turns the per-process figure into a RAM chart, and it maps three team sizes to a dedicated server. If you are still comparing Nextcloud with a hosted service, read the cost comparison first.

What Does a Nextcloud Server Run?

A Nextcloud server runs five parts: a Linux system, a web server, PHP, a database and a memory cache. The Nextcloud 35 manual recommends Apache with mod_php or php-fpm, PHP 8.3 to 8.5, and PostgreSQL or MariaDB. It also calls memory caching highly recommended, and it says APCu together with Redis is the best choice for most new installations.

Flow diagram of a Nextcloud server: browsers and apps on desktop and phone send requests to a web server running Apache or Nginx, which passes them to PHP that runs Nextcloud, which uses a database and cache such as MariaDB and Redis, and finally the data disks that hold the files.

The manual’s own walkthrough installs Nextcloud on Ubuntu 24.04 with Apache and MariaDB, from the tar archive. We follow that route below.

How Much Hardware Does a Nextcloud Server Need?

Nextcloud does not publish one whole-server hardware table. Its manual sets memory per PHP process, and its guidance for one server is up to 100 users and 100 GB to 10 TB of storage. The exact CPU and RAM line for that band sits behind a subscription in Nextcloud’s customer portal.

Older manuals gave a number. The version 11 manual asked for one server with at least 2 CPU cores and 16 GB of RAM, for up to 150 users, as Nextcloud’s forum quotes it.

Table of what Nextcloud says about the size of one server: the version 35 manual asks for 128 MB of RAM per process at least and recommends 512 MB, the customer portal gives up to 100 users and 100 GB to 10 TB of storage for one server, and the older version 11 manual asked for 2 CPU cores and 16 GB of RAM for up to 150 users.

How Do You Size RAM From the Per-Process Figure?

Multiply the PHP processes that run at the same time by 512 MB, then add room for the database cache and the system. At the 128 MB minimum, 100 processes need 12.5 GB, and at the recommended 512 MB they need 50 GB.

Horizontal bar chart of RAM used by PHP processes at the recommended 512 MB each: 5 GB for 10 processes, 12.5 GB for 25, 25 GB for 50 and 50 GB for 100, with a dashed line at 64 GB marking the smallest Swify plan and the end of the bar at 128 GB.

However, processes are not users. Most people are idle at any moment, so measure your own peak before you size for the worst case. Even then, RAM is rarely what limits a Nextcloud server.

Nextcloud Server Hosting: Which Swify Plan Fits?

A Dedicated 1 fits a team inside Nextcloud’s 100-user band, and disks decide when to go bigger. The plans below start from the guidance above, so treat them as starting points and test with your own files.

Table of where to start with a Nextcloud server on a Swify plan: Dedicated 1 with 10 cores and 64 GB for up to 25 people and around 1 TB, Dedicated 5 with 20 cores and 128 GB for 25 to 100 people with document editing, any plan plus hard disks for archives of 10 TB or more, and a conversation first for more than 100 people.

What About Drives and Bandwidth?

Drives and bandwidth are the real limits, so size them first. A hard disk is the cheapest class per terabyte, and a full 1 Gbps port moves 450 GB an hour with no egress fees. Swify servers are also unmanaged with full root access, and both Debian and Ubuntu are on Nextcloud’s list.

How Do You Install a Nextcloud Server?

Install it from the official tar archive with Apache and MariaDB, which is the route the manual walks through on Ubuntu. Debian follows the same steps. The steps are short, and the order matters more than the commands.

1. Update the system, then install Apache, MariaDB and the PHP modules.
2. Create the database and a dedicated database user.
3. Download the archive, unpack it into the web root and give the web user ownership.
4. Create the virtual host and put TLS in front of it.
5. Run the installer, then add APCu and Redis as the memory cache.
6. Set up background jobs with cron, and test an upload before you invite anyone.

The updater’s own documentation warns about a trap: it does not back up your database or data directory. Make a backup before every update, as the section below explains.

How Do You Keep Nextcloud Safe?

Patch PHP and Nextcloud, put TLS in front, and keep a backup the server cannot overwrite. Nextcloud runs on PHP, so a flaw in the runtime reaches it directly. Every PHP branch that Nextcloud 35 supports got a fix in October 2026, and you only benefit if you install it and restart the workers.

• Patches: update PHP, then restart php-fpm or Apache so the new code is loaded.
• Transport: serve everything over HTTPS, and redirect plain HTTP.
• Access: keep SSH to keys, and expose only the ports you use.

What Should a Nextcloud Server Backup Contain?

A Nextcloud server backup contains five things: the config folder, the custom apps folder if you have one, the data folder, the theme folder and the database. That is the list in the Nextcloud 35 manual, which also says to copy them to a location outside your Nextcloud environment.

Table of what the Nextcloud manual says to keep in a backup: the config folder, the data folder and the database are all needed to restore, while the theme folder and the custom apps folder are needed only if you use a theme or custom apps.

How Do You Copy a Nextcloud Server Safely?

Put the server in maintenance mode while you copy, so no one changes a file mid-backup. The restore guide is blunt: you cannot finish a restore without the database, the data directory and the configuration files.

RAID does not replace any of this, because a mirrored disk copies a deletion as faithfully as a file. A separate machine works: a second server with large hard disks can hold the copies, and one more copy off-site makes the set stronger.

How Long Does a Nextcloud Restore Take?

At full line rate, 1 TB takes about 2.2 hours over a 1 Gbps port, and 10 TB takes about 22 hours. Real speeds are lower, so test a restore before you need it, and see how much of a faster port you really get in our 10 Gbps port guide.

Table of how long a restore takes at full line rate: 1 terabyte takes 2.2 hours over a 1 gigabit port and 13 minutes over a 10 gigabit port, 5 terabytes take 11.1 hours and 67 minutes, and 10 terabytes take 22.2 hours and 2.2 hours.

Nextcloud Server: The Short Version

A Nextcloud server needs a Linux system, PHP 8.3 to 8.5, a database and a cache, with disks and backups doing most of the sizing. RAM is rarely the limit, and the real work is patching and backing up.

• Size RAM from the per-process figure: 512 MB for each PHP process that runs at once.
• Start from Nextcloud’s own band: up to 100 users and 10 TB on one server.
• Back up five things, outside the server, before every update.

Frequently Asked Questions

What is a Nextcloud server?

What are the Nextcloud server requirements?

How much RAM does Nextcloud need?

How many users can Nextcloud handle on one server?

Is a dedicated server better than a VPS for Nextcloud?

How do I back up a Nextcloud server?

Do I need Redis for Nextcloud?

How long does it take to restore a Nextcloud backup?