Instead of Google Drive

A client rang me in a genuine panic. An employee had left the company two weeks earlier, on good terms, and now nobody could open three years of project documentation. The files had lived in that person's personal cloud account, shared into a folder everyone used. When the account went, the sharing went with it.

Nothing had been stolen and nobody had done anything wrong. The company simply discovered, at the worst possible moment, that it did not own the arrangement its work depended on. That call is the reason I am fairly evangelical about this particular piece of software, and I should say up front that I sell it preinstalled, so weigh what follows accordingly.

What Nextcloud actually is

Think of it as the file-sharing service you already use, except the server is a machine you own and the account list is one you control.

In practice that means a folder on every computer that syncs automatically, an app on every phone, a web interface for when you are on somebody else's machine, and a link you can send to a client who does not have an account. Calendars and contacts synchronise as well, which is the part people underestimate — a shared company calendar that does not depend on anybody's personal account is worth more than it sounds.

The difference that mattered for my panicking client is structural rather than technical. Accounts belong to the organisation. When somebody leaves, an administrator reassigns their files in about a minute, because the data was never in a personal account in the first place. That is not a feature Nextcloud has and the alternatives lack — the big providers have business plans that handle this properly too. It is what you get by default when the server is yours, rather than what you get if somebody remembered to buy the right tier.

What changes on the first day

Honestly, for the person using it: almost nothing, and that is the point. A folder appears. Files put in it show up on the other machines. If anything about the daily experience is dramatic, the setup was done badly.

What changes on the first day is on the other side. Storage stops being a monthly quantity you are billed for and becomes a disk with a size. Adding space means adding a drive, once. For a company generating photographs, video or scanned documents — the workloads where subscription storage becomes genuinely expensive over a few years — that single change tends to dominate the economics.

And one thing changes that nobody asks about until later: you can read the storage directly. The files on the disk are ordinary files in ordinary folders. If Nextcloud vanished tomorrow, the data would still be sitting there, openable by anything. That is the property I check for in any system I put a client's work into, and a surprising number of products fail it.

The work you are taking on

This is where most articles on this subject stop being useful, so let me be specific about the bill.

Updates. Nextcloud releases regularly and the updates include security fixes. A server nobody updates is worse than the subscription it replaced, because the subscription was being patched by people paid to do it. On the machines I hand over this is configured to happen without anybody remembering, and I say that plainly because an unmaintained server is the most common way this ends badly.

Backups. Your own server means your own copy, and "the files are on the NAS" is not a backup — it is one copy on one device in one building. A drive failure, a theft or a flood takes the lot. This deserves its own article and has one, but if you take nothing else from here: the server needs a copy somewhere that is not the server.

Access from outside. Getting to your files from a café is the part people expect to be hard, and it is the part where mistakes are dangerous. Exposing a server directly to the internet without knowing what you are doing is how small companies end up in ransomware statistics. There are sane ways to do it — an encrypted private network between your devices is the one I use, because it opens nothing to the public at all.

When I tell people not to do this

When there is nobody to own it. A server with no responsible person is a liability with a power cable. If the answer to "who updates this?" is a shrug, a subscription with a support line is genuinely the better engineering decision, and I will say so even though it costs me a sale.

When the team is genuinely distributed and lives inside a suite of collaborative documents with several people typing into the same file simultaneously. Nextcloud does collaborative editing and it works, but the big providers have poured a decade of engineering into that specific experience and it shows. Pick the tool that fits the work, not the philosophy.

Where it fits best, in my experience, is the unglamorous middle: a few people, a lot of files, work that must stay available and must not depend on any one person's account. That describes most of the small companies I deal with, and it described my panicking client exactly. He has his three years of documentation. It is on a machine in his own office, and when the next person leaves, nothing will happen.