GUIDE · IB management updated

Picking your IB management software for a CySEC operation (2026)

How CySEC-regulated brokers and prop firms should evaluate IB and affiliate management software in 2026. The audit-trail tool CySEC scrutinizes alongside MiFID II reporting. Four vendor archetypes, five selection axes, CySEC-specific audit considerations, and the RFP questions that pressure-test multi-tier IB scenarios.

Why this guide exists

IB management is the affiliate-side counterpart to broker CRMs (Chapter IV). Where the CRM owns the trader lifecycle - onboarding, KYC, deposit flow, retention - the IB stack owns the introducer relationship: multi-tier rebate structures, sub-IB attribution, clawback workflows, commission reconciliation, and the audit trail CySEC scrutinises during periodic CIF reviews alongside MiFID II transaction reporting.

These are not the same tool. Conflating them is the most common architecture mistake at CySEC startup brokers.

This guide is written for two audiences: CySEC-regulated Cyprus Investment Firms (CIFs) running IB - and affiliate-driven client acquisition, and prop-firm operators managing introducer compensation networks. It draws on the 10-vendor chapter and is complemented by the cross-pillar partner programs aggregator, which takes the commercial-strategy view this chapter deliberately avoids.

The central question this guide answers: given the vendors active in this space in 2026, which archetype fits your operation, and what do you actually test during procurement?


The four vendor archetypes

The IB management market sorts into four distinct archetypes. Operators frequently fail to identify which archetype they are evaluating - causing mismatched RFP criteria and stalled procurement cycles.

1. IB-pure specialist (enterprise)

Dedicated IB-tracking platforms built specifically for FX/CFD broker workflows. Deep multi-tier support, native trade-attribution integrations across MT4, MT5, cTrader, and alt-WL platforms, and enterprise account management with named success contacts.

The canonical example in this category is Cellxpert (Tel Aviv). Confirmed client roster via live research includes Exinity, EightCap, IronFX, Pepperstone, XTB, and Deriv - a tier-1 signal that is comparatively rare in the category. Cellxpert does not publish pricing; procurement is BD-led.

Choose this archetype when scale, reliability, and broker-specific feature depth matter more than pricing transparency or self-serve onboarding. Lowest business-development friction risk for established operators; the vendor has seen your compliance requirements before.

2. IB-pure specialist (mid-market)

Modern IB-tracking platforms with mid-market positioning, often Cyprus-native, and increasingly supporting prop-firm challenge flows alongside traditional FX/CFD IB structures.

Tracknow (Limassol) is the clearest Cyprus-native example. Confirmed features include 10-level MLM attribution and prop-firm challenge flow integration; confirmed clients include EightCap and Focus Markets. Track360 (EU/global) brings an Axcera prop-tech partnership, advertised unlimited tier depth, and a publicly available first-month-free entry point on an otherwise quote-driven model.

Choose this archetype for CySEC startup brokers and growing prop firms. Lighter enterprise overhead than category 1; less proven at institutional scale. Limassol proximity of Tracknow reduces timezone and legal-jurisdiction friction for CySEC compliance discussions.

3. CRM-bundled IB module

The IB tool is one feature within a broader broker-CRM stack rather than a standalone product. The integration benefit is real: trade attribution, CRM events, and IB commission calculations share a data layer without a custom middleware build.

Examples in this category include B2Broker IB (within B2Core; confirmed models: spread, lot, CPA, and markup commissions; unlimited tier trees), Leverate LX IB (18+ years in Limassol; IB module embedded in LXLite / LXCRM stack), Match-Trade IB, and UpTrader IB (Cyprus operations; note that UpTrader’s public IB documentation page returned access errors during research and feature depth could not be independently confirmed - verify directly with the vendor).

Choose this archetype when a single-vendor stack is a priority and the operator is already evaluating or using the same vendor’s CRM. The trade-off is lock-in: replacing the CRM later means re-platforming the IB stack simultaneously.

4. Plugin / overlay

IB capability delivered as a server-side plugin on existing platform infrastructure, without requiring the operator to migrate to a new system.

Brokeree IB is the primary example: a server-side MT4/MT5 plugin with Extended Agent Commissions and confirmed anti-scalping logic. The anti-scalping feature is material for CySEC compliance - it provides a mechanism to identify and clawback rebates on trades generated by scalping strategies that inflate IB compensation without representing genuine client volume.

Choose this archetype when the broker already runs MT4/MT5 and wants IB capability without re-platforming or adding a new vendor relationship. The structural limitation is equally clear: the plugin approach is MT-specific and offers limited functionality beyond the MT ecosystem.

The general-purpose affiliate tracker half-archetype

A fifth category worth naming explicitly rather than ignoring: general-purpose affiliate-tracking platforms not designed for broker workflows. Trackier and Affise are the most commonly cited examples in this position.

Neither has native MT4/MT5 trade attribution or broker-specific IB features - this is a structural gap confirmed in research, not a minor product limitation. Both require custom API work to ingest trade events, meaning the broker absorbs integration engineering cost that the broker-specific specialists include in their product.

The reason operators consider them: Affise publishes pricing ($499/month at entry, graduated tiers to $1,999/month - the rarest confirmed pricing signal in the category), and Trackier offers scale and conversion-tracking depth that some affiliate managers find superior for non-trade attribution. Treat these as the “outside the broker-tech bubble” option, appropriate only when the operator has internal integration capability and a specific reason to prefer general-purpose infrastructure.


The five selection axes

1. Pricing transparency

Quote-only is the category default. Across the ten vendors in the full chapter, only Affise publishes a pricing schedule - confirmed via live research at $499/month (entry), a mid-tier band, and $1,999/month (enterprise). Track360 publicly states a first-month-free model on what is otherwise a quote-driven structure. All other vendors - Cellxpert, Tracknow, B2Broker IB, Leverate LX IB, Match-Trade IB, UpTrader IB, Brokeree IB, and Trackier - require direct BD engagement to obtain pricing.

For operators doing early-stage budgeting, this means IB management is almost always a two-step process: preliminary qualification of features and compliance fit, then BD engagement for commercial terms. Plan for a four- to six-week commercial cycle per shortlisted vendor.

2. Broker-specific integration depth

Native trade attribution from MT4/MT5/cTrader and alt-WL platforms is the key differentiator separating broker-specific vendors from general-purpose trackers. IB-pure specialists (Cellxpert, Tracknow, Track360) and CRM-bundled modules (B2Broker IB, Leverate LX IB, Match-Trade IB, UpTrader IB) all support broker integrations as a core product feature. Brokeree IB is MT4/MT5-only by design.

General-purpose trackers (Trackier, Affise) do not natively ingest trade events. Connecting them to MT4/MT5 trade data requires building a middleware layer that translates platform trade records into the tracker’s event API. That engineering work is real - typically weeks of development, ongoing maintenance, and a dependency risk if either the platform or the tracker API changes. The headline pricing comparison between Affise and a broker-specific specialist becomes less favourable once integration cost is included.

3. CySEC and Cyprus broker fit

Documented Cyprus presence, named CySEC customer references, and audit-trail depth for CySEC compliance reviews are the three proxies for fit in this dimension.

Tracknow is Limassol-native - geographic and regulatory alignment with CySEC is built in. Leverate has 18+ years of Cyprus operations. Match-Trade and UpTrader both have Cyprus entities. Cellxpert’s confirmed roster (Exinity, EightCap, IronFX, Pepperstone) includes multiple CySEC-registered or CySEC-equivalent regulated entities.

For CySEC startup brokers, proximity to Limassol matters operationally: on-site compliance presentations, easy legal jurisdiction for contract disputes, and vendor familiarity with CySEC-specific examination processes.

4. Multi-tier IB structure depth

How deep the IB hierarchy goes, how clawback flows propagate through tiers, and whether sub-IBs can self-onboard via the portal versus requiring operator approval are the three variables that differentiate vendor implementations beyond marketing copy.

Track360 advertises unlimited tier depth. Tracknow’s 10-level MLM structure is confirmed. B2Broker IB supports unlimited trees with spread, lot, CPA, and markup commission types mixed within a single tree - confirmed via research. Brokeree IB’s depth within MT is confirmed but limited by the plugin architecture outside MT.

Most vendors claim “multi-tier IB” - almost none disclose the actual limit in public documentation. Tier depth must be pressure-tested in the RFP phase (see the question framework below). The scenario to test: five tiers deep, mixed commission models at each tier, fraud clawback initiated at tier 3 that must propagate correctly to tiers 4 and 5.

5. Commission model flexibility

Operators need to model IB rebate structures flexibly: revshare (percentage of spread), CPA (per-funded-account event), volume rebate (per-lot), hybrid structures, and tier-dependent variations where tier 1 IBs earn on a different model than tier 3 sub-IBs.

B2Broker IB is the most documented multi-model implementation: spread, lot, CPA, and markup commissions confirmed, mixable within a single IB tree. Cellxpert and Tracknow support revshare, CPA, and hybrid structures based on confirmed client roster characteristics. Per-vendor depth in clawback rules - specifically, the logic governing rebate reversal when a trade is cancelled, disputed, or identified as fraudulent - varies materially and is rarely disclosed without direct vendor engagement.


CySEC and IB compensation audit fit

Audit trail depth as a compliance requirement

CySEC examines IB compensation arrangements during periodic CIF reviews and targeted inspections. The IB management stack must produce auditable, time-stamped records across five operational events: introducer onboarding (including KYB documentation on the IB legal entity), commission calculation per trade, payout reconciliation, clawback events, and dispute resolution. Lightweight tracking systems - and general-purpose affiliate trackers not designed for this workflow - can fail this bar even when their general reporting capabilities are strong.

Enterprise IB-pure specialists such as Cellxpert and depth-positioned CRM modules such as B2Broker IB are more likely to have addressed CySEC-style audit requirements through repeated client examination experience. That experience is not a guarantee - verify audit-log format, retention periods, and export capabilities explicitly during procurement.

Named CySEC customer evidence

The strongest diligence signal for CySEC fit is publicly named CIF operators running the vendor today. Tracknow’s confirmed clients (EightCap, Focus Markets) and Cellxpert’s confirmed roster (Exinity, EightCap, IronFX, Pepperstone, XTB, Deriv) lead this dimension in terms of available public evidence. Other vendors in the chapter have less publicly attributable CySEC client evidence as of this research cycle. That gap does not imply absence of CySEC clients - it reflects what vendors have chosen to disclose publicly.

Anti-abuse and fraud detection

IB networks attract predictable abuse patterns: self-introduction (an IB registering under a fabricated client identity to earn their own CPA), multi-account churning (generating wash trades to inflate volume rebates), and trade-pattern manipulation designed to game lot-based commission structures.

CySEC will ask how the operator detects these patterns and what the clawback mechanism looks like. The IB stack must provide a direct answer. Cellxpert’s enterprise positioning implies fraud-detection capability aligned with tier-1 broker requirements. Brokeree IB’s confirmed anti-scalping logic addresses one specific abuse vector at the MT level. Vendors that do not address fraud detection explicitly in their documentation should be asked the question directly - a vague answer at the RFP stage is a red flag.

MiFID II transaction reporting coordination

MiFID II transaction reporting is a CRM and platform obligation, not an IB obligation. The IB stack does not generate the Article 26 reports. The operational requirement is coordination: trade attribution in the IB system must agree with trade records in the reporting chain so that examinations do not surface reconciliation gaps between what the CRM logged as a trade and what the IB system logged as a commission event. This is an integration architecture question, not a standalone IB-software feature.


Cost-of-ownership reality

Published pricing in this category is exceptional. Affise’s confirmed $499-$1,999/month range is the only transparent pricing signal across the 10 vendors in the chapter. All other vendors are quote-driven, and the commercial terms that emerge from BD engagement are rarely disclosed by clients.

The visible line items in a broker IB management budget typically include: software licensing or SaaS fee, integration engineering (especially significant for non-standard platform combinations or for general-purpose trackers requiring custom MT4/MT5 connectors), custom commission-model development for non-standard rebate structures, IB portal customisation, and multi-language portal support (Cyprus broker IB traffic is typically multilingual - Arabic, Russian, Chinese, and Greek are common demand vectors in addition to English).

The integration-engineering cost differential is the most frequently underestimated item. Broker-specific specialists (Cellxpert, Tracknow, Track360, B2Broker IB) include platform connectivity as a product feature; general-purpose trackers (Trackier, Affise) do not. A broker without internal engineering capacity evaluating Affise at $499/month should cost the MT4/MT5 integration build separately before comparing it to a broker-specific specialist at a higher headline price.

Brokeree IB’s plugin architecture inverts this: the integration cost is low because it runs within existing MT infrastructure, but the cost ceiling is also the feature ceiling. Operators who grow beyond MT need a separate procurement cycle.


Three RFP questions to pressure-test vendor claims

Vendor sales materials for IB management are consistently optimistic about multi-tier depth, commission flexibility, and compliance readiness. The following questions are designed to surface gaps between marketing claims and operational reality. They apply to all four archetypes, with archetype-specific variants noted.

Question 1 - Multi-tier scenario walkthrough

“Walk through a specific multi-tier IB scenario: introducer A signs sub-IB B who signs trader C. Trader C executes one lot at spread Y. Show us where the rebate is calculated for A, where it is calculated for B, where the audit log entry is created, what the timestamp and event fields look like, and what happens operationally if A wants to clawback B’s rebate on the grounds that trader C was B’s own account registered under a false identity. We want to see the actual feature in a demo environment, not a slide deck representation of the feature.”

This question simultaneously tests tier-depth, audit-log structure, and anti-abuse workflows in a single scenario. Vendors who can demo this fluidly have the feature; vendors who defer to written documentation or slide decks are indicating a gap.

Question 2 - CySEC reference clients

“Provide a list of CySEC-licensed CIFs currently running your IB stack. We expect at least three named references willing to take a 30-minute call covering: implementation timeline from contract to go-live, ongoing reliability for commission reconciliation, and how they handled their first CySEC examination of IB compensation records. For general-purpose platforms such as Trackier and Affise, this question becomes: which CySEC-regulated firms have built custom MT4/MT5 integration on top of your platform, and can we speak to their technical lead about that build?”

Vendors without named CySEC references are not automatically disqualified - but the absence is information. For a CySEC CIF operator, reference calls with other CIFs are the highest-quality diligence available.

Question 3 - Anti-abuse posture and clawback mechanics

“Describe your anti-abuse detection capability. Specifically: how does the system detect self-introduction (an IB referring a fabricated client identity), multi-account churning, and trade-pattern manipulation designed to inflate per-lot rebates? What is the typical elapsed time between an anomaly being flagged and a rebate clawback being executed? Are the detection rules configurable by the operator, or are they vendor-defined defaults? Can clawback decisions be recorded with a reason code and timestamp that would satisfy a CySEC examiner reviewing IB compensation records?”

This question separates platforms with genuine anti-abuse infrastructure from those that rely on manual review or post-hoc reconciliation.


How this guide will be updated

The IB management software category evolves alongside broker M&A activity, prop-firm regulatory developments, and CySEC clarifications on IB compensation arrangements. When a material change occurs - a vendor acquisition, a significant product update, a new CySEC guidance note on introducer compensation - substantive corrections are logged at /corrections/ with a dated entry.

The cross-pillar partner programs aggregator takes the commercial-strategy view of IB programme design and is updated on the same cycle. The broker CRMs chapter covers the trader-side counterpart stack and should be read alongside this guide when evaluating integrated versus standalone architectures.

This is the fifth chapter guide in the Phase 1 series, following the CySEC AML walkthrough, the prop-firm tech stack picker, the alt-WL platform picker, and the broker CRM picker. Phase 2 continues with turnkey broker solutions, payments infrastructure, risk management tooling, and liquidity provision - all evaluated against the same CySEC regulatory baseline.