Orchestrade: cross-asset trading, risk and treasury operations

Orchestrade brings trading records, valuation, risk and operational processing into a cross-asset platform. Financial institutions and energy businesses use it to manage portfolios and trading workflows across business lines. Its operating proposition is a shared system of records and processes that can be extended as products change.[1]

For hedge funds, the documented risk measures include option Greeks, DV01, CS01, value at risk and projected cash flows. Portfolio views can be organized by fund, strategy, trader, geography or currency. Middle-office processing covers confirmations, payment schedules, corporate actions and fee schedules; an integrated general ledger supports funds doing shadow accounting. Different stakeholders can use separate curves and pricers within the same platform.[3]

Treasury coverage includes repos, securities lending, inter-entity funding, deposits and loans. Cash and maturity ladders support liquidity analysis, while collateral workflows include eligibility, substitution, allocation and margin calls. Accounting integration covers accruals, mark-to-market and profit-and-loss posting under IFRS or local GAAP. These are treasury-system functions operated for an institution; the software supplier is not the source of the institution’s funding.[6]

Orchestrade describes a hub-and-spoke approach connecting execution-management systems, order-management systems and bank platforms. This lets a fund retain execution relationships while bringing trade information into its portfolio and risk workflow. Connectivity is therefore distinct from supplying liquidity or being the executing broker.[3]

The public commercial route is a demonstration and business enquiry. The inspected pages do not provide a numeric licence tariff, implementation fee, minimum contract value or price per user. A scoped proposal is needed to establish the cost of the chosen deployment and service package.[12]

A full platform replacement and a single-desk component are both supported use cases. A cost comparison consequently needs the same scope: modules, interfaces, migration work, hosting and ongoing operational responsibility. The bank page’s lower-cost claims do not provide the inputs for a reproducible savings calculation.[2]

The technical page lists deployments on AWS, Google Cloud, Microsoft Azure, private cloud and on-premises. The stack includes .NET/C#, PostgreSQL or SQL Server, optional MongoDB, RabbitMQ and containerized components. These choices affect the implementation architecture and which infrastructure the customer or service provider operates.[5]

Orchestrade also works with technology, infrastructure and systems-integration partners. The project therefore needs an explicit division of responsibility for interfaces, environments, migration and production operation; a partner logo by itself does not define that division.[8]

The AFL account illustrates how implementation can include changing workflows as well as installing software: it describes loan acquisition and hedging, behavioural assumptions in asset-liability management, production forecasts and FR-GAAP/IFRS9 metrics. The work was delivered remotely during the pandemic. That case establishes one delivered project’s scope, not a standard timetable for every customer.[9]

Existing customers are directed to the separate Client Support portal. Public contact information identifies offices across the Americas, Europe and Asia, but does not set a universal support window, severity-response schedule or recovery-time commitment. Those terms need to be agreed for the contracted service.[12]

Orchestrade’s website terms identify Orchestrade, Inc. as the operator and state that it is not regulated by a financial authority. The terms also exclude investment advice and personal recommendations. This is the supplier’s published description of its website and business boundary; trading, risk or reporting functionality does not itself confer permissions on a customer institution.[13]

The same terms govern the public website and information supplied through it. Their availability and liability provisions should not be substituted for a negotiated software licence, managed-service agreement or production service-level schedule. Those commercial documents determine the contracted delivery obligations.[13]

Orchestrade dates its foundation to 2009 and describes San Mateo as its base. Its current product scope spans financial institutions and energy firms rather than a retail trading account offered under the Orchestrade name.[1]

The entity named in the purchase agreement should be checked against the relevant company details. The UK company record is corporate-registration evidence; it is not evidence of investment-services authorisation.[15]

Operator

Orchestrade, Inc. and regional group entities

Service scope

Cross-asset trading, portfolio, treasury, risk and operational software.

Customer types

Banks; Hedge funds; Energy and commodity businesses

Delivery

Hosted; On premises; API; Managed service

Pricing publication

Not disclosed

Headquarters

San Mateo, United States

Pricing scope

No numeric commercial tariff in the inspected public material.

Implementation

Component or broader deployments, with client-specific interfaces and migration.

Support

Client Support portal and regional offices; contractual service levels are not published.

Permissions and regulatory scope

Software supplier; website terms state no financial-authority regulation.

Provider metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 9Source 12Source 14Source 13

The current technology page still labels its web portal as in development. A requirement for browser-based operation should therefore be agreed against the delivered interface, rather than inferred from the availability of APIs or cloud deployment.[5]

The treasury material also distinguishes existing functions from further regulatory alignment. It describes native SFTR XML/ISO 20022 feeds, while presenting full liquidity coverage ratio and net stable funding ratio alignment as a direction being prepared for. A procurement specification should identify the actual reports, calculations and controls required, rather than treating the broad compliance language as complete regulatory coverage.[6]