Tink vs Unraid
Unraid is a NAS OS with Docker and KVM. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Unraid runs the array. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Unraid because a homelab NAS looks like ops. Then the guest volume fills, nginx dies, and the array still shows started — no VM matched host fill. A filling /var is a Tink warning; it is not an Unraid job unless you scraped the dashboard and watched it.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep using Unraid if you already run an array. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Unraid |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — USB boot, array, parity, cache pool, then a host that still has no mechanic after the array stays started |
| What you get | Working monitoring, diagnosis, and approved fixes | A NAS OS plus KVM and Docker. Disk fill, nginx, Postgres, and certs stay your problem until you SSH into the guest or the Unraid terminal |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Unraid Starter, Unleashed, or Lifetime. You still pay the person who owns the array after the last VM stays running |
| Hidden costs | None — fully managed | A quiet cache pool at 2am, array disk warnings that are not guest fill, and a second tool to tell you the Linux VM is sick while the dashboard still shows started |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Array, parity, and Docker/VM lifecycle. Unraid does not watch a quiet cert or guest auth.log after the VM started |
| Configuration | None after install — heuristics and AI | Slots, parity, shares, Docker, VMs, and which disk warning actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read the Unraid dashboard, then SSH into the guest to change the Linux box the NAS already sits under |
| Fix execution | Proposes and executes approved commands with an audit trail | Start and stop array, VMs, and containers — Unraid cannot free guest disk, rotate a cert, or stop SSH brute-force unless you wrote that plugin |
| Alerting | Built-in across 8 channels | Not an Unraid job — notifications plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not an Unraid job — a green started VM does not forecast a quiet volume filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Unraid does not read guest auth.log, journald, or firewall state after the VM started |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the guest dies after the last dashboard poll — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — Unraid has no customer-facing status page for the Linux guest |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — an array recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed VMs into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | Web GUI and terminal. No mechanic you text when /var filled and the last VM still showed started |
| Learning curve | None — works after install | Steep — USB key, parity, cache, shares, and which failure is the array vs the running guest |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Homelabs that already run Unraid for NAS and guests, not a sick-VPS mechanic |
When Unraid is the right choice
Keep using Unraid when you already want that exact job:
- A USB-booted NAS with parity and mixed disks — you need an array, shares, and Docker, not a mechanic.
- An existing homelab host — cache pools, Community Apps, and media shares matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — guests already start, the array already ships, and someone owns the USB key.
- Hosts that only page on array or VM death — you already run Unraid notifications and exporters, not a sick-box SSH loop.
The real cost of “just watch the array stay started”
Unraid runs storage and guests. A working ops loop for five Linux boxes is not:
- A started VM still means you SSH into the guest and change the box by hand when it gets sick later
- Host fill, nginx, certs, and SSH brute-force never appear unless a separate tool scraped those signals and a rule fired
- A filling /var is a Tink disk warning on every scan — Unraid will stay quiet until the next VM process dies
- A single VPS with a dead agent still needs a mechanic, not another array line
For a 5-server team, Tink Mechanic at $45/month is cheaper than an Unraid license plus the engineer who keeps failed-VM notifications alive, and every scan includes a diagnosis a quiet dashboard poll will not type.
No NAS homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Proxmox · Tink vs XCP-ng · Tink vs QEMU