Cutter 8
- vCPU
- 4 × dedicated
- RAM
- 8 GB
- Storage
- 160 GB NVMe SSD
- Transfer
- 10 TB
- IPv4 / IPv6
- 1 / /64 routed
Solution
Nextcloud is IO-bound and storage-hungry rather than CPU-hungry. Two cores and 4 GB serve a family; a 20-person team wants 4 cores and 8 GB with Redis and PHP-FPM tuning. Storage is the real decision: the Hold line gives you 2–16 TB at a price per terabyte that makes consumer cloud subscriptions look expensive.
| Resource | What you actually need |
|---|---|
| CPU | 2 cores for a household, 4 for a small team |
| RAM | 4 GB with Redis; 8 GB with full-text search |
| Disk | 2 TB and up on the Hold line |
| Stack | PHP 8.3, PostgreSQL or MariaDB, Redis, nginx |
Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.
Two terabytes is the sensible starting size.
Redis for file locking is not optional at any real scale.
Raise memory_limit to 1 GB and increase the OPcache interned strings buffer.
It costs performance; full-disk encryption plus TLS is enough for most threat models.
Nightly encrypted backups to another region, restic or Borg.
Budget 50–100 GB per active user for documents and photos, more if they sync video. Storage grows faster than you expect; the Hold line is priced so that over-provisioning is cheap.
It removes the provider's ability to read, scan or hand over your files, which no commercial service can offer. In exchange you own patching and backups.
PostgreSQL. Nextcloud supports MariaDB, but Postgres handles concurrent writes better and is what large installations run.