Tink vs borgmatic
borgmatic wraps Borg behind YAML and a systemd timer. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
borgmatic runs the archive. Tink answers “why is this VPS sick?”
Accidental sysadmins land on borgmatic because a YAML wrapper looks cheaper than a NAS. Then the host volume fills, nginx dies, and borgmatic list still looks complete — no archive match for host fill. A filling /var is a Tink warning; it is not a borgmatic job unless you scraped on_error hooks and watched them.
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 borgmatic if you already run Borg. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | borgmatic |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — borgmatic.yaml, source_directories, repositories, encryption_passphrase, then a host that still has no mechanic after the last borgmatic create reports finished |
| What you get | Working monitoring, diagnosis, and approved fixes | A Borg wrapper and a timer. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past borgmatic list |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free software. You still pay the person who owns the VPS after the last borgmatic.timer stays green |
| Hidden costs | None — fully managed | A quiet overnight create, a healthy YAML that is not host fill, and a second tool to tell you the box is sick while borgmatic list still looks complete |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | borgmatic.yaml, systemd timer, and Borg repos. borgmatic does not watch a quiet cert or host auth.log after the last archive finished |
| Configuration | None after install — heuristics and AI | borgmatic.yaml, source_directories, repositories, keep_daily, hooks, and which failed borgmatic create actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read borgmatic list and journalctl -u borgmatic, then SSH into the host to change the Linux box borgmatic already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | borgmatic create, prune, compact, check — borgmatic cannot free host disk, rotate a cert, or stop SSH brute-force unless you archived that path |
| Alerting | Built-in across 8 channels | Not a borgmatic job — on_error hooks and Healthchecks.io plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a borgmatic job — an archive date does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — borgmatic 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 the borgmatic.timer dies after the last run — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — borgmatic has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a borgmatic list recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed borgmatic.service into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | borgmatic list and SSH. No mechanic you text when /var filled and the last create still showed finished |
| Learning curve | None — works after install | Steep — YAML, passphrases, prune keep_daily, consistency checks, and which failure is Borg vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run borgmatic for Borg orchestration, not a sick-VPS mechanic |
When borgmatic is the right choice
Keep using borgmatic when you already want that exact job:
- Borg orchestration — you need borgmatic.yaml, source_directories, and a timer, not a mechanic.
- An existing backup stack — borgmatic create, prune, compact, and check matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — borgmatic already runs, the passphrase already exists, and someone owns the Borg repo.
- Hosts that only page on archive or timer death — you already run on_error hooks and Healthchecks.io, not a sick-box SSH loop.
The real cost of “just watch borgmatic list”
borgmatic runs Borg and a timer. 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 — borgmatic will stay quiet until the next create fails
- A single VPS with a dead agent still needs a mechanic, not another archive date
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-timer notifications alive after a green borgmatic.timer, and every scan includes a diagnosis a quiet borgmatic list will not type.
No borgmatic.yaml homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Borg · Tink vs restic · Tink vs Kopia