# Nextcloud VPS in Stockholm: self-hosting guide for 2026

URL: https://cloudj.net/blog/nextcloud-vps-sweden
Published: 2026-11-11 · Updated: 2026-11-11

> Run a Nextcloud VPS in Stockholm: pick a size, install Nextcloud All-in-One with Docker, plan disk growth and set up backups for a Nordic or EU team.

A Nextcloud VPS gives a team its own file sync, calendars, contacts and document editing on a server it controls, instead of renting space in someone else's cloud. Stockholm is a natural home for it if your team is in Sweden, the Nordics or northern Europe, and you want your files on an EU server. This guide takes you from an empty server to a working Nextcloud with HTTPS and backups, and spends extra time on the part people usually get wrong: storage.

If you are still weighing up European cities, the [Europe VPS guide](https://cloudj.net/blog/europe-vps-guide) compares them; the [best VPS in Sweden guide](https://cloudj.net/blog/best-vps-sweden) looks at Stockholm in detail.

## Why run Nextcloud on a Stockholm VPS

- **Data location you can state plainly.** Files sit on a server in Stockholm, inside the EU. That makes it easier to answer the "where is our data?" question from clients and auditors.
- **Close to the people using it.** A Nordic team syncing large folders all day benefits from a server in the region.
- **Room for sync traffic.** Monthly plans in Stockholm include 5 TB of traffic, which matters when every laptop and phone syncs the same folders.

Cloudj cloud servers in Sweden come in 30 ready-made plans or a custom mix of vCPU, RAM and disk. The [Sweden cloud server page](https://cloudj.net/cloud-servers/sweden) has the details.

When it is not a good fit: if your team lives mostly in the UK or North America, put the server nearer to them. A London server is described in the [London VPS guide](https://cloudj.net/blog/forex-vps-london) and an east-coast US server in the [New York VPS guide](https://cloudj.net/blog/forex-vps-new-york); both are written for traders, but the location notes apply to any workload.

## Step 1: size the server

Nextcloud is a PHP application with a database and, ideally, Redis. Users who only sync files are light; users who edit documents in the browser, run video calls with Talk, or use full-text search are heavy.

| Team | Starting size | Notes |
|---|---|---|
| 1 to 10 users, files and calendars | 2 vCPU, 4 GB RAM | Comfortable for All-in-One |
| 10 to 50 users, plus online office | 4 vCPU, 8 GB RAM | Office suites need RAM |
| 50+ users or heavy Talk usage | 8 vCPU, 16 GB RAM or more | Consider dedicated CPU |

Shared CPU is fine for a small team; general purpose or dedicated CPU makes sense once many people edit documents at the same time. You can resize CPU and RAM later from the console, so start at the smaller end.

## Step 2: plan storage before you upload anything

Storage is where most self-hosted Nextcloud projects run into trouble. Three habits avoid it:

1. **Estimate honestly.** Add up what people will actually upload in the first year, then add room for versions and trash. Nextcloud keeps old file versions and deleted files for a while, which can add a large share on top of live data.
2. **Separate data from the system.** Keep Nextcloud's data directory on its own path (for example `/mnt/ncdata`), so the operating system and the files do not compete and backups are simpler.
3. **Grow, don't migrate.** Cloudj lets you grow the server disk from the console. After growing it, extend the partition and filesystem on Linux. Plan the change for a quiet hour.

```bash
# after growing the disk in the console (ext4 root on /dev/vda1)
sudo growpart /dev/vda 1
sudo resize2fs /dev/vda1
df -h /
```

Set quotas per user in the Nextcloud admin panel from day one. It is much easier than asking people to delete files later.

## Step 3: prepare the server

1. Deploy Ubuntu or Debian in Stockholm from the [Cloudj console](https://app.cloudj.net) with an SSH key.
2. Point a DNS record such as `cloud.example.com` to the server's IP address.
3. Harden SSH and enable a firewall. Open 22, 80, 443 and 8080 (the All-in-One admin page, which you can close again after setup). Open 3478 TCP and UDP if you will use Talk. The [UFW firewall guide](https://cloudj.net/blog/ufw-firewall-vps) shows the commands.
4. Install Docker; the [Docker on a VPS guide](https://cloudj.net/blog/install-docker-vps) covers it.

## Step 4: install Nextcloud All-in-One

Nextcloud All-in-One (AIO) runs Nextcloud, its database, Redis, a web server with automatic HTTPS, and optional extras in containers managed by one master container. It is the simplest supported way to run Nextcloud on a single VPS.

```bash
sudo docker run \
  --init \
  --sig-proxy=false \
  --name nextcloud-aio-mastercontainer \
  --restart always \
  --publish 80:80 \
  --publish 8080:8080 \
  --publish 8443:8443 \
  --env NEXTCLOUD_DATADIR="/mnt/ncdata" \
  --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
  --volume /var/run/docker.sock:/var/run/docker.sock:ro \
  nextcloud/all-in-one:latest
```

Then open `https://your-server-ip:8080`, copy the passphrase it shows, enter your domain, and choose the optional containers (online office, Talk, full-text search). AIO requests a certificate for your domain and starts everything. Turn on only the extras you will use, since each one costs RAM.

If you prefer a manual install with Nginx and PHP-FPM, the [Nextcloud admin manual](https://docs.nextcloud.com/server/latest/admin_manual/) covers it. It gives more control but more upkeep.

## Step 5: backups you can actually restore

A file server without tested backups is a liability. Use more than one layer:

- **AIO's built-in backup.** AIO includes BorgBackup. Point it at a backup location, schedule daily backups, and run a test restore once.
- **Off-server copy.** Copy the Borg repository to storage outside the server, for example a second server in another city or an object storage bucket. A backup on the same disk does not protect you from losing the server.
- **Custom image after setup.** Saving a custom image of the configured server gives you a quick way to rebuild the system layer; your data still comes from Borg.

The [VPS backup strategy guide](https://cloudj.net/blog/vps-backup-strategy) explains how to choose frequency and retention.

## Step 6: keep it healthy

- Update through the AIO interface; it updates all containers together.
- Watch disk usage and RAM in the console metrics, and set an alert well before the disk is full.
- Check **Administration settings > Overview** in Nextcloud after each update; it lists warnings worth fixing.
- Enable two-factor authentication for admins.

## FAQ

### How much RAM does a Nextcloud VPS need?

For a small team using files and calendars, 4 GB RAM with 2 vCPU is a comfortable start with All-in-One. Add RAM before adding CPU if you enable online office or Talk.

### Can I add storage later?

Yes. You can grow the disk from the Cloudj console, then extend the partition and filesystem on the server. Keep the data directory on its own path to make this simple.

### Is Stockholm a good location for a team outside Sweden?

It suits teams in the Nordics and northern Europe well. If most users are elsewhere, choose a location closer to them.

### Should I use All-in-One or a manual install?

All-in-One is easier to install, update and back up on a single server. A manual install suits admins who need custom web server or PHP tuning.

## Deploy your Nextcloud server

Start with a modest Stockholm server in the [Cloudj console](https://app.cloudj.net), install All-in-One, and grow disk and RAM as your team's files grow. See live prices for Sweden on the [pricing page](https://cloudj.net/pricing).