Tink vs Borg
Borg chunks, encrypts, and prunes archives. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Borg stores the archive. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Borg because content-defined chunks look cheaper than a NAS. Then the host volume fills, nginx dies, and borg list still shows last night’s archive — no chunk match for host fill. A filling /var is a Tink warning; it is not a Borg job unless you scraped borg info 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 Borg if you already run archives. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Borg |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — BORG_REPO, BORG_PASSPHRASE, borg init, borg serve over SSH, then a host that still has no mechanic after the last archive lists as completed |
| What you get | Working monitoring, diagnosis, and approved fixes | Deduped archives, compression, and authenticated encryption. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past borg list |
| Pricing | Free (Scout) / $9 / $29 per machine per month | BSD-3-Clause and free. You still pay the person who owns the VPS after the last archive stays listed |
| Hidden costs | None — fully managed | A quiet borg create at 2am, a locked repo that is not host fill, and a second tool to tell you the box is sick while borg check still reports no errors |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Archives, chunks, and exit codes. Borg does not watch a quiet cert or host auth.log after the last create finished |
| Configuration | None after install — heuristics and AI | BORG_REPO, exclude patterns, compression, borgmatic cron, and which systemd timer actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read borg -v, then SSH into the host to change the Linux box Borg already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | systemctl restart borg and borg break-lock — Borg cannot free host disk, rotate a cert, or stop SSH brute-force unless you wrote that job |
| Alerting | Built-in across 8 channels | Not a Borg job — log lines plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a Borg job — an archive name does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Borg does not read host auth.log, journald, or firewall state after the last archive landed |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if borg dies after the last timer — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — Borg has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — an archive recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed borg create into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | borg list and SSH. No mechanic you text when /var filled and the last archive still showed completed |
| Learning curve | None — works after install | Steep — repositories, borg serve, prune policies, compact, mount, and which failure is Borg vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Borg for backup archives, not a sick-VPS mechanic |
When Borg is the right choice
Keep using Borg when you already want that exact job:
- Deduped archives with a passphrase — you need BORG_REPO, borg create, and prune, not a mechanic.
- An existing backup stack — borg serve over SSH, borgmatic timers, and compact matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — borg init already ran, the repo already ships, and someone owns the Borg box.
- Hosts that only page on archive or lock death — you already run borg check, not a sick-box SSH loop.
The real cost of “just watch borg list stay complete”
Borg runs archives and chunks. A working ops loop for five Linux boxes is not:
- A healthy archive 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 — borg list will stay quiet until the next create process dies
- A single VPS with a dead agent still needs a mechanic, not another archive line
For a 5-server team, Tink Mechanic at $45/month is cheaper than a second person who keeps failed-backup notifications alive, and every scan includes a diagnosis a quiet borg info poll will not type.
No borg init homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs rclone · Tink vs rsync · Tink vs Syncthing