Self hosted business tools: the whole small-business stack, time tracking, wiki, the lot

Here is the short version: a small business can run nearly all its day-to-day software, the time tracking, the wiki, the file sync, the chat and the project boards, on one quiet server it owns, for the price of the box and a few dollars of power a month, instead of paying per-user SaaS fees forever. I do exactly this. The self hosted business tools I run cost me almost nothing each month and the equivalent SaaS bundle would be hundreds. The catch is not money. It is whether someone will look after the box. This is the real stack, the real maths, and the honest line on when to self-host and when to just pay.

The maths nobody does before they sign up

SaaS pricing is designed to feel small. Ten dollars a user here, fifteen there, eight for the little one, and each one is a "yeah, fine". Then you count up. A five-person shop running a time tracker, a wiki, a file-sync tool and a chat app is easily paying somewhere in the range of two to four hundred dollars a month once you are off the free tiers. That is a few thousand dollars a year, every year, rising as you add people, and at the end of it you own nothing.

The open-source versions of those exact tools cost zero in licence fees. Not a discount. Zero. You pay for the hardware once and the power to keep it on. So the question was never "is the software cheaper", because it always is. The real question is what the SaaS fee is actually buying you, and whether you need it.

What the SaaS fee is really for

Be honest about this or you will make a bad call. That monthly fee is renting you three things: someone else patches the software, someone else keeps it online, and someone else holds the backups. For a business with no technical person and no appetite to grow one, that is a fair trade: you are buying time you do not have. I am not anti-SaaS. I am anti paying SaaS prices for something you could run yourself in an afternoon and never think about again.

The line I draw is simple: own the tools where the cost is the data sitting there, rent the tools where the cost is keeping it running 24/7 for the public. Internal tools, the time tracking, your wiki, your files, your team chat, are cheap to host and forgiving if they blink for ten minutes during a reboot. That is the sweet spot for self-hosting. Anything customer-facing that must never go down is a different conversation, and often genuinely belongs in the cloud. I have written separately on when cloud hosting is the right call for a small business.

The stack I'd actually run

Every one of these is mature open-source software with an active project behind it. You do not need all of them. Pick the ones that map to a SaaS bill you are already paying.

• Time tracking, Kimai. The open replacement for the per-seat trackers. Projects, customers, timesheets, exportable invoicing reports. Runs in a single container. This alone often pays back the whole exercise.
• Wiki and docs, BookStack or Wiki.js. Your processes, your "how we do X", your client notes, in a clean searchable wiki you own. BookStack is the gentlest to set up; Wiki.js if you want Git-backed pages.
• Files and sync, Nextcloud. The big one. Your Dropbox/Drive replacement with desktop and phone sync, sharing links, calendars and contacts bolted on. It is the heaviest tool here, so give it the most RAM.
• Team chat, Rocket.Chat or Mattermost. A self-hosted Slack. For an internal team that mostly talks to itself, you will not miss the paid version.
• Project boards, Vikunja or Planka. Lists, kanban, due dates. Light enough to run on almost anything.
• The glue, Docker behind a reverse proxy. Run each tool as a container so they stay isolated and removable, put something like Caddy or Nginx Proxy Manager in front for clean URLs and automatic HTTPS, and you have a tidy stack instead of a pile of half-installed apps fighting over ports.

The hardware is smaller than you think

People picture a server room. The reality for a small team is one quiet box. A mini PC or a tidy second-hand business desktop with 16GB of RAM and an SSD will run that whole list at once without breaking a sweat, and it draws somewhere around 15 to 30 watts idle. On a Sydney power tariff that is a few dollars a month, not a line item you will notice. A Raspberry Pi will happily carry a couple of the lighter tools if you want to start tiny.

Two things matter more than raw grunt. First, the box has to stay on and survive a power blip, and a cheap UPS turns "the office flickered and everything's down" into a non-event. Second, it needs a sane network behind it. If you are self-hosting things you reach from outside the office, you want it sitting behind a properly set-up router and network, not exposed naked to the internet. The business networking and firewall setup underneath this matters as much as the apps on top.

The honest downsides

I would be doing you a disservice if I only sold the upside. Self-hosting moves three jobs onto you, and you have to actually do them:

• Updates. You patch the apps and the host OS. With Docker this is mostly pulling new images on a schedule, but it is not zero. Neglected self-hosted software is a security liability, full stop.
• Backups, the one people skip. Owning your data only helps if you can get it back. You need an automated nightly backup of the databases and files, off the box itself, ideally with one copy offsite. If you do not have a backup you can actually restore from, you do not have self-hosting, you have a single point of failure with extra steps. This is the same discipline behind a proper business backup, so do not start self-hosting without it.
• Being the helpdesk. When it breaks, you fix it. For a confident operator that is a Saturday morning. For everyone else, that is the value the SaaS fee was hiding.

Where I land on it

Own your stack, do not rent your dependence, but only where you will look after it. If you have someone in the business who enjoys this, self-hosting your internal tools is one of the highest-return moves a small operator can make: you stop paying rent on software forever, your data stops living on five different companies' servers, and nobody can hike a price or kill a feature you depend on. If you do not have that person, be honest, keep paying the fee, and put your energy into the work that actually makes you money. There is no shame in either. There is only shame in paying SaaS prices for tools you could own, or in self-hosting something critical you have no plan to back up. If you want the full picture on running IT this way without overspending, start with our guide to straight-talking managed IT for small business, and if you'd rather pay someone to run it, read what a real IT support SLA looks like before you sign one. Then come back and build the stack.

Weighing it up for your own setup and want a straight answer on what is worth self-hosting and what to leave in the cloud? That is exactly the kind of thing we work through with people, with no lock-in and no pushing gear you do not need. Tell us what you are running and what it is costing you, and we will tell you honestly where the money is.

Frequently asked questions