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