Tink vs ReaR
ReaR (Relax-and-Recover) writes a rescue ISO and a backup archive. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
ReaR builds the ISO. Tink answers “why is this VPS sick?”
Accidental sysadmins land on ReaR because a bootable rescue image looks like insurance. Then the host volume fills, nginx dies, and the last rear mkbackup still looks complete — no OUTPUT match for host fill. A filling /var is a Tink warning; it is not a ReaR job unless you scraped cron mail 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 ReaR if you already run bare-metal recovery. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | ReaR |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — /etc/rear/local.conf, OUTPUT=ISO, BACKUP=NETFS, BACKUP_URL, then a host that still has no mechanic after the last rear mkbackup exits 0 |
| What you get | Working monitoring, diagnosis, and approved fixes | A bootable rescue ISO and a backup archive. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past rear dump |
| Pricing | Free (Scout) / $9 / $29 per machine per month | GPL and free. You still pay the person who owns the VPS after the last rear mkbackup stays green |
| Hidden costs | None — fully managed | A quiet cron, a healthy ISO that is not host fill, and a second tool to tell you the box is sick while rear mkbackup still looks complete |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | local.conf, rescue media, and NETFS archives. ReaR does not watch a quiet cert or host auth.log after the last ISO landed |
| Configuration | None after install — heuristics and AI | OUTPUT, BACKUP, BACKUP_URL, exclude paths, and which failed rear mkbackup actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read rear dump and the backup log, then SSH into the host to change the Linux box ReaR already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | rear mkbackup and rear recover — ReaR cannot free host disk, rotate a cert, or stop SSH brute-force unless you restore the whole tree |
| Alerting | Built-in across 8 channels | Not a ReaR job — cron mail from a failed mkbackup plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a ReaR job — an ISO date does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — ReaR does not read host auth.log, journald, or firewall state after the last rescue image landed |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the host dies after the last rear mkbackup — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — ReaR has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a rescue-ISO recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed rear mkbackup into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | rear dump and SSH. No mechanic you text when /var filled and the last ISO still showed finished |
| Learning curve | None — works after install | Steep — local.conf, OUTPUT vs BACKUP, NETFS URLs, boot media, and which failure is ReaR vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run ReaR for bare-metal recovery, not a sick-VPS mechanic |
When ReaR is the right choice
Keep using ReaR when you already want that exact job:
- Bare-metal disaster recovery — you need OUTPUT=ISO, rear mkrescue, and rear recover, not a mechanic.
- An existing backup stack — rear mkbackup, NETFS URLs, and restore from a rescue image matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — ReaR already runs, local.conf already exists, and someone owns the backup disk.
- Hosts that only page on ISO or cron death — you already run failed-mkbackup cron mail, not a sick-box SSH loop.
The real cost of “just watch the ReaR log”
ReaR writes a rescue ISO and an archive. A working ops loop for five Linux boxes is not:
- A healthy ISO still means you SSH into the host 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 — ReaR will stay quiet until the next rear mkbackup fails
- A single VPS with a dead agent still needs a mechanic, not another rescue image
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-cron notifications alive after a green rear mkbackup, and every scan includes a diagnosis a quiet ISO list will not type.
No ReaR local.conf homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Timeshift · Tink vs Bacula · Tink vs luckyBackup