Everything a brokerage, prop firm or fintech needs to operate — built together, tested together, and operated together. You configure it and put your brand on it.
Most providers sell you one layer and leave you to source the other six. Every integration seam becomes your problem, your timeline, and your incident at 3am. We build and operate the whole stack, then hand it over under your brand.
Assembled and operated as one system
Matching, order routing, and multi-asset execution across crypto, FX, equities and commodities.
Card and alternative payment methods across Africa, Asia and LATAM, with settlement on supported corridors.
Branded physical and virtual cards, per-card and per-transaction economics built in.
Challenge plans, add-ons, evaluation rules, retries and payout logic.
Multi-tier attribution, commission schedules, and partner reporting.
Exposure limits, spread and slippage configuration, and per-instrument risk policy.
Administration, compliance workflows, reconciliation and reporting in one interface.
Click a row to work it
Most vendors treat administration as an afterthought and ship a thin CRM. Your operations team spends more hours here than your customers spend trading.
Granular permissions per desk, per region, per function. Every privileged action is attributed to a named operator and written to an immutable log.
Onboarding review, document verification, sanctions and PEP screening, and case management shaped around the licence you hold.
Positions, payments and ledger reconciled continuously rather than at month end, with breaks surfaced as they occur.
Operational, financial and regulatory reporting from one source, scheduled or on demand.
A single record per client spanning onboarding, funding, activity, support history and risk posture.
Sourced separately, these arrive from five to seven vendors. Each has its own contract, its own SLA, its own outage and its own integration — and when something breaks between two of them, neither owns it.
We build and operate all eight. One contract, one launch date, one engineer who knows your deployment, and no seam between layers for a problem to fall through.
A brokerage or prop firm needs all eight of these on day one. The vendor market supplies them in fragments — the terminal from one, the processor from another, cards from a third — so the launch becomes an integration project across five to seven contracts, each with its own outage and its own finger to point. Here is everything we have built, layer by layer, in full.
“Elsewhere” describes how often a layer is included by vendors in this market as a category. We do not name them.
Matching, pricing and execution across four asset classes on a single account and a single margin position.
Availability of any instrument, payment method, card programme or corridor depends on the licences you hold and on local law. Scoping establishes what is actually available to you before it appears in a build plan.
Sourcing a liquidity provider, an acquirer, a local-method aggregator, a BIN sponsor, a settlement bank and a screening vendor — each with its own commercial minimum, its own underwriting and its own integration — is what takes the year. We already hold those relationships and the integrations are already built, so you join an existing arrangement instead of starting six procurement cycles at once.
We do not publish provider names. The same discretion that keeps your relationship private keeps theirs.
Pricing and fills for four asset classes, plus the feeds the platform quotes from.
Approach providers individually, meet each commercial minimum, negotiate spreads without volume history, then build and certify a separate integration per venue.
Acquirers, sponsors and banks each run their own checks on your business, your directors and your model, and any of them can decline. An introduction improves your odds and shortens the queue. It does not decide the outcome.
Authorisation is between you, your counsel and your regulator. We do not give regulatory or legal advice and are not a substitute for a compliance function.
If a corridor or a model cannot be supported properly, we say so at scoping instead of taking a fee and discovering it during your integration.
Somewhere in every evaluation a developer is asked whether this is sane to integrate with, and the marketing site never answers the three questions that decide it: are webhooks signed, are retries idempotent, and how is money represented. Here they are.
REST over HTTPS, JSON in and out, versioned in the path so an upgrade is your decision rather than ours.
POST /v1/payouts
Idempotency-Key: 9f2c-4a71-b0e8
{
"amount": 250000, // minor units
"currency": "GBP", // ISO 4217
"destination": "acct_...",
"reference": "INV-2291"
}
201 Created
{
"id": "pyt_...",
"status": "pending",
"created_at": "2026-08-21T09:14:02Z"
}Payloads above illustrate shape, not a published schema. The contract that binds an engagement is the integration documentation issued with it, and your engineers get sandbox access during evaluation rather than after signature.
A missing layer is not a discount — it is a second vendor, a second contract, a second integration, and a support boundary that runs straight through your customer's worst day.
| Capability | Platform-only vendors | Liquidity-led providers | CRM-led providers | Krexum |
|---|---|---|---|---|
| Multi-asset trading | ||||
| Payment rails | ||||
| Card issuing | ||||
| Funded-trader system | ||||
| Partner / IB network | ||||
| Risk & execution controls | ||||
| Operations console | ||||
| Coverage | 29% | 57% | 71% | 100% |
Categories describe common vendor shapes in this market rather than any single named provider. Coverage reflects what a buyer must source elsewhere to launch.
Exposure managed per instrument and per client tier, enforced at order entry rather than left to a dealer’s judgement under pressure.
Verification tiers, screening and case management configured to your regime, with the evidence trail a regulator will ask for.
Multi-tier partner structures, commission schedules and payout runs, with every referral attributable end to end.
These are the failures that decide whether a platform survives its first year in production. We list them because we have had to build for them.
A best-effort reconstruction from logs that have partly rotated.
Decisions, policy versions and operator actions are retained as records rather than logs, with the model and rule version that produced each outcome.
