Broker CRM  /  Back office  /  IB management

One platform.Three connected experiences.

Run client operations, partner programmes and broker-branded retention from a governed platform built around your workflows.

Built for modern CFD and multi-asset brokers

MetaTrader 5 Manager APITenant-pinned adapter for client, account, group and deal data.
Per-broker deploymentSeparate database, hostnames and brand pack for each broker.
Broker-defined KYCDocument policy, routes and evidence without a mandatory third-party vendor.
Append-only governanceStrong-proof actions, four-eyes approvals and retained evidence.

Three connected experiences

Built for three audiences. Governed as one system.

Broker teams, partners and traders each get a workspace designed for their job, while identity, policy, workflow and evidence stay connected underneath.

Broker Back Office

Everything your operations team needs to run the client lifecycle.

Leads, clients, KYC, partners, payments servicing, support and approvals in role-relevant workspaces — with the evidence trail attached to every action.

Client 360Lead assignmentKYC reviewPayments queuesApprovalsRole catalogues
Explore Broker CRM
nexus.demo-broker.com/back-office/clients/CL-40912
M. Karlsen
Clients / Client 360
AN
Lifetime deposits
$41,200
Net funding
$17,260
▲ 30d
Open tickets
1
SLA 4h left
Client profile
  • Client IDCL-40912
  • Registered14 Mar 2026
  • JurisdictionPortugal
  • AttributionNorthline IB · campaign NL-07
  • OwnerA. Novak · Desk 2
  • Risk classificationStandard
KYC documents
Policy v4
  • Proof of identityVerified
  • Proof of addressVerified
  • Source of fundsManual review
  • DeclarationNot required
Trading accounts
Read-only from MT5
AccountTypeGroupBalance
8840112Live · Standardreal\NL\std$12,400
8840119Live · Proreal\NL\pro$4,860
9920045Demodemo\NL\std$50,000
Relationship timeline
  • Deposit $2,500 · settled3d
  • Note added by A. Novak — callback booked5d
  • KYC source of funds requested6d
  • Account opened Live · Pro9d
  • Attributed to Northline IB21d

IB Portal

A partner workspace that explains its own numbers.

Campaigns, attribution, network hierarchy, commission records, payouts and support — so partners can see how a figure was produced instead of asking.

AttributionSub-IB networkCommission tracePayout requestsStatementsMarketing assets
Explore the IB system
partners.demo-broker.com/portal
Partner overview
IB Portal
VP
Payable balance
$18,940
Settled to 31 Jul
Attributed clients
312
▲ 18 this month
Commission · 30d
$6,420
▲ 9.1%
Conversion rate
34.2%
Link to funded
Attributed volume
Lots · 12 months
Commission by plan
Settled
Tier 2 rebate52%
CPA31%
Sub-IB share17%
Network and sub-IBs
3 levels
Vantage PartnersMaster IB312 clients
Atlas ReferralsSub-IB118
K. OseiSub-IB41
Meridian GroupSub-IB86
Campaign performance
Broker-issued
CampaignMarketClicksFunded
NL-07 · SummerEU4,120148
NL-11 · WebinarEU1,86062
NL-14 · ReferralRestricted94027

Trader Portal

The broker-owned client experience, on any device.

Onboarding, document upload, account discovery and configured engagement, under the broker brand rather than a collection of unrelated third-party interfaces.

Native KYC uploadAccount catalogueChallengesRewardsLeaderboardsSupport
Explore the trader experience
my.demo-broker.com/portal
Overview
Trader Portal
MK
Broker points
3,480
▲ 320 this week
Challenges completed
11
Documents
Verified
Policy v4
Account types available to you
Explore account types
Account typePlatformCurrencyMinimum
StandardMetaTrader 5USD · EUR$100
ProMetaTrader 5USD$2,500
Raw spreadMetaTrader 5USD$5,000
DemoMetaTrader 5USD—
Your challenges
Trader lane
Trade 15 lots12 / 15
Weekly · ends Sunday+750 points
Complete profile3 / 4
One-off+150 points
Rewards catalogue
Broker-selected
Trading credit1,200 ptsAvailable
Cashback reward2,000 ptsAvailable
VIP account tier6,500 ptsLocked
CRM.IB.Trader.One ecosystem.

Three audiences, one operating foundation. The connection is the product, not an integration project you run afterwards.

One connected broker ecosystem

Not three products. One platform with three front doors.

The same identity, policy and evidence run underneath every workspace, so a change made once is respected everywhere it matters.

Broker Back Office
  • Operations and compliance
  • Client and partner servicing
  • Approvals and evidence
IB Portal
  • Attribution and networks
  • Commission records
  • Payouts and statements
Trader Portal
  • Onboarding and documents
  • Account discovery
  • Challenges and rewards

Shared underneath every experience

IdentityPermissionsKYC policyAccount typesAttributionClient recordsWorkflowApprovalsRewardsBrandingAudit evidence

What changes

Fewer disconnected tools. More accountable operations.

Connect operations
Replace fragmented relationship workflows with shared identity, records and governed actions.
Grow partner channels
Make attribution, networks, commission evidence and partner servicing easier to operate.
Own the experience
Keep onboarding and engagement under the broker brand across every device.
Configure safely
Publish policies, account types and programme rules through scoped, audited administration.

Native KYC and account configuration

Configure KYC around the broker policy.

Define required documents, permitted file types and automatic or manual review routes, then map each published account type to a broker-approved MT5 group.

nexus.demo-broker.com/back-office/kyc
KYC review
Compliance
CM
Awaiting review
23
Oldest 3h
Auto-approved · 7d
412
▲ 8%
Override rate
1.9%
Within threshold
Submission in progress
Live route
SUB-40912 · A. DuarteReceived
Received→Validated→Policy→Routed→Recorded
Review queue
Manual route
ClientDocumentOutcomePolicyAge
A. DuarteSource of fundsManual reviewPolicy v412m
R. OkaforProof of addressAuto-approvedPolicy v431m
T. LindqvistIdentityRejected · unreadablePolicy v41h
H. NasserIdentityAuto-approvedPolicy v32h
C. BianchiSource of fundsManual reviewPolicy v43h
Published policy
Version 4
  • Required documents3
  • Accepted typesPDF · JPG · PNG
  • Maximum file size8 MB
  • Jurisdiction rules14 configured
  • Automatic route
  • Four-eyes on override

Broker publishes a versioned KYC policy

Required documents, accepted file types, size limits and review route.

Trader receives only their relevant policy

Scoped to the authenticated client and jurisdiction.

Documents upload to broker-private storage

Through a controlled gateway, with credential-bound receipts.

The CRM validates the receipt pack

Checked against the published policy before anything reaches a queue.

AutomaticEligible submissions route without staff handling.
Manual reviewEverything else enters a queue with SLA visibility.

Decisions carry reason and evidence

Overrides require explicit permission and append-only audit records.

Account type maps to an approved MT5 group

Individual IB override, then general IB group, then the standard route.

Deployment note. Account opening through the MT5 Manager API is configured for broker deployment and enabled during implementation, once the controlled write path, credential delivery and broker staging evidence are signed off.

Responsible engagement

Retention programmes shaped around your audiences.

Trader and partner programmes are configured separately, so rules, rewards and rankings never cross audiences. Eligibility, caps, cooldowns and evidence are part of the programme, not an afterthought.

nexus.demo-broker.com/back-office/engagement
Engagement programmes
Administration
RM
Active challenges
4
Points issued · 30d
1.42M
Redemptions pending
12
Governed lifecycle
Weekly trader challenge
Draft · not published
  • Audience laneTrader
  • ScheduleWeekly · Mon 00:00 UTC
  • MetricLots traded · MT5 volume path
  • Target15.0 lots
  • Points awarded750
  • EligibilityVerified KYC · funded
  • Caps and cooldowns
  • Replay-resistant evidence
Pseudonymous leaderboard
Weekly
  • 01quiet-harbour9,240
  • 02silver-ridge7,880
  • 03eastward-nine5,410
  • 04north-fifteen3,110
Programme health
Broker-moderated
Programme progress68% of cohort engaged
Eligible participants 2,140Redemptions 318

White-label configuration

Your infrastructure. Their brand.

The same interface structure, published with each broker's own logo, colour, typography, hostname and display name. Brand assets stay separate from the product so upgrades do not overwrite them.

nx.northline-markets.com
Account tierStandard
Challenge progress12 / 15
Points3,480
Explore account types
portal.kestrelfx.com
Account tierPrime
Challenge progress12 / 15
Points3,480
Explore account types
my.aureliacapital.com
Account tierGold
Challenge progress12 / 15
Points3,480
Explore account types
In delivery. Runtime broker brand packs and fleet rollout are designed for white-label deployment and remain in active delivery. The brokers shown are illustrative.

Deployment model

Each broker environment is segregated.

Brokers do not share a database, a hostname or a brand. Updates run per environment through backup, preflight, migration, smoke and rollback steps designed to preserve broker data and branding.

HX Nexus platformShared product, not shared data
Broker A
  • Own deployment
  • Own database
  • Own hostnames
  • Own brand pack
  • Own MT5 host configuration
Broker B
  • Own deployment
  • Own database
  • Own hostnames
  • Own brand pack
  • Own MT5 host configuration
Broker C
  • Own deployment
  • Own database
  • Own hostnames
  • Own brand pack
  • Own MT5 host configuration

No cross-broker client data · No shared tenant storage · Row-level security with crossed-tenant tests

Governance

Every sensitive action carries its own evidence.

Governance is a path through the system rather than a badge on a marketing page. Each step is enforced in the product and retained afterwards.

01UserAn authenticated staff, partner or trader session.
02RoleScoped from a broker-defined role catalogue.
03PermissionChecked per action, not per screen.
04ActionHigh-impact mutations require strong proof and a reason.
05ApprovalFour-eyes where the broker has defined it.
06AuditAppend-only evidence retained against the record.
nexus.demo-broker.com/back-office/approvals
Approvals
Governance
FA
Approval inbox
Four-eyes
RequestSubjectTypeRaised by
Withdrawal · $4,200M. KarlsenSecond approvalA. Novak
Commission plan · Tier 2Vantage PartnersPublishR. Idris
KYC overrideT. LindqvistExceptionC. Marek
Permission grantDesk 3 · refundsRole changeA. Novak
Payout request · $9,800Northline IBSecond approvalF. Adeyemi
Evidence trail
Append-only
  • Requested by A. Novak with reason09:14
  • Strong proof re-authentication passed09:14
  • Policy check withdrawal limit v209:15
  • Awaiting second approvernow

Fail-closed, not fail-quiet.

When a source is unavailable, the interface says so. It does not silently substitute demo or fixture data, because an operations team acting on invented numbers is worse than an operations team that has to wait.

Tenant-pinned requestsRow-level security Crossed-tenant testsSeparate audience sessions Time-bound break-glassAppend-only records
Security and deployment

Build your broker ecosystem

Switch on what you operate. The platform assembles around it.

Every module resolves to the same identity, permission and audit layer. Select the pieces that match your operation to see how they connect.

One deployment.One identity layer.One connected broker ecosystem.
hx0 / 8 activeBroker CRMTrader PortalIB PortalNative KYCAccount typesEngagementMT5 integrationSupport desk

Integration

Built around your existing infrastructure.

The trading platform integration is specific and documented. Everything else is configured to the broker's own providers during implementation rather than assumed.

MetaTrader 5 — Manager API

Tenant-pinned adapter for clients, accounts, groups, deals and balance operations used by CRM workflows.

Built and tested

MT5 account provisioning

Deterministic route resolution across individual IB, general IB and account-type groups.

Enabled during implementation

Configured to your providers.

HX Nexus does not ship a fixed vendor list. Storage, payment methods, messaging and support destinations are set per broker during implementation, against the providers you already hold contracts with.

KYC document storageBroker payment methodsEmail and messaging deliverySupport and ticketingReporting exportsCRM migration sources
MT5 integration detail
nexus.demo-broker.com/back-office/settings/mt5
MT5 integration
Settings
TS
Account type to MT5 group mapping
Broker-approved
Account typeStandard routeGeneral IB routeIndividual IB override
Standardreal\NL\stdreal\NL\ib-stdNot set
Proreal\NL\proreal\NL\ib-proreal\NL\vp-pro
Raw spreadreal\NL\rawreal\NL\ib-rawNot set
Demodemo\NL\std—Not set
Route resolution order
Deterministic
  • 1 · Individual IB overrideChecked first
  • 2 · General IB groupIf partner attributed
  • 3 · Account-type groupDefault route
  • Group catalogueRead from Manager API
  • Free-text group namesNot permitted
Manager API boundary
Per-tenant adapter
  • Client and account snapshotsRead
  • Deal volume for challengesRead
  • Group catalogueRead
  • Account creationControlled write
  • Order placementOut of scope
  • Margin and risk decisionsOut of scope

Built for the relationship and operational layer.

HX Nexus connects broker CRM, IB operations and trader experiences while remaining separate from the broker's trading and dealing infrastructure. MT5 data supports servicing, attribution, commissions and engagement progress under broker-controlled policies.

Not a trading terminal
Not a dealing platform
Not a risk engine

See HX Nexus against your operating model.

See how your CRM, onboarding, partner and trader workflows can operate through one broker-branded ecosystem.