EventWe're exhibiting at Forex Expo Dubai πŸ‡¦πŸ‡ͺMeet us at Forex Expo Dubai πŸ‡¦πŸ‡ͺAt Forex Expo Dubai πŸ‡¦πŸ‡ͺ22–23 Sep 202622–23 SepSee the schedule
Support

A named lead, not a ticket queue.

Every firm gets an implementation lead who owns the launch or migration end to end β€” program design, platform connection, data migration, team training and the parallel run before cutover.

Onboarding planNamed lead
Week 1Discovery + data mapping
Week 2Staging migration + rules
3Week 3Parallel run Β· both systems
4Week 4Cutover + hypercare
The path

Technology ready in 10 days.

Dated, owned, and reversible until you sign off at each gate. Payment, KYC, broker, and regulatory onboarding may affect the full market-launch date; migrations follow their own 4–8 week plan.

1
Days 1–2

Scope & design

Programs, rules, roles, branding, and required integrations agreed.

2
Days 3–5

Connect & configure

Trading platforms and approved provider accounts wired into your sandbox.

3
Days 6–8

Test & train

End-to-end flows tested while risk, ops, and finance teams train on the platform.

4
Days 9–10

Technology handoff

Configuration signed off and the production-ready technology handed to your team.

Total time to live
10 days
Why it's structured

Most platform failures are implementation failures.

No single owner

When implementation is split across a support queue, nobody holds the timeline and slippage is nobody's fault.

Migration done blind

Data moved without reconciliation means gaps discovered months later, usually during a dispute.

Training as an afterthought

The platform goes live and the team learns it in production, on real traders, under pressure.

Included

What's included

Standard on every firm running on the platform. No add-on tier, no per-seat unlock.

06capabilities
included by default
  • 01Named implementation lead
  • 02Shared channel with our engineers
  • 03Program design and economic modelling
  • 04Data migration with reconciliation sign-off
  • 05Team training before go-live
  • 06Hypercare for 30 days after cutover
Questions

Questions operators ask

No. A named lead, the migration work and team training are included with the platform. Bespoke development beyond standard configuration is scoped separately through Dedicated Tech Teams.
A decision-maker who can approve program design, someone technical for platform and PSP credentials, and your ops lead for training. Roughly a few hours a week, concentrated in weeks one and three.
You don't. The parallel run continues until you're confident, and the legacy system stays readable as a fallback. We keep the delta sync running through that period.
Let's talk

Get a dated implementation plan.

Tell us your stage and constraints and we'll come back with a week-by-week plan.