Guide · Infrastructure
How to self-host Nextcloud for a small team
The question behind most "should we self-host" debates is really "what does it take." Here is the shopping list for a team of five to fifty, hardware, skills, and the recurring work nobody mentions in the brochure.
What you actually need
- A server. Either a small VPS (a few euros a month is enough for a dozen users) or managed Nextcloud hosting (roughly €10-30 a month, and the provider handles updates and backups for you). An old office PC under a desk also works, if someone accepts that they are now the person who notices when it stops.
- A domain and TLS. A hostname pointing at the server and a certificate, free via Let's Encrypt, renewed automatically on every sane setup.
- Backups that someone tested. The database and the data directory, off the same machine, on a schedule. A backup that has never been restored is a hope, not a backup.
- One person who owns it. Not a department, a named human who installs updates, adds users, and reads the admin page occasionally. For a small team this is genuinely a few hours a month once it settles, but those hours must exist in someone's role.
The recurring work, itemized
App and server updates (monthly-ish, more if security releases land), certificate and backup monitoring, user onboarding and offboarding, and the rare-but-real "why is the disk full" afternoon. None of this is hard; all of it is unglamorous. The organisations that succeed at self-hosting are the ones where "the Nextcloud person" is a role written down somewhere, not an accident of who installed it first.
When it is the wrong answer
If nobody in the organisation can or wants to own the server, do not self-host, pay for managed hosting or use a SaaS and spend the difference on something else. Self-hosting fails not from complexity but from abandonment: an instance nobody updates slowly becomes a liability, while the data on it keeps mattering. Our admin-quit guide covers exactly what continuity looks like when the owner leaves.
Where our apps fit the bill
Everything we ship is a Nextcloud app, which means there is exactly one platform to maintain, not one per product. Once the instance runs, adding ArbeitszeitCheck or DutyCheck is an install from the app store, not a new vendor contract, a new login system, or a new place where employee data lives. The server is the price of admission for the whole suite, paid once.
If you want the capability without the chores, managed Nextcloud hosting is the middle path: the data stays in a datacenter you chose, our apps run unchanged, and the "who updates it" question becomes a line item instead of a person.