How to Build Your Own Cloud Storage on a VPS

Files pile up faster than disk space clears out: photos from the last trip, work archives, project backups, conference recordings. Some people hand it all over to Google Drive or Dropbox, others stick with an old external drive buried in a desk drawer. There’s a third option: set up your own cloud storage on a VPS and keep full control over where the data physically lives, who can reach it, and what it costs. Why bother running a server yourself when ready-made services work out of the box? The answer is simple — once the amount of data or the number of users grows, the gap in price and flexibility becomes hard to ignore. What follows is a step-by-step walkthrough of building that storage, from picking a server to setting up backups.

What Cloud Storage on a VPS Is and How It Differs from Ready-Made Services

Cloud storage on a VPS is a virtual server running software for storing and syncing files: Nextcloud, ownCloud, Seafile, or something leaner like MinIO. From the outside it looks just like a familiar cloud drive — a web interface, desktop and mobile apps, a sync folder. The difference lies in who controls the infrastructure underneath.

Ready-made services like Google Drive or Dropbox keep files on someone else’s servers, under terms most people accept without reading closely. Self-hosted storage on a VPS shifts both the data and the rules of the game to the owner: disk space, user count, access policy, even the interface itself can all be changed without hitting a plan’s limits. There’s a flip side worth mentioning, too — server maintenance, updates, and backups now fall on the owner rather than a third-party support team.

People usually land on this option for one of two reasons: they want to cut costs on a growing data archive, or they need full control over sensitive information — contracts, medical records, financial reports. Either way, a VPS running open-source software covers the job without cutting corners on functionality.

Which Software to Choose: An Overview of Popular Options

How to Set Up Cloud Storage on a VPS: A Step-by-Step Process

In practice, the whole process fits into five stages: preparing the server, setting up the environment, deploying the application, configuring HTTPS access, and organizing backups. Here’s each stage in more detail.

Step 1. Choosing a VPS and Operating System

For home use or a small team, a virtual server with 2 CPU cores, 4 GB of RAM, and 40 GB of SSD storage is enough to run Nextcloud for up to 20-30 users. If the plan is to store video files, design assets, or project backups, it’s worth sizing up the disk from the start — resizing on the fly is far simpler than migrating a live system to a new server later. This is where a Serverspace VPS comes in handy, with hourly billing and the option to scale disk and memory without a reinstall — the configuration can grow along with the archive instead of being rebuilt from scratch. It’s also worth turning on automatic disk snapshots early, before the storage fills up with real files, since that adds an extra layer of protection. As for the operating system, Ubuntu 22.04 or Debian 12 are the usual picks — both are well documented and support Docker without extra hassle.

Step 2. Installing Docker and Docker Compose

Containerization simplifies both the initial setup and later updates: instead of manually configuring PHP, a database, and a web server, a single configuration file does the job. Setting up PHP modules and a web server by hand eats up hours and almost always ends in a version conflict — a container sidesteps that problem entirely through environment isolation. Connect to the server over SSH and install Docker:

curl -fsSL | sh

Then confirm that Docker Compose is available as a plugin:

docker compose version

Step 3. Deploying Nextcloud with Docker Compose

Create a working directory and a docker-compose.yml file with two services — a MariaDB database and Nextcloud itself. In a minimal setup, the file defines a volume for data, a volume for the database, and exposes port 8080. Once the file is saved, the containers spin up with a single command:

docker compose up -d

A minute or two later, the web interface becomes available at the server’s address on port 8080 — that’s where you set the admin login and connect the database defined in the configuration. After the first login, the setup wizard will ask for a data storage path — it’s worth pointing this to a separate, larger volume right away rather than the system disk, so there’s no need to migrate gigabytes of files by hand later.

Step 4. Configuring Nginx and an SSL Certificate

Exposing storage to the internet without encryption is a bad idea — passwords and files would travel in plain text. Nginx sits in front of Nextcloud as a reverse proxy, with Let’s Encrypt handling certificates through certbot:

sudo apt install nginx certbot python3-certbot-nginx

Once the proxy configuration is in place, the certificate is issued with a single command:

sudo certbot --nginx -d cloud.example.com

A Let’s Encrypt certificate is valid for 90 days, but certbot adds its own scheduled task and renews it without any manual work — it’s still worth confirming that auto-renewal actually works by running a dry test with

sudo certbot renew --dry-run

. From this point on, the storage is reachable over HTTPS, and browsers and mobile clients stop flagging the connection as unsafe.

Step 5. Backups and Monitoring

Running your own server also means taking on responsibility for keeping the data safe. A simple but effective solution is a daily export of the data volume and a database dump to external storage using rsync or restic on a cron schedule. For monitoring, options range from a basic script that sends a Telegram alert once disk usage passes 85%, to full monitoring stacks like Zabbix or Netdata — the right choice depends on how many servers need to be watched at once. A disk that fills up completely is one of the most common reasons Nextcloud stops accepting new files.

What to Do When Data Grows Faster Than Expected

Sooner or later, the disk fills up faster than projected — that’s the rule rather than the exception. A VPS has a clear edge over physical hardware here: the disk can be resized through the control panel in a couple of minutes, with no downtime and no migration to new hardware. After the virtual disk is expanded, the only remaining step is to grow the filesystem with a command like resize2fs or its equivalent for the chosen filesystem — Nextcloud picks up the new capacity automatically, since it runs on top of a regular directory rather than a fixed-size block. If data growth is predictable — say, a team adds several gigabytes of reports and design files every week — it’s worth planning the disk expansion ahead of time instead of waiting for a low-space warning.

Pros and Cons of Self-Hosted Cloud Storage

At first glance, the difference between rented cloud storage and a ready-made service looks small — both sync files across devices. But there’s more going on behind the scenes, and some of it only becomes noticeable after a few months of actual use.

The line about maintenance tends to get the least attention — which is a mistake, since an administrator’s time costs money too, even when it doesn’t show up as a separate line item on an invoice.

Limitations and Risks Worth Knowing Upfront

Self-hosted storage solves part of the equation, but it also creates new points of responsibility. Most of these risks are manageable, as long as they’re accounted for before launch rather than after the first incident.

• Software updates fall on the server owner: a missed Nextcloud security patch can leave an exploitable gap open.
• Disk or VPS failure without configured backups means losing the entire archive — the provider is responsible for the infrastructure, not the contents of the disk.
• The server’s network bandwidth caps how fast large numbers of files can sync at once.
• Without proper firewall and SSH configuration, storage becomes an easy target for password brute-forcing and scanning bots.

Standard measures cover much of this ground: fail2ban against brute-force attempts, ufw to close off unused ports, and unattended-upgrades to keep system packages current automatically. None of it requires deep expertise — just consistency. It would be a mistake to expect a VPS provider to secure the data inside the virtual machine itself — they’re responsible for the physical infrastructure, not for what happens inside the operating system the server owner administers.

For companies handling customer personal data, it’s worth checking in advance where the provider’s servers are physically located — data localization requirements vary by industry and jurisdiction. Self-hosted storage on a VPS has an advantage here over a ready-made service: the server location can be chosen deliberately, rather than adapting to whatever infrastructure the vendor happens to use.

Practical Use Cases

Family Photo and Video Archive

Instead of scattered copies across phones and laptops, a single storage location syncs automatically through the Nextcloud app. Parents and kids get access to shared albums, and phone storage frees up without the risk of losing photos. It works especially well with background auto-upload from a phone — the archive grows without anyone lifting a finger.

File Sharing for a Small Team

For a team of 5-15 people, self-hosted storage covers shared access to design files, contracts, and technical documents without paying for extra seats on a third-party corporate plan. Access permissions are flexible: some folders can be read-only, others locked away entirely from outside eyes.

Storing Project Backups and CI/CD Artifacts

Developers often use VPS storage as an intermediate spot for builds, database dumps, and CI/CD logs — connecting through WebDAV or MinIO’s S3-compatible API drops it straight into a pipeline. This approach takes load off the main repository and speeds up rolling back to a previous build after a failure.

Workstation Backup

Nextcloud clients for Windows and macOS can run in one-way backup mode — handy for remote employees whose laptops aren’t covered by a corporate backup policy.

A Home Media Server

It’s common to run Jellyfin or Plex alongside Nextcloud on the same VPS, pairing an archive with a media library that’s reachable from anywhere, without being tied to a single service. A film and TV library stays accessible at home and on the road — without a monthly subscription to yet another streaming platform.

Common Mistakes When Setting Up Self-Hosted Storage

Most problems with self-hosted storage don’t show up at setup — they surface a couple of months into actual use, once the server has been left to run on its own.

• Storage gets launched without HTTPS “temporarily,” and the certificate never gets set up afterward.
• Backups are stored on the same disk as the primary data, so a drive failure wipes out both at once.
• The admin password stays at its default or stays too simple, and two-factor authentication never gets turned on.
• The disk fills up with no warning, since free-space monitoring was never set up from the start.
• Updates keep getting pushed off indefinitely, letting vulnerabilities pile up in outdated software versions.

Any one of these mistakes rarely causes a disaster on its own, but together they add up to a scenario where recovering the data stretches into days — if it’s still possible at all.

Conclusion

Self-hosted cloud storage on a VPS is a trade-off between the convenience of a ready-made service and full control over the infrastructure. Initial setup takes a couple of hours, and ongoing maintenance comes down to regular updates and checking that backups actually work. In exchange, the data stays exactly where the owner decided to keep it, rather than wherever suits a third-party provider. For more on server setup and other developer tools, check out the Serverspace blog.

FAQ