Documentation
Tink is an AI-powered server mechanic. Install it on any Linux server and it continuously monitors, diagnoses, and guides you through fixes from the CLI.
Overview
Tink sits on your server as a lightweight agent. It watches system health (CPU, memory, disk, network, services), detects issues before they become outages, and explains problems in plain English. When something needs fixing, Tink guides you through the repair step by step from your terminal.
Your dashboard at tink.bot/account shows all your machines, their current health, and a history of every scan and fix. Alerts go to Telegram, email, or any channel you configure.
Installation
One command. Works on any Linux server (Ubuntu, Debian, CentOS, RHEL, Amazon Linux, Alpine).
curl -fsSL https://tink.bot/install | shThe installer downloads the Tink agent binary, creates a systemd service, and prompts you for your account token. The agent starts scanning immediately after install.
Tip: Get your account token from tink.bot/account after signing up. The token links your server to your dashboard.
How It Works
Tink monitors CPU, memory, disk, network, and running services. Scans run every few minutes and adapt frequency based on system load.
When something looks wrong, Tink analyzes the symptoms and explains the issue in plain English. No need to parse log files or decode cryptic error codes.
Tink suggests specific commands to fix the issue. You review each command before it runs. Nothing executes without your approval.
Every scan, diagnosis, and fix is logged. Your dashboard shows a complete timeline of what happened and what was done about it.
Dashboard
Your dashboard at tink.bot/account shows:
- All registered machines with real-time health status
- CPU, memory, disk, and uptime for each server
- Recent scans with issues found and fixes applied
- Alert channel configuration (Telegram, email)
- Account settings, billing, and API tokens
CLI Commands
The Tink agent runs as a daemon, but you can interact with it from the command line:
tink statusShow current health summarytink scanRun an immediate scantink fixStart an interactive fix sessiontink logsView recent scan and fix historytink updateUpdate the agent to the latest versiontink uninstallRemove the agent and systemd serviceAlerts & Channels
Tink sends alerts when it detects issues on your servers. Configure alert channels from your dashboard:
- Telegram - instant messages to your phone
- Email - digest or per-incident alerts
- Webhook - POST to any URL for custom integrations
Each alert includes the machine name, issue summary, severity, and a suggested fix. Click through to your dashboard for full details.
Rescue Mode
If a server is in bad shape and the Tink agent can't start normally, use rescue mode:
curl -fsSL https://tink.bot/rescue | shRescue mode runs a one-shot diagnostic without installing anything permanently. It collects system info, identifies critical issues, and prints a prioritized fix plan.
Security
- The agent runs as a non-root user with limited permissions
- All communication is encrypted over HTTPS
- Account tokens are scoped per-machine
- Fix commands require explicit user approval before execution
- No shell access is granted to the Tink service
- System data stays in your account; we don't share or sell it
Plans
- Scout (Free) - 1 machine, hourly scans, basic alerts, 50 AI messages/month
- Mechanic ($9/mo per machine) - Unlimited machines, 5-minute scans, supervised fixes, all alert channels, 500 AI messages/month
- Crew Chief ($29/mo per machine) - Unlimited machines, real-time scans, autonomous remediation, unlimited AI messages, priority support
- Rescue ($29 one-time) - Emergency diagnostic session with full autonomous remediation
FAQ
Any Linux distribution with systemd. Ubuntu, Debian, CentOS, RHEL, Amazon Linux, Fedora, and Alpine are all tested.
No. Tink suggests fixes and waits for your explicit approval. Nothing runs without you confirming it first.
Minimal. The agent idles at under 20MB RAM and near-zero CPU between scans. Scans themselves take a few seconds.
Tink is designed for long-running servers, not ephemeral containers. For Kubernetes, point it at your nodes instead.
System metrics (CPU, memory, disk, network), running services, and relevant log snippets when diagnosing issues. No application data, credentials, or file contents.