Tink vs iotop
iotop is a Linux I/O TUI — top, but for disk. It is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
iotop ranks the writers. Tink answers “why is this VPS sick?”
Accidental sysadmins land on iotop because htop did not show the disk and sudo iotop -o names the process that is writing. Then /var is at 91%, nginx dies, and nobody is in the TUI — no sentence that says what to run. A filling volume is a Tink warning; it is an iotop IO% line until you SSH.
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 iotop if you already want live I/O ranking on an SSH session. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | iotop |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | apt/yum install iotop, then sudo iotop — kernel taskstats must be on |
| What you get | Working monitoring, diagnosis, and approved fixes | A curses TUI of DISK READ/WRITE, IO%, and COMMAND — you still decide what to kill |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open source. You still pay the person who SSHs in when /var is filling |
| Hidden costs | None — fully managed | Root on every box, delay accounting, and no pager unless you wrap iotop -b in cron |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Interactive I/O ranking. iotop does not parse auth.log or propose a command |
| Configuration | None after install — heuristics and AI | Which columns, -o only-I/O, -a accumulated, batch interval, and which host you are watching |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — you read IO% next to a PID and guess whether it is a backup, a leak, or nginx |
| Fix execution | Proposes and executes approved commands with an audit trail | Monitoring only — iotop cannot free disk, restart nginx, or rotate a cert |
| Alerting | Built-in across 8 channels | None by default — iotop writes to a TTY; paging is extra |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Live I/O only — iotop does not say how many days until the volume fills |
| SSH brute-force detection | Built-in — parses auth.log every scan | Not included — iotop does not read host auth.log or journald |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | If the host is down you cannot sudo iotop either |
| Public status page | Shareable URL with 90-day history | Not included — iotop has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | Not included — a batch log of PIDs is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire something else into PagerDuty |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | SSH + sudo + a curses TUI. No mechanic you text when /var filled |
| Learning curve | None — works after install | Low to launch; higher to map IO% to the job that is filling the disk |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Operators already SSH'd in who need to see which process is saturating this host's disks right now |
When iotop is the right choice
Keep using iotop when you already want that exact job:
- Live I/O ranking — you are already SSH'd in and need DISK READ/WRITE and IO% on this host right now.
- Batch capture —
iotop -b -o -n 3to dump the current writers into a file you will read later. - No extra service — a package on the box, not a hub, SaaS, or Telegram bot.
- No conversation layer wanted — some operators prefer a TUI and will never use a mechanic.
The real cost of “just run iotop”
The package is easy to install. A working ops loop for five Linux boxes is not:
- A healthy TUI still means you SSH into the host and change the box by hand when it gets sick
- Host fill, nginx, certs, and SSH brute-force never appear unless you built extra checks
- A filling /var is a Tink disk warning on every scan — iotop stays an IO% counter until you are looking
- A single VPS with nobody logged in still needs a mechanic, not another sudo session
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who SSHs in to watch iotop after the outage, and every scan includes a diagnosis a quiet TUI will not type.
No SSH homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs nmon · Tink vs htop · Tink vs atop