Trackifly splits tracking into Hub (dashboard + API) and Edge (domains). Attach any number of domains — across multiple clients or campaigns — to Hub, deploy Edge nodes on any VPS, and stream events back to Hub in real time.
Cloud or self-hosted · No vendor lock-in · ClickHouse-ready
curl -fsSL https://trackifly.com/install.sh | bashEverything you need for accurate attribution — deploy on our cloud or your own servers, without the spreadsheet of configs.
Keep routing rules close to the domain and collect clicks/conversions with an event trail that is easy to reason about.
Serve static landers from the Edge server, run basic IP/UA checks, and forward orders to your external API without exposing it directly.
Start simple (dev/MVP), export CSV anytime, and move to ClickHouse when you need high-volume analytics.
Attach domains from multiple clients or campaigns to one Hub. JWT-protected admin API, store-managed Edge keys (shown once), domain scoping, and optional node binding per Edge node.
Built for real-world setups where domains are not on the same machine as your dashboard.
You want one place to manage campaigns and see results, while keeping traffic routing close to the domain server.
Clients run Edge on their own VPS. To add a domain: just point its DNS A record to the Edge IP. Campaign config and reporting stay in your Hub — clients only manage DNS.
Segment access per client and per domain. Reduce "shared key" risk with scoped Edge keys and optional node binding.
A simple split that maps to how traffic is actually hosted: Hub for control, Edge for domains.
Manage unlimited domains and campaigns from one place — across any number of clients. Hub stores configs, serves snapshots to Edge nodes, and collects all click/conversion events.
One Edge node handles all domains pointed at its VPS — from any number of clients or campaigns. To add a domain: client points DNS A record to the Edge IP. Edge picks it up automatically, no restart needed.
Start lightweight for dev/MVP. Add Redis for shared state, and ClickHouse when reporting volume grows.
A predictable flow: configure once in Hub, run Edge near domains, review results in Hub.
Start Hub for the dashboard, admin API, snapshots, and collector endpoints.
Create a campaign, add a domain in Hub, choose its action (local lander or redirect). Then point the domain's DNS A record to the Edge VPS IP — done.
Generate scoped keys and, if needed, bind them to a specific Edge node_id for safer client hosting.
Deploy Edge on the domain server. It polls snapshots, serves the domain, and reports events back to Hub.
No free tier. Start a 7-day Trial to validate your domain routing and event flow.
Quick setup and hosting answers.
Open /app/ (or use Open dashboard in the header). Hub hosts the dashboard and admin API.
Yes. Client runs Edge on their VPS, points their domain DNS A record to that IP — Edge picks it up automatically. Campaign config and event reporting stay in your Hub. Multiple domains per node, no restarts needed.
No for dev/MVP. When you need production-scale analytics and reporting volume, ClickHouse is the recommended backend.
Open /api/healthz - it should return ok.
Place them under content/<campaign>/site/index.html (example: content/cmp_1/site/index.html). Edge can serve them directly on the domain.
Still have questions? Contact us →
Deploy Hub + Edge in minutes. No SaaS lock-in, no per-event fees, no surprise bills.