Tink vs host
host is a BIND DNS lookup CLI — pick a name, print has address. It is not a mechanic. Tink installs in one command, watches the Linux box, explains what is wrong, and helps you fix it.
host dumps has address. Tink answers “why is this VPS sick?”
Accidental sysadmins land on host because host example.com shows A/AAAA/MX without a dashboard. Then disk is at 91%, nginx dies, and last night's address line does not say what to run. A filling /var is a Tink warning; it is not a BIND query.
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 host if you already want a lookup against a resolver. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | host |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Install bind-utils / dnsutils, then run host against a name every time DNS looks wrong |
| What you get | Working monitoring, diagnosis, and approved fixes | A one-shot lookup: has address, mail is handled by, IPv6 — only while you are watching |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open source. You still pay the person who SSHs in after the outage |
| Hidden costs | None — fully managed | Which nameserver, -t type, -a vs one record, and whether anyone was watching when NXDOMAIN hit |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Active DNS query. host does not parse auth.log or propose a command |
| Configuration | None after install — heuristics and AI | Name, type, server, -v, and whether /etc/resolv.conf is even the resolver the app uses |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — you read has address yourself |
| Fix execution | Proposes and executes approved commands with an audit trail | Monitoring only — host cannot restart nginx, free disk, or rotate a cert |
| Alerting | Built-in across 8 channels | None by default — host is a snapshot; paging is extra |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Live lookup only — host does not forecast fill time or a quiet disk going bad later |
| SSH brute-force detection | Built-in — parses auth.log every scan | Not included — host does not read auth.log or journald |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | If the box is down you cannot SSH into host either |
| Public status page | Shareable URL with 90-day history | Not included — host has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | Not included — a has-address line 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 + host. No mechanic you text when /var filled |
| Learning curve | None — works after install | Low to launch; higher to map SERVFAIL to the disk that filled |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Operators who already want a BIND dump and will still SSH in when the box is sick |
When host is the right choice
Keep using host when you already want that exact job:
- Lookup inventory — you need A/AAAA/MX records, not a fleet digest.
- Name-oriented — you control the query and the resolver; neither end is a mechanic.
- No extra service — a binary you run toward a name, not a hub, SaaS, or Telegram bot.
- No conversation layer wanted — some operators prefer a CLI and will never use a mechanic.
The real cost of “just run host”
The lookup is cheap to install. A working ops loop for five Linux boxes is not:
- A complete has-address line still means you SSH into the box and change it by hand when it gets sick
- Disk 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 — host stays a live snapshot until you are looking
- A single VPS with nobody logged in still needs a mechanic, not another address line
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who opens host after the outage, and every scan includes a diagnosis a quiet BIND lookup will not type.
No SSH homework. No silent box. One command install.
Start MechanicAlso compare: Tink vs ping · Tink vs mtr · Tink vs iperf3