Tink vs Timeshift
Timeshift copies rsync or btrfs snapshots, schedules, and restore points. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
Timeshift takes the snapshot. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Timeshift because a system restore snapshot looks cheaper than an outage. Then the host volume fills, nginx dies, and timeshift --list still looks Success — no snapshot match for host fill. A filling /var is a Tink warning; it is not a Timeshift job unless you scraped cron 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 Timeshift if you already run system restore snapshots. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Timeshift |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — timeshift.json, rsync vs btrfs mode, /timeshift disk, then a host that still has no mechanic after the last timeshift --create exits 0 |
| What you get | Working monitoring, diagnosis, and approved fixes | System restore snapshots, schedules, and a GTK window. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past timeshift --list |
| Pricing | Free (Scout) / $9 / $29 per machine per month | GPL and free. You still pay the person who owns the VPS after the last snapshot stays listed |
| Hidden costs | None — fully managed | A quiet cron at 2am, a full /timeshift that is not host fill, and a second tool to tell you the box is sick while timeshift --list still looks Success |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Snapshots, retain counts, and rsync or btrfs. Timeshift does not watch a quiet cert or host auth.log after the last snapshot landed |
| Configuration | None after install — heuristics and AI | timeshift.json, snapshot device, filters, schedule, and which cron actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read timeshift --list, then SSH into the host to change the Linux box Timeshift already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | Retry timeshift --create — Timeshift cannot free host disk, rotate a cert, or stop SSH brute-force unless you restore the whole tree |
| Alerting | Built-in across 8 channels | Not a Timeshift job — cron mail plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a Timeshift job — a snapshot comment does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Timeshift 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 the guest dies after the last Success cron — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — Timeshift 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 timeshift --create into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | timeshift-gtk and SSH. No mechanic you text when /var filled and the last snapshot still showed created |
| Learning curve | None — works after install | Steep — rsync vs btrfs, timeshift.json, snapshot device, filters, and which failure is Timeshift vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Timeshift for system restore, not a sick-VPS mechanic |
When Timeshift is the right choice
Keep using Timeshift when you already want that exact job:
- System restore snapshots — you need timeshift.json, rsync or btrfs mode, and timeshift --restore, not a mechanic.
- An existing snapshot schedule — boot/hourly/daily retain counts and /timeshift matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — Timeshift already runs, the snapshot device already ships, and someone owns the restore disk.
- Hosts that only page on snapshot cron death — you already run Timeshift mail, not a sick-box SSH loop.
The real cost of “just watch timeshift --list”
Timeshift takes snapshots and restore points. 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 — Timeshift will stay quiet until the next cron fails
- A single VPS with a dead agent still needs a mechanic, not another snapshot comment
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-cron notifications alive after a Timeshift install, and every scan includes a diagnosis a quiet timeshift --list Success will not type.
No timeshift.json homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs restic · Tink vs Borg · Tink vs Kopia