Brokers and CFD providers
Your own trading front end, on the back end you already have
Web terminals, mobile apps and back-office screens in your brand, connected to the platform, bridge and CRM you already run. For brokers who want to own the client experience without replacing everything behind it.
Illustrative screen built on synthetic data
Who it is for
Built for brokers and cfd providers
Brokers on a third-party platform
Firms that want their own web or mobile front end while keeping the platform's back end, risk and reporting.
Brokers adding products
Firms adding asset classes, account types or markets that the current front end handles badly.
Brokers fixing retention
Firms losing new clients in the first days, where onboarding, the first trade and the charts are the problem.
What you get
Features for both sides of the screen
01
For your clients
- Web terminalWatchlists, charts, order tickets with inline validation, positions and history, in your brand.
- Mobile appsiOS and Android apps that stay usable on a weak connection, with the same account state as the web.
- A simple first tradeA guided first order for new clients and the full ticket for experienced ones, without two separate products.
- Costs before the clickSpread, margin and overnight charges shown before the order is placed, not after.
02
For your dealing and operations team
- Back-office viewsAccounts, exposure, open positions and client activity in one place.
- Configuration, not codeNew instruments, fields and account types added through configuration wherever the platform allows it.
- Audit trailWho changed what, and when, for every setting your compliance team cares about.
- Support toolsThe client's own view of an account, available to your support team without asking for screenshots.
How we connect
One front end, several systems behind it
- 1
Platform and bridge
Prices, orders and positions through the platform's APIs, FIX sessions or the bridge your liquidity runs through.
- 2
CRM and client portal
Accounts, verification status, deposits and withdrawals from the systems that own them.
- 3
One state, every screen
A single account state pushed to web, mobile and back office, so the three never disagree.
Details clients notice
What separates a terminal people trust from one they tolerate
- Reconnects
- A dropped connection resumes from the last known state, without a reload and without duplicate orders.
- Validation as you type
- Order size, margin and price limits checked in the ticket, so rejections from the server are rare.
- Low-bandwidth mobile
- Snapshots plus small updates rather than full refreshes, so the app keeps working on a train.
- Statement agreement
- Charts, positions and statements built from the same data, so a candle never contradicts the account history.
Why AlchmAI
Why trading firms choose a specialist
Front-office pedigree
Six bank trading apps on one ticket library.
Keep your back end
No platform replacement required.
Your brand, your code
Repositories and design files are yours.
Configuration first
New products without new screens.
Charts done properly
From the team behind a 100m-tick chart.
Compliance in the build
Cost disclosure and audit trails from the first sprint.
Selected work, uk investment bank, markets division
Six front-office trade capture and pricing applications on one configuration-driven ticket library
A prop firm dashboard, a broker's order ticket and an RFQ blotter are the same problem: fast, validated input that stays in sync with everything else. We have built it where the stakes were highest.
6
applications on one shared ticket library
0
code changes to onboard a new product or field
15+
engineers working to the standards set at inception
How we engage
It starts with a two-week Platform Review
1. Weeks 1 to 2
Platform Review
Read-only access. Findings report, costed plan and a prototype where it helps. You sign off the baseline we will measure against.
2. Weeks 3 to 8
Build, in fortnightly releases
Working software every two weeks on an environment you can use. Any AI wording is agreed with your compliance lead before a client sees it.
3. Go-live
Evidenced release
A runbook, an evidence file your compliance lead can read in one sitting, and an off switch for every AI feature.
4. Day 90
Results check
What changed, measured against the baseline you signed at the review.
Questions
Brokers and CFD providers: common questions
Do we have to replace our trading platform?
No. Most brokers keep their platform for execution, risk and reporting and add their own front end on top. We integrate through whatever the platform exposes.
Can you build both web and mobile?
Yes, on a shared code base where it makes sense, so the same validation and account logic runs on both.
Who owns the code and the design?
You do. Repositories, design files and documentation are handed over, and nothing is built on a framework that ties you to us.
Can you add AI features to the terminal?
Yes, using Signed-off analysis, so chart summaries describe the market and never recommend a trade.
How long does a terminal take?
It depends on the products, the number of integrations and the state of the APIs behind them. The Platform Review gives you a costed plan before anything is built.
Related
Often built alongside
FIX and broker API integration
Order entry, market data and drop copy over FIX, plus REST and WebSocket broker APIs.
Learn moreMarket data infrastructure
Feed handling, tick storage, aggregation, replay and distribution, monitored end to end.
Learn moreAI agents for trading teams
Narrow agents with fixed tools, limits, approval queues and a kill switch.
Learn moreShow us where new clients drop off.
Share your onboarding and first-trade flow on a call, and we will point to the screens that are costing you clients.