Tink vs bmon
bmon is a portable bandwidth monitor and rate estimator with ncurses graphs. It is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
bmon draws the NIC. Tink answers “why is this VPS sick?”
Accidental sysadmins land on bmon because the graphs are instant and bmon -p eth0 needs no dashboard. Then disk is at 91%, nginx dies, and nobody is watching the TUI — no sentence that says what to run. A filling /var is a Tink warning; it is not a bmon rx/tx graph.
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 bmon if you already want live per-interface rate graphs on an SSH session. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | bmon |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | apt/yum install bmon, then bmon -p eth0 every time the NIC looks busy |
| What you get | Working monitoring, diagnosis, and approved fixes | Ncurses graphs and rate estimates per interface — you still decide what to restart |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open source. You still pay the person who SSH'd in after the uplink filled |
| Hidden costs | None — fully managed | Input module (netlink vs proc), -p policy, graph scale, and no pager unless you wrap it |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Interactive TUI on selected NICs. bmon does not parse auth.log or propose a command |
| Configuration | None after install — heuristics and AI | Interface policy, input/output modules, and whether you left bmon running in tmux |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — you read rx/tx rates and ASCII graphs yourself |
| Fix execution | Proposes and executes approved commands with an audit trail | Monitoring only — bmon cannot stop the flood, restart nginx, or rotate a cert |
| Alerting | Built-in across 8 channels | None by default — bmon is a live TUI; paging is extra |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Live rates only — bmon does not forecast fill time or a quiet NIC going bad later |
| SSH brute-force detection | Built-in — parses auth.log every scan | Not included — bmon 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 SSH into bmon either |
| Public status page | Shareable URL with 90-day history | Not included — bmon has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | Not included — a live graph 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 + a curses graph. No mechanic you text when /var filled |
| Learning curve | None — works after install | Low to launch; higher to map a spike on eth0 back to the process that filled the disk |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Operators already SSH'd in who want live per-interface rate graphs |
When bmon is the right choice
Keep using bmon when you already want that exact job:
- Live per-interface graphs — you are already SSH'd in and need rx/tx rates on this NIC right now.
- Interface-oriented — iftop shows sockets; nethogs groups PIDs; nload is two graphs; bmon is the portable rate estimator.
- 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 bmon”
The package is easy to install. A working ops loop for five Linux boxes is not:
- A healthy graph 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 — bmon stays a bitrate counter until you are looking
- A single VPS with nobody logged in still needs a mechanic, not another curses session
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who opens bmon 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 nload · Tink vs iftop · Tink vs nethogs