Tink vs LXD
LXD is a system-container and VM manager. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
LXD starts the instance. Tink answers “why is this VPS sick?”
Accidental sysadmins land on LXD because system containers look like ops. Then the volume fills, host nginx dies, and the last instance still shows RUNNING — no guest matched host fill. A filling /var is a Tink warning; it is not an LXD job unless you scraped the API 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 LXD if you already run system containers or VMs. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | LXD |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — snap, lxd init, storage pool, bridge, profiles, and a host that still has no mechanic after lxc list looks fine |
| What you get | Working monitoring, diagnosis, and approved fixes | A system-container and VM manager. Disk fill, host nginx, Postgres, and certs stay your problem until you SSH in |
| Pricing | Free (Scout) / $9 / $29 per machine per month | LXD is Apache-2.0. You still pay the engineer who owns the node after the last instance shows RUNNING |
| Hidden costs | None — fully managed | A quiet node at 2am, pool disk fill, and a second tool to tell you the VPS is sick while lxc list still shows RUNNING |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Instance lifecycle. LXD does not watch a quiet cert or host auth.log after the container started |
| Configuration | None after install — heuristics and AI | Daemon, storage pools, networks, profiles, and which instance death actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read lxc list / the REST API, then SSH in to change the host the instance already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | Start and stop instances only — LXD cannot free host disk, rotate a cert, or stop SSH brute-force unless you wrote that runbook |
| Alerting | Built-in across 8 channels | Not an LXD job — the daemon, a custom hook, and a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not an LXD job — a green RUNNING line does not forecast a quiet volume filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — LXD does not read host auth.log, journald, or firewall state after the instance started |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the box dies after the last API poll — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — LXD has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — an instance list recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed instances into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | lxc CLI and REST API. No mechanic you text when /var filled and the last container still showed RUNNING |
| Learning curve | None — works after install | Steep — storage pools, bridges, privileged vs unprivileged, and which host failure is the hypervisor vs the running box |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run LXD instances and need a container/VM manager, not a sick-VPS mechanic |
When LXD is the right choice
Keep using LXD when you already want that exact job:
- System containers and VMs — you need pools, bridges, and instance images, not a mechanic.
- An existing LXD host — REST API, profiles, and isolation matter more than host nginx, certs, and SSH on a quiet VPS.
- An existing homelab or lab fleet — instances already start, the daemon already ships, and someone owns the pool.
- Hosts that only page on failed instances — you already run exporters and PromQL, not a sick-box SSH loop.
The real cost of “just poll lxc list”
LXD manages system containers and VMs. A working ops loop for five Linux boxes is not:
- A RUNNING instance still means you SSH in 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 — LXD will stay quiet until the next instance process dies
- A single VPS with a dead agent still needs a mechanic, not another RUNNING line
For a 5-server team, Tink Mechanic at $45/month is cheaper than an LXD host plus the engineer who keeps failed-instance notifications alive, and every scan includes a diagnosis a quiet API poll will not type.
No instance-manager homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Firecracker · Tink vs Docker · Tink vs Podman