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