Neither side is “the cheap one” in general. Cloud charges rent forever; a local server charges once and asks for care. The right answer falls out of three numbers: your team size, your data size, and your internet quality.
Every figure below is a clearly labelled example — cloud prices and plans change, so check the current per-user price before a real decision. The structure of the maths does not change: cloud cost scales with people, local cost scales with data, and each side hides costs the brochure does not lead with. Run your own numbers through the same three sections.
Business cloud storage is sold per user, per month. Multiply your quoted price by your headcount and by 36 months before comparing anything — a fee that looks trivial for one person becomes the largest IT line in the budget at fifteen people over three years, and it never stops while you use the service. What the rent genuinely buys: zero hardware, access from anywhere without VPN work, backups and uptime handled by the provider, and painless growth one seat at a time. For a three-person office, that bundle is honestly hard to beat.
A file server is a capital purchase: the PC or a TrueNAS build, two data disks, a small UPS — one bill, typically comparable to a few months of cloud rent for a mid-size team. Running costs are electricity (a modest modern build sips power; an old tower drinks it — measure yours), an internet connection you already have, and one disk replacement across three years as a planning allowance. Adding your eleventh employee costs nothing on the server side. The crossover most offices find: below roughly five users cloud wins on total cost and effort; somewhere in the high single digits the local server starts paying for itself.
Three the quote omits. Internet dependency: a cut connection or a slow line turns "open the 800 MB project folder" into a coffee break, and big uploads on asymmetric connections are measured in hours. Data gravity: the more you store, the more painful leaving becomes — downloading terabytes out is slow, and some plans meter it. Discipline drift: personal free accounts and shared links multiply until nobody knows where the company's only copy of something lives. None of these are arguments against cloud; they are the true price lines to add under the subscription.
Also three. Admin time: someone owns updates, users, and the backup check — an hour a month when set up as this series describes, a weekend of panic when not. Failure is yours: when the server dies at 9 AM, the repair clock is yours too; the mirror, snapshots and offline copy in this series exist precisely to keep that morning boring. Remote access work: outside access means the VPN setup from this series — fifteen minutes once, but it is your fifteen minutes, not a feature you were sold.
The mature answer is rarely pure. The bulk data lives locally — accounts, projects, media, the terabytes that are slow and expensive in cloud — while a small cloud layer handles email, documents that travel, and phone-photo-class convenience. Some offices also use cloud as the server's offsite backup copy, which quietly satisfies the 3-2-1 rule. Decide by data type, not by ideology, and revisit the maths whenever headcount doubles — the crossover point moves as you grow.
The video builds the local side of this comparison — watch what the hardware actually is, then run your own three-year numbers with your real cloud quote.
▶️ Watch Full VideoNo. For two to five users with modest data, cloud subscriptions usually cost less in total once you honestly count admin time — and they remove hardware risk entirely. Local wins on cost as team size and data size grow, and wins on speed for large files at almost any size, because your LAN is faster than your internet connection.
Because the company then owns nothing: files live in accounts that walk out with employees, storage fragments across a dozen 15 GB silos, there is no central permission control, and recovering a leaver's files becomes a negotiation. Business data belongs in accounts the business controls — a business cloud plan, or your own server.
For office documents, a stable connection matters more than a headline number — but moving hundreds of gigabytes (video projects, disk images, design archives) stays slow on anything a small office typically buys, especially uploads. That asymmetry is the permanent home-field advantage of the local server: gigabit on your LAN, every hour of the day.