Bruno Bridge · Datasheet
Product Specification & Commercial Terms · Bruno Bridge
Bruno Bridge — MT5 Execution Infrastructure
Price confirmation, order and risk routing, and A-book/B-book clearing for MT5 brokers — delivered as a standalone bridge into an operator's existing MT5 servers, independent of whether that operator runs the rest of the Bruno suite. This document covers connectivity, deployment, security posture and published pricing.
99.95%
Contractual uptime
$0.25
Per $1M, price confirmation
$1,000
Monthly minimum, covers hosting & maintenance
SOC 2
Compliant
What Bruno Bridge is § 01
Bridge is the MT5 execution layer — price confirmation, order and risk routing, and A-book/B-book clearing — for brokers who need institutional execution infrastructure without adopting Bruno's full Core/OMS/Admin suite. It plugs into a broker's existing MT5 server; client bases are not migrated and retail order flow is not interrupted.
| Product class | MT5 price confirmation and execution bridge |
| Operator type | MT5 brokers and dealing-room operators — standalone, not conditional on running Bruno Core |
| Core functions | Real-time price streamingNative price confirmationAdvanced order routingA-book / B-book clearingLive LP hedgingConfigurable risk gatesVirtual dealer desk |
| Order handling | Market orders processed Immediate-or-Cancel (IOC); limit and take-profit orders processed Fill-or-Kill (FOK); full open, close and partial-close support |
| Onboarding | Config-driven. Brand, server and symbol are externalised configuration — no code changes to onboard a new MT5 server |
| Commercial model | $2,000 one-time setup, then a per-$1M fee on confirmed volume billed monthly against a $1,000 minimum. No minimum term (§ 07) |
How it works § 02
Every order that reaches a broker's MT5 server passes through the same confirmation and routing path below before it is filled.
- Order submitted. A trader places a market, limit, or take-profit order on the broker's MT5 server.
- Price confirmed. Bridge ingests L2 depth in real time and confirms the order against a VWAP fill calculated across every price layer consumed.
- Risk gates applied. Stale-quote rejection, gap absorption on limit orders, and max-deviation protection on market orders run before the order is accepted, with every threshold configurable per symbol.
- Routed by book. A-book orders route straight through to a liquidity provider; B-book orders are warehoused internally. Routing is configurable per symbol, group, or account.
- Manual review when flagged. Orders that need dealer review enter the lease-based Virtual Dealer queue instead of routing automatically — take, approve, partially fill, reject, or release.
- Execution confirmed back to MT5. The fill (or partial fill) is written back to the trader's account, with the confirmation and clearing decision retained for audit.
Bridge specifications § 03
| Price streaming | Real-time streaming price feed into the broker's MT5 server, underpinning every downstream confirmation and routing decision |
| Price confirmation | Real-time L2 depth aggregation with VWAP fills calculated across every price layer consumed |
| Order routing | Rules-based routing engine — A-book or B-book, configurable per symbol, group, or account — with dealer-queue override for flagged orders |
| Clearing | A-book straight-through processing to liquidity providers, or B-book internal warehousing — configurable per symbol, group, or account |
| Live hedging | B-book exposure can be hedged live with a liquidity provider in real time, rather than carried unhedged |
| Risk gates | Stale-quote rejection · Gap absorption on limit orders · Max-deviation protection on market orders — all configurable per symbol |
| Virtual Dealer Desk | Lease-based dealing desk queue for orders flagged for manual review, with full state tracking on every action |
| Order-level monitoring | Order-level reporting and monitoring across confirmation, routing, and clearing decisions |
| Group & symbol management | Per-brand, per-server and per-symbol configuration; every threshold and routing rule overridable at any level |
Integration & connectivity § 04
| MT5 side | Native MT5 bridge — socket/API integration directly against the broker's MT5 server. No third-party bridge layer required. |
| Liquidity-provider side | FIX 4.4 outbound sessions to liquidity providers, used for confirmed A-book straight-through order routing |
| Session security | TLS 1.2+ session-level encryption |
| Existing infrastructure | Bridge sits alongside a broker's existing MT5 setup rather than replacing it — client bases are not migrated and active order flow is not interrupted |
Deployment model § 05
| Deployment | Managed SaaS, hosted on Tradesocio's AWS infrastructure — no on-premise or source-code licensing option |
| Onboarding | Config-driven — no code changes required to bring a new MT5 server, brand, or symbol group online |
Security & compliance § 06
| Infrastructure | Hosted on AWS, Tradesocio's standard production infrastructure |
| Access control | Role-based access, scoped per brand and per operator |
| Compliance | SOC 2 compliant |
| Audit trail | Full audit trail on price confirmation, risk-gate decisions, clearing routing, and Virtual Dealer actions |
Commercial terms § 07
A $2,000 one-time setup fee, then a per-$1M fee on confirmed volume, billed monthly against a $1,000 minimum. No minimum term.
Setup
$2,000
One-time
Minimum term
None
Month to month
Monthly minimum
$1,000
Covers hosting & maintenance
Currency
USD
Exclusive of applicable taxes
| Service | Fee |
|---|---|
| Price confirmation | $0.25 per $1M |
| A-book clearing | $1.00 per $1M |
Options and definitions
| Confirmed volume | Notional value of orders that pass through Bridge's price confirmation in the calendar month |
| Monthly minimum | $1,000 per month, billed whenever combined price-confirmation and A-book-clearing fees total less than $1,000 in the calendar month. Covers hosting and maintenance. |
| Additional FIX connection | By agreement |
| Annual commitment | Optional. There is no obligation to take one. |