Tink vs Snapper
Snapper takes timeline and pre/post btrfs snapshots. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Snapper runs the snapshot. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Snapper because openSUSE and SLES ship it next to zypper. Then the host volume fills, nginx dies, and the last snapper list still looks complete — no config match for host fill. A filling /var is a Tink warning; it is not a Snapper job unless you scraped snapperd and watched COW space.
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 Snapper if you already run btrfs snapshots. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Snapper |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — btrfs subvolumes, /etc/snapper/configs/root, timeline cleanup, then a host that still has no mechanic after the last snapper list looks complete |
| What you get | Working monitoring, diagnosis, and approved fixes | A snapshot list and a rollback. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past the last snapper create |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free software. You still pay the person who owns the VPS after the last snapper timeline stays green |
| Hidden costs | None — fully managed | A quiet timeline snapshot that is not host fill — and the COW space from snapper create can be the fill — plus a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Snapper configs, snapper list, and snapperd. Snapper does not watch a quiet cert or host auth.log after the last snapshot number landed |
| Configuration | None after install — heuristics and AI | Configs, NUMBER_LIMIT, TIMELINE_CREATE, pre/post zypper hooks, and which failed snapper create actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read snapper list and btrfs filesystem df, then SSH into the host to change the Linux box Snapper already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | snapper create and snapper rollback — Snapper cannot free host disk, rotate a cert, or stop SSH brute-force unless that path lived in a snapshot |
| Alerting | Built-in across 8 channels | Not a Snapper job — a failed snapperd unit plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a Snapper job — a snapshot number does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Snapper does not read host auth.log, journald, or firewall state after the last snapshot landed |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if snapperd dies after the last timeline — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — Snapper has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a snapshot recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed snapperd journal mail into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | snapper list and SSH. No mechanic you text when /var filled and the last snapshot still showed 0 |
| Learning curve | None — works after install | Steep — btrfs subvolumes, config files, timeline vs number cleanup, YaST Snapper, and which failure is COW space vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Snapper for btrfs snapshots, not a sick-VPS mechanic |
When Snapper is the right choice
Keep using Snapper when you already want that exact job:
- btrfs snapshots from a config — you need snapper create, snapper list, and snapper rollback, not a mechanic.
- An existing SUSE stack — /etc/snapper/configs/root, zypper pre/post snapshots, and YaST Snapper matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — Snapper already runs, the config already exists, and someone owns the COW space.
- Hosts that only page on snapshot or snapperd death — you already run failed-unit journal mail, not a sick-box SSH loop.
The real cost of “just watch snapper list”
Snapper runs btrfs snapshots and a config. A working ops loop for five Linux boxes is not:
- A healthy snapshot 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 — Snapper will stay quiet until COW space or the next create fails
- A single VPS with a dead agent still needs a mechanic, not another snapshot number
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-snapperd notifications alive after a green snapper list, and every scan includes a diagnosis a quiet snapshot number will not type.
No Snapper config homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Timeshift · Tink vs luckyBackup · Tink vs restic