One of four products in one stack. The same page structure on all four, so comparing them is reading rather than hunting.
ForgeQuote
The pricing engine and liquidity layer: it takes provider feeds, applies your markup and routing rules, and produces the prices your clients trade on.
What it removes.
The support ticket between you and your own spread. Changing a markup, a routing rule or a book assignment is something you do in an interface, in seconds, on your own authority. It also removes the assumption that your pricing is someone else’s product to tune.
Capabilities.
- 01
Your markup, your rules
Spread, markup and commission are configured per instrument, group and account type. Changes take effect without a deployment or a request to us.
- 02
A book you control
A-book, B-book and hybrid routing are decisions you make per group and per instrument. The logic is visible rather than inferred from behaviour.
- 03
Aggregated liquidity
Multiple provider feeds combined into one book with per-provider weighting. Adding or dropping a provider does not touch the terminal.
- 04
Execution you can audit
Every fill records the price it was quoted at, the provider it went to, and the latency of each hop. Disputes end in a query rather than an argument.
The claim is one system. This is where it is either true or not.
How it connects to the rest of the stack.
Not "integrates with" — there is nothing between these to integrate. Each line below names what actually crosses, and what does not have to happen as a result.
- ForgeQuote ForgeTerminal
- The terminal renders exactly what the engine produced. There is no intermediate feed to explain a discrepancy.
- ForgeQuote ForgeCRM
- Group and account-type pricing rules live where the accounts live, so a client moved between groups is priced correctly immediately.
- ForgeQuote ForgeRails
- Margin is calculated against the same balance payments settle into, so a deposit is usable margin without a reconciliation pass.
Technical detail.
| Providers | Multiple concurrent feeds, per-provider weighting and failover. |
|---|---|
| Routing | A-book, B-book, hybrid. Per group, per instrument. |
| Integrations | oneZero and PrimeXM X‑Core are supported as managed infrastructure. |
| Audit | Per-fill record of quote, route and per-hop latency. |
Interface.
No screenshots yet. Real interface captures and a short video are outstanding (brief §11). A stock mock-up would be the one thing this page cannot afford: the pitch is that the product exists, and a fabricated screenshot argues the opposite to anyone who looks closely. The demo environment is the honest substitute until the assets exist.
Questions that come up.
Not written yet. The brief asks for three or four questions that actually come up in sales calls. Those have to come from someone who has sat in them — inventing plausible-sounding questions would produce a section that answers nothing a real buyer asked.
5open items on this page
- Screenshots of the pricing configuration screens, and a short interface video (brief §11).
- Latency figures and the measurement endpoints they are taken between — see /trust/execution. No number appears here until it carries its endpoints, statistic, window and sample size.
- The list of liquidity providers we are integrated with today.
- Which asset classes are covered at launch, and which are not.
- FAQ — needs real sales-call questions.
Listed because a page that hides what it does not know is the thing this audience is checking for. Figures among these will each need their measurement definition before they can appear — see execution transparency.
See it before you decide.
ForgeQuote is not sold separately. The demo gives you the whole stack, because that is the only way to check whether the connections above are real.