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