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.

Book a broker walkthrough Explore the platform
Broker Back OfficeIB PortalTrader Portal

Three connected experiences

Built for three audiences. Governed as one system.

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

Broker Back Office

Manage leads, clients, KYC, partners, operations, engagement and approvals from role-relevant workspaces.

For CRM, compliance and operations teams

IB Portal

Give partners transparent access to campaigns, networks, commissions, reports, payouts, support and engagement.

For introducing brokers and partner managers

Trader Portal

Deliver broker-native onboarding, account discovery, challenges, rewards and branded engagement.

For your clients, under your brand

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. Publish trader account types and map each route to broker-approved MT5 groups, including general and individual IB mappings.

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.

Broker publishes a versioned KYC policy

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

Trader sees 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.

Automatic approval or manual review

Eligible submissions route automatically; everything else enters a review queue.

Decisions carry reason and evidence

Overrides require explicit permission and append-only audit records.

Challenge schedule
Daily · Weekly · Monthly
Progress metric
Lots traded · CRM events
Points
Custom name and icon
Rewards
Broker-selected catalogue
Leaderboards
Pseudonymous, moderated
Controls
Caps · Cooldowns · Eligibility

Responsible engagement

Retention programmes shaped around your audiences.

Schedule Trader and IB challenges separately, define points and rewards, track approved metrics and offer branded mini-games with configurable eligibility and abuse controls. Rules, rewards and rankings never cross audiences.

Integration and governance

Connected to MT5 through a controlled boundary.

Broker-approved platform data supports CRM servicing, partner attribution, commissions, account routing and engagement progress — under explicit deployment controls, never as a dealer surface.

Tenant isolation

Every broker request is bound to a tenant context, with database row-level security and cross-tenant testing.

Isolation

Strong-proof actions

High-impact mutations require strong proof, an explicit reason and, where defined, separate four-eyes approval.

Governance

Append-only evidence

Policy, approval and lifecycle records are retained as append-only evidence. Unavailable states show honestly rather than substituting fixture data.

Auditability

Deployment fit

Deployed per broker. Configured to your brand.

Each broker runs its own deployment with configurable hostnames for the Back Office, Trader and IB experiences. The upgrade path is designed to preserve broker databases and brand assets through backup, preflight, migration, smoke and rollback steps.

In delivery. Runtime broker brand packs and fleet rollout are designed for white-label deployment and remain in active delivery. We show you exactly where each capability stands during the walkthrough.

Brand pack

Logo, colour, typography, favicon and display name, published as shared design tokens.

Hostnames

Broker-configured labels and domains for admin, Trader and IB experiences.

Policy and account types

KYC policy, enabled demo and live account types, and broker-approved MT5 group routing.

Programmes

Commission plans, challenges, rewards and games, published through scoped administration.

Controlled updates

Backup, preflight, migration, smoke and rollback steps that preserve broker data and branding.

Product boundary

The relationship layer. Not the trading stack.

  • Not a trading terminalIt does not place or manage trades.
  • Not a dealing platformIt does not automate dealer decisions.
  • Not a risk engineIt does not calculate margin, liquidation, hedging or exposure.

See it against your own operating model.

A working session with the product team: your CRM, partner and onboarding workflows mapped to the platform, with an honest view of what is built and what arrives during implementation.

Book a broker walkthrough Explore the platform