Tink vs cert-manager
cert-manager is a Kubernetes certificate controller. It watches Certificate objects, then issues and renews TLS secrets. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
cert-manager renews cluster TLS. Tink answers “why is this VPS sick?”
Accidental sysadmins land on cert-manager because every Kubernetes TLS diagram mentions it. Then the volume fills, nginx dies, and Certificate stays Ready — the VPS was never a Secret. A filling /var is a Tink warning; it is not an ACME challenge unless you already run cert-manager on that cluster.
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 cert-manager if you already operate Kubernetes and need cluster TLS issuance. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | cert-manager |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — a cluster, ClusterIssuer, ACME account, DNS-01 or HTTP-01, and still no host mechanic |
| What you get | Working monitoring, diagnosis, and approved fixes | Renewed Kubernetes secrets. The box is still yours to diagnose and SSH |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free (Apache 2.0). You still pay for the cluster, Let's Encrypt rate limits, and the engineer who owns Issuers |
| Hidden costs | None — fully managed | Stuck CertificateRequests, DNS challenge failures, webhook timeouts, and a second tool that pages you when /var fills |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Certificate CRDs and Secret rotation — cert-manager does not watch the OS |
| Configuration | None after install — heuristics and AI | Issuers, ClusterIssuers, Certificate specs, solvers, and which Ingress the controller is allowed to annotate |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — cert-manager logs Ready=False. You still SSH or kubectl describe to learn why a VPS is sick |
| Fix execution | Proposes and executes approved commands with an audit trail | Issue only — cert-manager cannot free disk, restart host nginx, or rotate a cert on a VPS that is not a Secret |
| Alerting | Built-in across 8 channels | None — scrape controller metrics or watch Certificate Ready before anyone is paged about the host |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Renewal only — cert-manager reissues before NotAfter. It does not forecast host fill |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — cert-manager does not read auth.log, journald SSH, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | A silent Certificate is a missing controller — only if the API server still answers |
| Public status page | Shareable URL with 90-day history | None — cert-manager has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a Certificate renewal is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire controller metrics into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | kubectl get certificate. No mechanic you text when /var filled on a VPS that is not a Secret |
| Learning curve | None — works after install | Steep — Kubernetes, ACME solvers, DNS-01, webhook, and which Ready=False actually means the box is sick |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need cluster TLS issuance, not a sick-VPS mechanic |
When cert-manager is the right choice
Keep cert-manager when you already want that exact job:
- Cluster TLS issuance — cert-manager is how Kubernetes renews a Secret before NotAfter. You need it to feed Ingress, not to watch a quiet VPS.
- An existing cluster — ClusterIssuers, ACME solvers, and Certificate objects already exist, and someone owns DNS-01.
- Secret rotation questions — Ready=True and solver failures matter more than host nginx, disk, and SSH.
- Hosts that only exist as Nodes — you already run Kubernetes, not a sick-box SSH loop.
The real cost of “just run cert-manager”
cert-manager is in every Kubernetes TLS diagram. A working ops loop for five Linux boxes is not:
- A Certificate renewal still means you SSH in and change the box by hand
- Host fill, nginx, and SSH brute-force never appear unless they show up as a stuck challenge you already scrape
- A filling /var is a Tink disk warning on every scan — cert-manager will stay Ready until the Secret is the thing that expired
- A single VPS with no cluster still needs a mechanic, not a Certificate controller
For a 5-server team, Tink Mechanic at $45/month is cheaper than cert-manager plus the engineer who keeps ClusterIssuers and ACME solvers alive, and every scan includes a diagnosis a quiet Certificate Ready will not type.
No ACME-solver homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs etcd · Tink vs Horizontal Pod Autoscaler · Tink vs Prometheus