The engine, and everything built on it
At the centre of everything Jcom makes is a trading engine: the core machinery that takes prices in, matches and executes orders, calculates margin and equity in real time, keeps account state, and writes the audit trail behind all of it. It is the part no user ever sees, and it is the part everything else depends on.
Around that engine we build the platform: the trading panel a client trades on, the personal cabinet where they manage their account, and the admin and CRM back office where a brokerage runs its whole operation. The three ship together, on top of the same engine, so a price on a chart, a balance in a cabinet and a position in the back office are always the same number.
One engine serves every deployment. What differs per brokerage is everything a person can see: the brand, the domain, the design, the instrument list, the account types and the terms. That separation is the whole product.
What is in the platform
A brokerage does not just need a price chart. It needs the machinery around it: the place clients trade, the place clients manage themselves, and the place staff run the operation. All three ship together.
Client trading panel
The screen the trader actually uses: charts, watchlists, the order ticket, open positions, pending orders, margin and equity, and history. It runs in the browser, so there is nothing for the client to install.
Personal cabinet
Where the client manages the account rather than the trade: profile and document upload, deposit and withdrawal requests, statements, and the thread back to the broker's support desk.
Admin and CRM back office
The broker's operational cockpit: client and lead management, account administration, risk controls, finance, a support desk, notifications and staff permissions. This is the part most brokers underestimate.
Market data distribution
Prices are taken upstream once and distributed to every deployment, so quotes and charts stay consistent instead of each installation fetching and reconciling its own feed.
Risk and account controls
Leverage caps, instrument permissions, account types and margin behaviour are configuration, not code. The broker decides what its clients can trade and on what terms.
Deployment and branding
Each licensee gets its own environment, its own domain, and its own logo, palette, typography and copy. Two brokers on the same engine should not look like the same product.
What the back office actually does
The admin and CRM side is where a brokerage is run day to day, so it is worth being specific about what a member of staff can do inside it.
- Clients and leads. One record per person, holding the enquiry, the documents, the accounts, the tickets, and a history of what staff changed and when.
- Account administration. Create and configure trading accounts, set the account type, apply leverage and instrument permissions, and change the state of an account.
- Risk controls. Caps and limits that constrain what an account can do, so exposure is a setting rather than a surprise.
- Finance. Deposit and withdrawal requests arrive as work items, are reviewed by a person, and carry an approval trail. The money itself moves through the broker's own payment providers, never through us.
- Support desk. Client conversations land in a queue that staff can assign, answer and close, next to the client record rather than in someone's inbox.
- Notifications. Operational and system events raised to the staff who need to see them.
- Staff permissions. Roles decide who can see and change what. A support agent and a finance approver are not the same person and should not hold the same rights.
The model: shared engine, your brand
The engineering argument for white-label is boring and correct. Order handling, margin calculation, market-data plumbing, account state and the audit trail are hard, and they are the same problem for every brokerage. Rebuilding them per client would mean maintaining six versions of the same bug.
So we maintain one engine and improve it for everyone, and we keep everything a client sees separable from it: the design system, the brand, the domain, the copy and the configuration all belong to the licensee. A fix to the engine reaches every deployment. A change to your look reaches only yours.
The consequence for a trader reading this page is simple. The platform may be ours, but the terms are not. Your spreads, swaps, commissions, leverage, instrument list and account tiers were chosen by your broker. If you want to know why a number is what it is, the person to ask is your broker.