One small mini PC runs our whole business: what we self-host and what it costs
A palm-sized mini PC runs our email, files, invoices, monitoring and smart-home hub. What runs on it, what to watch for, and what it really costs each month.

The machine that runs our company is palm-sized. It idles at about 4 to 6 watts and rarely passes 15 at the wall, so it costs less to run than a bulb (approximate, we have not metered it). When we last counted, it was running 38 containers: email, files, our quote and invoice portal, monitoring, and the smart-home hub.
Here is what runs on it, the mistakes to avoid, what it costs, and when we would pay for cloud instead.
Why one small box
Cloud subscriptions are priced per seat, per month, forever. A mini PC flips that: you pay once for the hardware, a little each month for electricity, and your time.
Hosted mail alone runs ₹125 to ₹700 per user per month, so three people pay roughly ₹4,500 to ₹25,000 a year before file storage or an invoicing app. A ₹20,000 box plus about ₹100 a month of electricity pays back in one to a few years. Approximate.
Ours is a GEEKOM mini PC with an Intel N150, a four-core low-power chip, 16 GB of RAM and a 512 GB NVMe drive. Its integrated GPU runs the camera software's detection and video decoding, leaving the main cores free.
When not to do this. It trades money for attention. Skip it if:
- power cuts are frequent and you have no UPS;
- your upload speed is slow (under about 20 Mbps);
- a service being down for a day would cost you a client;
- nobody will spend an hour or two a month on upkeep.
What runs on ours
Almost everything runs in Docker containers, in a few compose files:
- Smart home: Home Assistant, the Mosquitto MQTT broker, Zigbee2MQTT for wireless sensors and bulbs, and Frigate for cameras. Two small IR bridges for the air conditioners run as plain system services.
- Business: Mailcow for company email, Nextcloud for files and sharing, and our own quote and invoice portal.
- Keeping watch: Uptime Kuma, ntfy for phone alerts, n8n for small automations, and Homarr as the dashboard.
- Plumbing: Caddy as the reverse proxy, Watchtower for image updates, and Autoheal to restart anything unhealthy.
We removed OnlyOffice because nobody used it.

What you need
- Mini PC, N100 or N150 class, 16 GB RAM, 500 GB NVMe: about ₹15,000 to ₹25,000 (used: ₹8,000 to ₹15,000).
- Separate storage for files and backups: about ₹9,000 to ₹18,000 for a 2 TB SSD or 4 TB hard drive.
- A UPS in the 600 to 1,000 VA range: about ₹3,000 to ₹6,000.
- A domain name: about ₹800 to ₹1,500 a year.
- A broadband line you already pay for, and a router you can configure.
How we set it up
-
Install a plain Linux server and Docker. We use Ubuntu. When it works,
docker psanswers with an empty list. -
Put a reverse proxy in front. Caddy takes all web traffic and gets HTTPS certificates automatically. A new service is three lines:
files.example.com { reverse_proxy nextcloud:80 }Caddy fetches the certificate the first time the name is requested, so the padlock appears within about a minute.
-
Sort out reachability. Home lines usually get a changing address. Run a DDNS updater every few minutes (ddclient or your registrar's client), or use a tunnel such as Cloudflare Tunnel or Tailscale and open nothing on the router. A tunnel covers web services; mail also needs DNS plus port forwarding. When it works, your names resolve from a phone on mobile data.
Home lines drop more often than you think, so every compose service carries
restart: unless-stoppedand monitors retry twice before alerting. After a drop everything comes back without anyone touching it. -
Check port 25 before you plan email. Many lines block it. Test from the box:
nc -zv -w5 gmail-smtp-in.l.google.com 25. A reply means outbound 25 is open; a timeout means your ISP blocks it. We send through a relay service either way, because residential addresses have poor sending reputation, and the relay handles SPF. -
Add services one at a time. Bring one up, put it behind the proxy, add a monitor, then move on.
-
Set up nightly backups to a separate drive, NAS or machine, not the same disk. Ours is a cron job at 3 a.m. It dumps every database with
docker exec, checks each dump is above a minimum size, archives Mailcow's mail, copies the compose files and configs across withrsync, deletes old dumps after seven days and old mail archives after 30, then posts to ntfy withcurl. Mailcow's ownbackup_and_restore.shand restic are worth adding. -
Then restore something. Start a temporary database container of the same version, pipe the dump in (
docker exec -i tmpdb psql -U user dbwith the dump on stdin, or the MySQL equivalent), run one count query on a table you know, then remove the container. When it works, the count matches the live app. Do it once a quarter. -
Plug in the UPS. A 600 to 1,000 VA line-interactive UPS carries a 20 to 25 W load for half an hour or more (approximate). Pick one with USB so NUT or apcupsd can shut the box down cleanly when the battery runs low, and put the router and fibre ONT on it too, or the box stays up but offline.
What goes wrong, and the fixes
All are common, and we check for each on our own box.
Backups that only say they worked. A common trap: the database dump command changes in a newer image, and the nightly job keeps writing a tiny error file while reporting success. Alert on any dump under 10 KB, and restore one every quarter. Better still, have the script ping an Uptime Kuma push monitor only if the newest dump is under 24 hours old and above a minimum size. If the ping does not arrive the monitor goes red and ntfy buzzes the phone. An exit code of zero is not evidence.
Unclean reboots. On patchy power, a box without a UPS can restart uncleanly several times a week. Fix: the UPS, and monitor retries so a short restart wakes nobody.
The drive that mounts late. If the recordings drive takes 30 seconds or so to mount and Docker starts first, Frigate records onto the internal disk underneath the empty mount point. Fix: sudo systemctl edit docker.service and add [Unit] / RequiresMountsFor=/mnt/recordings (your own mount path). After a reboot, docker ps only starts once the drive is present.
USB drives hanging the boot. Several SSDs on one USB hub can stall a cold boot. Fix: connect drives directly and mount them with noauto,x-systemd.automount,nofail,x-systemd.device-timeout=10 in fstab, so a slow or missing drive no longer blocks boot.
Watchtower updating itself mid-run. It can leave other containers removed rather than restarted; docker compose up -d brings them back. Stop it updating itself: put the label com.centurylinklabs.watchtower.enable=false on its own service. Add a check script that compares docker compose config --services with docker compose ps --services --status running and posts to ntfy when they differ.
Background jobs left to page loads. By default Nextcloud runs its housekeeping only when someone loads a page, so on a quiet server jobs pile up. Fix: in Nextcloud admin settings set Background jobs to Cron, then on the host add */5 * * * * docker exec -u www-data nextcloud php cron.php (container name as in your compose file). The admin page then shows a recent last run instead of a red warning.
Update discipline
- Pin versions for anything with a database. Our Nextcloud image is pinned, not
latest, and goes up one major at a time with a dump first. - Mailcow only through its own update script. It is 18 containers that depend on each other, so Watchtower leaves them alone. Frigate is updated by hand too.
- Watchtower for the boring rest, with notices to ntfy.
Monitoring
Uptime Kuma runs about 55 checks in seven groups. Things that are not containers, like disk health, report in from small host scripts.
A typical check: an HTTP monitor on your file server's status URL, 60 second interval, 2 retries, ntfy as the notification. The phone shows "Down: Files", then a few minutes later "Up: Files, down for 3 min".
ntfy runs as a container behind the reverse proxy. The phone app subscribes to a private topic with an access token, and Uptime Kuma's notification points at that topic.

What not to self-host yet
- Outgoing email delivery. Receive your own mail, but rent the sending step. Big mail providers distrust residential addresses.
- Your public website. Ours is a static site on a hosting service. If the box is down, the website is not.
- Payments. Use a payment provider. Holding card data makes you liable for it, so never store card details yourself.
- Anything you cannot restore. One day you will have to.
- Anything clients hit directly. Keep it in the cloud until you have a UPS, a second internet line and a tested restore.
Cost and time
A box of this class idles at about 4 to 6 watts and rarely passes 15 at the wall, without drives: roughly 3 to 11 units a month, or about ₹25 to ₹100 at about ₹6 to ₹9 a unit. Drives take it nearer 20 to 25 watts. These are estimates.

| Item | One-time (approx.) | Monthly (approx.) |
|---|---|---|
| Mini PC, N100/N150 class, 16 GB | ₹15,000 to ₹25,000 (used: ₹8,000 to ₹15,000) | |
| External storage | ₹9,000 to ₹18,000 per drive (approximate, varies by seller) | |
| UPS | ₹3,000 to ₹6,000 (approximate, varies by seller) | |
| Domain name | about ₹70 to ₹125, billed yearly (approximate, varies by seller) | |
| Electricity, box only | about ₹25 to ₹100 | |
| Electricity, box plus drives | about ₹100 to ₹160 | |
| Outgoing mail relay | free tier to a few hundred rupees | |
| Your time | a few weekends to set up | an hour or two a month |
When cloud is the better buy. If you need someone else to answer when a disk fails at 2 a.m., or the time row is worth more than the money rows, pay a provider. Self-hosting wins when you store lots of large files or want your data on your own shelf.
The short version
One quiet box can carry a small business, with restored backups, monitoring that reaches your phone, and updates one at a time.
TDH Systems can set up and look after a small server like this for your business. See what we build.