Tink vs Calico
Project Calico is a Kubernetes CNI. It also exposes Felix dataplane gauges and policy counters for Prometheus. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
Calico scrapes Felix. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Calico because every Kubernetes networking diagram includes Felix. Then the volume fills, nginx dies, and Grafana still shows endpoints — no PromQL matched host fill. A filling /var is a Tink warning; it is not a Calico job unless the packet path itself is the failure.
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 scraping Calico if you already operate Kubernetes and need CNI SLOs. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Calico |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — operator or manifest install, IP pools, Felix, BIRD/Typha, and prometheus.yml scrape |
| What you get | Working monitoring, diagnosis, and approved fixes | A CNI scrape target. Host disk fill, nginx, Postgres, and certs stay your problem until PromQL fires and you SSH in |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open-source Calico is free. Tigera Calico Cloud/Enterprise is paid. You still pay Prometheus, Grafana, and the engineer who owns NetworkPolicy |
| Hidden costs | None — fully managed | Felix dataplane restarts, Typha fan-out, IP pool exhaustion, a noisy iptables chain, and a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | felix_int_dataplane_failures and policy gauges. Calico does not watch host fill or a quiet cert unless you added another exporter |
| Configuration | None after install — heuristics and AI | IP pools, Felix config, BGP/VXLAN, NetworkPolicy, and which PromQL actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You graph felix_active_local_endpoints in Grafana, then SSH in to change the box |
| Fix execution | Proposes and executes approved commands with an audit trail | Metrics only — Calico cannot free disk, restart nginx, or rotate a cert |
| Alerting | Built-in across 8 channels | Not a Calico job — Prometheus rules and Alertmanager have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a Calico job — a CNI scrape does not forecast a quiet volume filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Calico does not read auth.log, journald, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the agent dies — unless you built an up{job="calico-node"} deadman check |
| Public status page | Shareable URL with 90-day history | None — Calico has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a Felix scrape target is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire Alertmanager into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | calicoctl and Grafana. No mechanic you text when /var filled and Felix still showed endpoints |
| Learning curve | None — works after install | Steep — Felix, BIRD, Typha, IPAM, NetworkPolicy, PromQL, and which dataplane failure actually pages |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need Calico/Felix scrapes, not a sick-VPS mechanic |
When Calico metrics are the right choice
Keep scraping Calico when you already want that exact job:
- Kubernetes CNI SLOs — you need Felix dataplane failures, BGP/VXLAN health, and policy counters, not a mechanic.
- NetworkPolicy at cluster scale — IP pools, Typha, and iptables/eBPF dataplane matter more than host nginx, certs, and SSH on a quiet VPS.
- An existing Prometheus + Grafana stack — calico-node already clusters, Felix already scrapes, and someone owns NetworkPolicy.
- Hosts that only page on Calico — you already run exporters and PromQL, not a sick-box SSH loop.
The real cost of “just scrape Calico”
Calico is in every Kubernetes networking diagram. A working ops loop for five Linux boxes is not:
- A healthy felix_active_local_endpoints still means you SSH in and change the box by hand
- Host fill, nginx, certs, and SSH brute-force never appear unless Prometheus scraped those signals and a rule fired
- A filling /var is a Tink disk warning on every scan — Calico will stay quiet until the packet path itself is the failure
- A single VPS with a dead calico-node still needs a mechanic, not another CNI scrape
For a 5-server team, Tink Mechanic at $45/month is cheaper than Calico plus the engineer who keeps Prometheus scrapes and Felix dataplane rules alive, and every scan includes a diagnosis a quiet Grafana board will not type.
No Felix homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Cilium · Tink vs Prometheus · Tink vs kube-proxy