Why your tracker should live on your own server
inotrack installs on your VPS: a Go core, events in ClickHouse, settings in Postgres. Only you hold the server keys, and the license never stops your traffic, even if we are down.
curl -fsSL https://get.inotrack.run/install.sh | bash
Your data never leaves your server
Clicks, conversions, offers and finances are stored in your own database. The license server sees only service telemetry: event volumes, version, module status. No offer details and no financial figures.
Internet down? Traffic keeps flowing
If the key expires or the connection to the license server is lost, you get 72 hours of offline grace with full functionality, then graceful degradation: paid modules switch off, but the tracker keeps accepting clicks. Your data is never deleted.
Updates and backups with one command
tracker-ctl update pulls the new version from a private registry, runs migrations and rolls back on its own if the health check fails. tracker-ctl backup puts Postgres, ClickHouse partitions and uploaded landing pages into one archive.
One server or a network of nodes
You can start with a single VPS. When traffic starts coming in from several regions, add edge nodes: they accept clicks close to your audience and replicate events to the central instance.
Questions
What can you see of my data?
Only service telemetry: the volume of clicks and conversions, the version, module status, errors. Offers, domains, creatives and money never go to the license server.
What happens if the license server is unreachable?
For 72 hours the tracker runs with full functionality. After that, paid modules switch off, but the tracker keeps accepting clicks and postbacks and no data is lost.
Do I need a separate server?
Yes: a dedicated VPS isolates projects from each other. An inexpensive one will do: the core handles 10,000+ clicks/s on 1 vCPU (benchmark at 100 concurrent requests).
How long does the install take?
One command on a clean VPS: the installer checks the OS, resources and DNS, brings up docker compose with Caddy and auto-TLS, runs migrations and creates the first admin. Usually 10–15 minutes.
Run inotrack on your own server
One command on a clean VPS, 10–15 minutes. Get your key right after you pay on the site, or a free one for 7 days.
Questions? Message us on Telegram: @SmokeJung.