Launch your brokerage in three days.
ForgeTerminal, ForgeQuote, ForgeCRM and ForgeRails are one system on one source of truth — not four products glued together.
3
- Days to live
- Technical setup only. Licensing, incorporation and banking are procured separately and are not in this figure.
See day-by-day breakdown ›
One system against seven seams. Every seam is a hand-off point: latency, identity, reconciliation, support ownership, data location, liability.
One stack, not five vendors.
One bounded system
- ForgeTerminal
- ForgeQuote
- ForgeCRM
- ForgeRails
one system, one source of truth
0 seams
A typical five-vendor stack looks like this: five vendors, five separate contracts, five support queues.
7 seams
The arrangement above is illustrative, not surveyed — it is the shape these stacks usually take, not an industry average. The seam count is exact: it counts the hand-off points drawn in the diagram.
- 01PlatformFeedlatencyOne extra network hop on every quote.
- 02PlatformCRMidentityAccount state held in two places.
- 03PSPHostingpaymentsDeposit flow crosses an ops boundary.
- 04CRMPSPreconcileTwo ledgers, nightly, by hand when it breaks.
- 05FeedHostingsupportOutage ownership disputed between vendors.
- 06CRMHostingdataRecords sit where you did not choose; exit is a migration project.
- 07meshyour opsliabilityNo single accountable party, so it lands on your team.
Four things that follow from owning the stack.
- 01
Native integration
One system of record. A trade, its margin calculation and its ledger entry belong to one system, not three synced copies. No integration layer between them to fail.
→ mechanism: one source of truth
- 02
Your own pricing engine
ForgeQuote is ours. Spread, markup and book routing change in the interface, not in a support ticket.
→ mechanism: no upstream licence gate
- 03
Independent technology
No third-party platform licence in the stack, so no per-seat fee and no roadmap owned by someone else.
→ mechanism: no third-party platform fee
- 04
One contract, one team
One commercial agreement covering the whole stack. One escalation path, with no hand-off between vendors.
→ mechanism: single accountable party
Three starting points, and what each one actually has to move.
Where are you starting from?
- 01
You are launching
No stack, no accounts, no flow yet.
Everything stood up at once, in an order that does not leave you waiting on a third party.
In scopeFull technical setup. Licensing, incorporation and banking run in parallel on your side.
- 02
You are an IB or affiliate becoming a broker
You have the flow and the relationships; someone else holds the infrastructure and the client data.
Your own book, your own pricing, and your existing partner tree carried over intact.
In scopeIB structure and client records migrate. Your commission logic is configured, not rebuilt.
- 03
You are already running a brokerage
A live book on a stack you did not choose, with seams you now maintain.
To move without a trading halt, and to know in advance exactly what moves and what does not.
In scopeAccounts, balances, open positions, closed history and IB tree. Cutover is rehearsed before it is run.
Proof surface 1 of 3. The instrument here is a horizontal time axis.
Three days, and what happens in each.
1
- Day one
- Configuration. Instruments, spreads, leverage tiers, account types and branding are set against your commercial model.
2
- Day two
- Integration. Liquidity connections, payment rails and your domain and mail records are brought up.
3
- Day three
- Testing and handover. Order flow, deposits and withdrawals are exercised end to end, then your team takes the keys.
It is fast because nothing in it has to be negotiated with a third party. There is no vendor onboarding in the critical path — the terminal, the pricing engine, the CRM and the payment layer are all ours, so the only schedule involved is yours and ours.
Placeholder — step 3. The horizontal tick axis that binds the three days into one scale, with major ticks at each day boundary.
Proof surface 3 of 3. The instrument here is a two-column answer ledger.
What about MetaTrader?
Handled in the open, in the words it actually gets asked in. If an answer here does not hold up under a technical review, we would rather you find that out now than after a contract.
- My traders only know MetaTrader. They will not switch.
- The interface follows MT conventions: the same order ticket, the same chart interactions, the same one-click trading and depth window. Retraining is measured in minutes, not weeks.Documentation link pending — ask for it in the demo.
- We have years of MQL expert advisors. We cannot rewrite them.
- MQL expert advisors run directly on ForgeTerminal. No transpiling step and no rewrite — you upload the same file.Documentation link pending — ask for it in the demo.
- Our tooling is built against the MT4 Manager and Gateway APIs.
- Full Web, Manager and Gateway API access is available, so existing integrations keep their shape rather than being rebuilt against something unfamiliar.Documentation link pending — ask for it in the demo.
- Migrating live accounts is where this goes wrong.
- Accounts, balances, open positions, closed history and the IB structure all migrate. History and IB tree are the two that most vendors quietly drop; they are in scope here.Documentation link pending — ask for it in the demo.
- Some of our partners contractually require MT5.
- MT4 and MT5 remain available as a managed service on our infrastructure. Choosing ForgeTerminal is not a requirement of working with us.Where to check this ›
The other half of the business, in one paragraph.
Managed infrastructure.
If you are staying on someone else's platform, we will still run it for you. MT4 and MT5 servers, cTrader, oneZero and PrimeXM X‑Core, hosted and maintained on our infrastructure with one support plan. This is a separate line of business from the stack above, and it does not require you to adopt any of it.
Published, because asking you to book a call to learn a price is a tactic, not a process.
Pricing is published.
No discovery call to find out what it costs. The page lists setup, monthly and per‑module figures, and the calculator gives you a number for your own volume and account count before you speak to anyone.
Placeholder — pricing figures required (brief §11).The page and the calculator are built in a later step; the figures themselves are a commercial decision and are not invented here. When they land they go in src/data/metrics.json like every other number.
Trust.
- Data ownership and exitWhat is yours, and how you take it with you.
- Execution transparencyWhich figures we publish, which we do not, and what each one still needs.
- Security and custodyWho can move money, and what stops them.
- RoadmapWhat is not built yet, dated.
See it before you decide.
A demo environment with your own credentials, not a guided screen‑share. Access lasts 14 days and can be extended.