Every broker, on its own rails

Omnitrade keeps FIX and REST connections open to global and regional brokers at the same time. Each connection runs as its own isolated service, so bringing a new broker live or upgrading a spec never disturbs the sessions already trading.

Sessions recover themselves. When a line blips, the platform reconnects and resyncs on its own. No desk ritual, no missed fills.

Sessions
CounterpartyProtocolStatusLast msg
Broker AFIX 4.4● UP09:41:06
Broker BFIX 4.2● UP09:41:05
Broker CREST● UP09:41:02
Broker DFIX 4.4● RESYNCED09:41:04
Broker EFIX 4.4● UP09:41:06
Broker FREST● UP09:40:58
09:31:02  Broker D  session dropped09:31:03  Broker D  reconnected, resyncing 214 messages09:31:04  Broker D  in sync. No fills missed
New order 0005.HK via Broker A
Algo
VWAP▾
VWAP
TWAP
POV
Implementation shortfall
At close
Dark
Quantity40,000
Limit62.30 HKD
Max % volume12%
Start / end09:30 – 16:00 HKT
✓ Valid for Broker A on HKEXPlace order

The ticket writes itself correctly

Every broker documents its algos differently, and the parameters shift by market. Omnitrade handles that in configuration: each ticket is drawn per broker, per market and per algo, with exactly the fields and checks that broker's spec demands.

When a broker adds an algo or changes a parameter, the ticket is updated in configuration rather than waiting on a software release.

Traders don't have to memorise each broker's quirks to use its algos properly.

From the whole fund to a single fill

Consolidated views across custodians, fund vehicles, asset classes and currencies, updating as executions land. Exposure, attribution and contribution sit next to P&L, so "what is driving returns" has an answer on screen the moment you ask it.

Drill from the portfolio to a position to the fills behind it. A PM, a trader and an operations analyst each get the dashboard their job needs.

Fund › Asia book › 9988.HK › fills
P&L today (USD)+4,512,806
● Live
PositionExposureP&LContrib.Custodian
9988.HK2.1M+104,220+1.9%Cust. A
0005.HK1.4M+96,410+0.8%Cust. B
2330.TW1.1M+88,102+1.2%Cust. A
EMAAR.DU0.6M+44,074+0.6%Cust. C
Ledger, Fund A, 30 Sep
TypeEntrySource
TRADEBuy 40,000 0005.HK @ 61.02Execution
SUBSubscription 2,000,000 USD, Class AManual
DIV0005.HK dividend 0.61 HKD / shareSFTP
CORP0700.HK scrip dividend electionSFTP
FEEManagement fee accrual, Q3Manual
XFERCustody transfer 2330.TW, A → BSFTP

Everything the fund did, in one ledger

Trades flow into the ledger straight from execution. Subscriptions, redemptions, dividends, corporate actions, fees and custody transfers arrive by entry or by custodian files over SFTP, so the ledger is a complete record of the fund.

One record of truth. The portfolio views, the shadow NAV and the regulatory reports all read from it.

An adversarial second opinion

Omnitrade computes its own NAV from the ledger, independently of your administrator, and reconciles it against custodian data as it updates: positions, cash and trades, line by line.

Breaks surface the day they happen, with the position, custodian and trade attached. When the administrator's NAV arrives, you have your own number to check it against.

Shadow NAV reconciliation
Shadow NAV$100,284,472
Custodian view$100,258,392
▲ 1 break: Custodian B, 0005.HKPosition 40,000 vs custodian 39,600, trade T-7781 unsettled
Custodian A positions248 / 248
Custodian B positions130 / 131
Custodian C trades3,421 / 3,421
MiFIR transaction report, 30 Sep
> generate --from ledger --regime uk-mifirTRN-00041  BUY 3,200 BARC.L XLON  READYTRN-00042  SELL 1,150 HSBA.L XLON  READYTRN-00043  BUY 8,000 VOD.L XLON  READYTRN-00044  BUY 420 AZN.L XLON  READYTRN-00045  SELL 2,600 LLOY.L XLON  READY…Generated 17:02 from the same ledger as today's NAVRe-keyed by hand: 0

Filed from the same ledger you trade on

Transaction reports come straight from the ledger, the same record that produced the NAV. What you file is what you did: no re-keying, and no second reporting database drifting out of sync.

UK MiFIR transaction reporting is live today, built to take on more jurisdictions as your obligations grow. Independent trade copies are available for compliance and surveillance.

Many mandates, clean walls

Run any number of funds from one deployment. Access is controlled per fund, user, counterparty and portfolio, each with its own configuration and trading limits. Walls are hard by default, and overlap only where you design it.

Deploy multi-tenant, or as a dedicated instance where your governance requires it.

Entitlements
UserFund AFund BFund C
PM, AsiaTRADEVIEWNONE
TraderTRADETRADENONE
OperationsVIEWVIEWVIEW
ComplianceVIEWVIEWVIEW
The Omnitrade app on an iPhone, showing today's transactions

The same platform in your pocket

Web on the desktop, plus native iOS and Android apps with the same trading, portfolio and monitoring. Updates stream live, and your own price feeds can be connected. REST and FIX APIs are there for programmatic access.

Download on the App StoreGet it on Google Play

Built for the scrutiny funds are under

Hosted on AWS with automated backups and point-in-time recovery. The backend scales out across stateless services: the architecture assumes growth rather than negotiating with it.

Security check
TLS 1.2+ in transit[ OK ]
AES-256 at rest[ OK ]
Multi-factor authentication[ OK ]
VPC isolation and security groups[ OK ]
Full audit trail[ OK ]
Automated backups[ OK ]
Point-in-time recovery[ OK ]

Weeks,
not quarters

Onboarding means configuring what is already built. How long it takes mostly comes down to broker setup on your side.

Bespoke integration project  noneImplementation fee  $0