Tink vs rsync
rsync copies trees, filters, and modules. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
rsync runs the copy. Tink answers “why is this VPS sick?”
Accidental sysadmins land on rsync because a cron + rsync -avz looks cheaper than a backup appliance. Then the host volume fills, nginx dies, and the last job still exits 0 — no path match for host fill. A filling /var is a Tink warning; it is not an rsync job unless you scraped the log 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 rsync if you already run copies. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | rsync |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — rsyncd.conf modules, SSH keys, --exclude lists, a 2am cron, then a host that still has no mechanic after the last transfer exits 0 |
| What you get | Working monitoring, diagnosis, and approved fixes | File copy, delta transfer, and rsync:// modules. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past sent X bytes received Y bytes |
| Pricing | Free (Scout) / $9 / $29 per machine per month | GPL and free. You still pay the person who owns the VPS after the last total size line looks healthy |
| Hidden costs | None — fully managed | A quiet rsync cron at 2am, a full destination that is not host fill, and a second tool to tell you the box is sick while rsync still reports 0 errors |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Bytes transferred and exit codes. rsync does not watch a quiet cert or host auth.log after the last copy finished |
| Configuration | None after install — heuristics and AI | rsyncd.conf, cron, --delete, bandwidth limits, SSH wrappers, and which MAILTO actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read the cron mail, then SSH into the host to change the Linux box rsync already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | systemctl restart rsync and rsync --dry-run — rsync cannot free host disk, rotate a cert, or stop SSH brute-force unless you wrote that job |
| Alerting | Built-in across 8 channels | Not an rsync job — cron MAILTO plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not an rsync job — a sent X bytes line does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — rsync does not read host auth.log, journald, or firewall state after the last tree synced |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if rsync dies after the last cron — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — rsync has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a transfer recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed rsync into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | cron mail and SSH. No mechanic you text when /var filled and the last job still showed total size is |
| Learning curve | None — works after install | Steep — filters, --delete, rsyncd modules, SSH transport, and which failure is rsync vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run rsync for copies and backups, not a sick-VPS mechanic |
When rsync is the right choice
Keep using rsync when you already want that exact job:
- Delta copies over SSH or rsync:// — you need rsyncd.conf, --delete, and a cron, not a mechanic.
- An existing backup or mirror stack — exclude lists, bandwidth limits, and MAILTO matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — rsync already starts, the destination already ships, and someone owns the rsync box.
- Hosts that only page on copy or daemon death — you already run cron mail, not a sick-box SSH loop.
The real cost of “just watch the last job exit 0”
rsync runs copies and modules. A working ops loop for five Linux boxes is not:
- A healthy exit code 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 — the cron mail will stay quiet until the next rsync process dies
- A single VPS with a dead agent still needs a mechanic, not another sent X bytes line
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-app notifications alive after a free rsync install, and every scan includes a diagnosis a quiet cron mail will not type.
No rsyncd.conf homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Syncthing · Tink vs MinIO · Tink vs Seafile