Building a Lightweight Knowledge Base for a Small Team: Migrating from Nextcloud to Cloudreve

One server, two containers, 1.6 GB RAM—handling online preview and streaming for 100 GB of company assets.

Plus three gnarly bugs that took me the better part of a day to track down.

Why We Ditched Nextcloud

Our company has about two dozen people. Over the years, we accumulated more than 100 GB of data on Nextcloud: product docs, project artifacts, training videos, and presales decks. The data is valuable, but the system became increasingly painful to use:

• Heavy. Nextcloud (PHP) + OnlyOffice Document Server routinely consumed over 4 GB of RAM, with OnlyOffice alone eating 2–3 GB.

Building a Lightweight Knowledge Base for a Small Team: Migrating from Nextcloud to Cloudreve

Related reading

#10 The Week I Held My Breath: Moving to a Real Server

I used JSON files instead of a database for 1,699 records. Here's what actually…

Migrating a 5-year-old React admin app from CRA + Webpack to Vite + SWC — 166…

We built 126 browser tools with zero uploads. Here is what broke along the way

A Free Server Caught the GUI Fallback a Model Buried in a CLI

I Consolidated My Entire Developer Homelab onto One Machine — Here's the Full…