Your traffic. Your server. No middlemen.
inotrack is a tracker for affiliate teams that are tired of paying for someone else's cloud and waiting for it to come back up. Clicks, postbacks, caps, splits and money all run on your VPS. The Go core and ClickHouse handle your whole team's load on one inexpensive machine, and ask nobody's permission.
curl -fsSL https://get.inotrack.run/install.sh | bashone line and you're free
Everything from click to cash. No duct tape
No modules on separate subscriptions and no exporting to Excel. Click tracking, routing across offers, postbacks and reporting all run on the same data, in one place.
Traffic tracking and routing
Where a click goes: flows, rules, smartlink, landing pages, bot protection, domains and edge nodes.
- Flows, caps and splits
- Auto-rules and stop-loss
- Duplication and bulk actions
- Smartlink
- Landing pages and funnels
- Bot and fraud filter
- Tracker domains
- Edge nodes
Conversions and affiliate networks
Network postbacks, sending conversions to ad accounts, an offer catalog from networks and app attribution.
- Postbacks and conversions
- S2S conversions to ad accounts
- Affiliate networks
- App attribution
Analytics and control
Reports down to the creative, cohorts, alerts and summaries, exports to spreadsheets and storage.
- Reports and analytics
- Alerts, Telegram and daily summary
- Exports: Sheets, S3, CSV
Money
Costs from ad accounts and hosting providers, P&L, reconciliation with networks and payouts.
- Cost import
- Finance module
SEO networks and push
Rankings and money for the sites in your network; site and app subscribers as a traffic source.
- SEO network
- Push
Team, API and operations
Roles and audit log, API and MCP, the mobile app, updates and backups for your own server, migration from another tracker.
- Team and access
- API, MCP and webhooks
- Mobile app
- Updates and backups
What inotrack looks like in action
Real tracker screens with demo data: dashboard, flows, bot filter, postbacks, reports and money.
Click → redirect → postback → report
A click never touches Postgres: flows live in Redis and events are written asynchronously in batches. No matter how many offers and rules you have, the redirect doesn't slow down.
Click
A visitor follows the flow link /go/{flow}. The core resolves the flow from the Redis cache and checks caps and access-control rules.
Redirect
The offer is picked by weight, EPC and caps, a clickid is generated, macros are filled into the URL, and the visitor gets a 302 to the offer. The click goes into a buffer and is written to ClickHouse in batches.
Postback
The network sends the conversion to /pb/{token}. It is matched by clickid and deduplicated by (network, clickid, goal), and the status moves along reg → lead → approve → ftd with no duplicates.
Report
Clicks and conversions show up in reports in real time: CR, EPC, ROI and profit, sliced any way you like: source, offer, sub1–10, geo. If a rule fires, you get a Telegram alert.
Numbers from a benchmark, not a slide deck
A click never hits Postgres and never waits on a write: it goes into a lock-free in-memory buffer, then to ClickHouse in batches, with a WAL on disk if storage lags. Every release is run through wrk/vegeta and pprof. If it fails, it doesn't ship.
10,000+ req/s
on 1 vCPU, the critical /go path
6 ms
redirect p99 at 100 concurrent requests
20 ms
postback processing p95, including the DB write
1–2 s
ClickHouse batch write interval
Go
click and postback handling, one binary with edge and central roles
ClickHouse
clicks, conversions, costs — billions of rows, ad-hoc SQL
Postgres
entities: offers, flows, finance, users
Redis
hot reload of flow configs, cap counters, postback dedup
Your server. Your data. Period.
It installs on your VPS with one command: Ubuntu/Debian, docker compose, Caddy with auto-TLS. There is no cloud between your traffic and your money. The license checks the key and touches nothing else.
Your data never leaves your server
Clicks, conversions, offers and finances live 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 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.
You pay for the license. Everything else is yours
The key unlocks modules according to your plan, and that is all it does: the tracker and the data live on your server. Switch plans without reinstalling anything.
Growth
A network of sites and your first paid funnels — for when one domain is no longer enough
Get a licenseBusiness
Running paid traffic, automation and money — the workhorse plan
Get a licenseEnterprise
A network of teams, several geos, your own infrastructure and SLA requirements
Get a licenseUnlimited clicks on every plan. Compare plans →
Questions
How is this better than Keitaro or Binom?
It isn't better at everything; it's just built differently. inotrack runs entirely on your server, with a Go core and events in ClickHouse, so the tracker doesn't buckle as traffic grows. On top of that you get a bot filter, a finance module with reconciliation and shaving detection, and an MCP server for managing it from Claude Code. Point-by-point comparisons, with sources, are at inotrack.run/en/compare.
Does it take long to install?
One command: curl -fsSL https://get.inotrack.run/install.sh | bash. The installer checks the OS, resources and DNS, brings up docker compose with Caddy and auto-TLS, runs migrations and creates the first admin. On a clean VPS it takes 10–15 minutes. Your coffee won't even get cold.
Where do I get a key?
Pick a plan at inotrack.run/en/pricing and pay in USDT (TRC20). The key shows up on the order page as soon as the payment is confirmed, and a copy goes to your email. Want to try it first? You get 7 days free at inotrack.run/en/trial. The installer asks for the key at the setup step. Questions? Message us on Telegram: @SmokeJung.
What if your license server goes down?
No problem: you get 72 hours of offline grace with full functionality, and clicks and postbacks flow as usual. After that comes graceful degradation: paid modules switch off, but traffic doesn't stop and your data doesn't disappear.
Can I bring over my old stats from Keitaro or Binom?
Stats, no. Campaigns, yes: the API key import brings over networks, offers, sources, landing page URLs and flows with weights and filters, all of them paused. Details at inotrack.run/en/migration.
Which networks work out of the box?
There are ready-made presets for Unicom24, Pampadu, Leadgid, Guruleads, Leads.su, PIN-UP, 3snet, Vavada, RevenueLab, Zeydoo, RakeCore (Rollix), plus incoming AppMetrica postbacks. The full list of integrations is at inotrack.run/integrations (in Russian). Network not on the list? Set up the parameter mapping yourself, without writing a line of code.
Do I need a separate server?
Yes, and it's not about greed. A separate VPS means an outage or a ban on one project doesn't touch traffic on the others. An inexpensive one will do: the core handles 10,000+ clicks/s on 1 vCPU.
What can you see of my data?
Only service telemetry: the volume of clicks and conversions, version, module status, errors. Offers, domains, creatives and money never go to the license server. Never.
Can I really run the tracker from Claude Code?
You can. The MCP server, built on the public API, can read (stats, offers, anomalies) and manage (pause and start offers, adjust split weights). Every write requires confirmation and lands in the audit log.
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.