TraderEvolution: broker trading infrastructure, APIs, routing and automation

TraderEvolution provides the operating software behind a brokerage: order handling, positions, accounts, risk and interfaces for clients and staff. It supports exchange-traded instruments and OTC derivatives within the same infrastructure, while preserving their different settlement and lifecycle requirements. Brokers can use its own applications or build an interface around the back end. The supplier describes the business as B2B and liquidity-neutral, so the technology does not itself supply the broker’s capital, custody or bank dealing relationships.[1]

The Client API requires its cluster to be deployed and configured, followed by application registration that supplies a client ID and secret. The developer guide also makes an important parsing distinction: some responses return ordered arrays rather than self-named fields. The /config endpoint supplies the column sequence and names, as well as request periodicity. An integration that hard-codes an assumed field order can therefore misread data even when the request succeeds.[9]

Brokers can selectively enable these integration levels. The presence of embedded charts should therefore not be described as proof that the same broker has completed the directory and account-trading integration.[6]

Public pages describe operational and data control but do not publish full licence or exit terms. That ownership language does not establish copyright transfer or perpetual software rights.[4]

TraderEvolution says it can deploy within five business days after server access is provided. Its white-label page separates that installation step from full go-live, which depends on instruments, liquidity connectivity, regulatory setup and branding. The stack can run on customer-controlled cloud resources, dedicated hardware or virtual machines. That arrangement gives the customer control over the environment while leaving it with an operating responsibility for the infrastructure.[12]

Administrative integration is more extensive than creating a login. The documentation describes API control over account types, groups, trading permissions, leverage, instruments, trading hours and routing rules. It also supports commission plans, markups, swaps, cross-currency calculation inputs and structured reports. These functions allow a CRM or banking system to coordinate onboarding and account configuration, rather than treating the platform as an isolated dealing screen.[8]

The commercial form requests company and project details and says the vendor will reply within one business day. That is an enquiry response expectation; the public page does not set a production outage response or restoration commitment.[16]

TraderEvolution Global Ltd identifies itself as an Irish company with CRO number 627273. Its product is software supplied to brokers, banks and other financial businesses. The company registration and technical support for compliance workflows do not establish a financial-services permission for the customer. The operating broker remains the party determining which instruments, client groups, dealing arrangements and staff authorities its deployment enables.[5]

The Client API uses token authentication, session management and role-based scopes. Back Office account-administration powers differ from trader order entry and post-trade reporting access.[8]

The FAQ places client data on the broker’s servers and identifies the broker as controller. TraderEvolution says it retains technical server access for deployment, configuration and support, while not accessing, processing or retaining client personal data. This is its stated operating boundary, not a verified deployment assessment.[4]

TraderEvolution describes its founding in 2017 and headquarters in Dublin. Roman Nalivayko is CEO and co-founder; Oleksandr Kachur is co-founder and R&D director. Both bring prior PFSOFT experience to the business. The company’s model centres on one evolving trading core, with development arising from multiple clients’ requirements made available across deployments. It accepts formal RFI/RFP processes, mutual NDAs and product demonstrations.[5]

The TRAction connection is a reporting integration rather than a regulator approval of every deployment. Its stated purpose is to move platform data into reporting workflows with less manual extraction. The broker still needs the right reportable population and account/entity data; the integration announcement does not establish successful submissions for a particular firm.[17]

Operator

TraderEvolution Global Ltd

Service scope

Multi-asset order management, risk and routing, branded front ends, operational APIs and broker-controlled automation.

Customer types

Brokers; Banks; Proprietary trading firms; Prime brokers; Technology providers; Neo-brokers

Delivery

On premises; API

Pricing publication

Quote only

Headquarters

Dublin, Ireland

Platforms

TraderEvolution Core; Web Platform and PWA; iOS and Android apps; Back Office; Dealer Terminal; MCP Server

Integrations

Client REST and WebSocket API; BackOffice REST API; FIX 4.4 and DropCopy; TradingView; Kafka; Database replica; External LPs and venues; TRAction

Pricing scope

Published model is a flat monthly licence by deployment tier; monetary rates and complete contractual terms are not public.

Implementation

Vendor deployment and configuration on the broker’s Linux infrastructure, with separate integration, acceptance and migration work.

Support

Direct B2B implementation/support relationship and public developer guides; the enquiry form states a one-business-day reply expectation.

Permissions and regulatory scope

Trading software supplied to financial businesses. Company registration, client financial permissions and the authority granted to APIs or AI tools are separate matters.

Provider metadata checked 20 Oct 2026Source 1Source 5Source 2Source 4Source 16Source 8Source 14Source 17

The current MCP page advertises 31 tools and support for autonomous agents using the Client API. It is an order-capable connection, not merely a research assistant. The public product description does not state that every agent order requires a human approval, and its listed account-query functions should not be expanded into an assumed withdrawal permission. Authority in a deployed agent workflow therefore needs to match the actual enabled tools and account access.[7]

Auto-Invest serves a different automation task. The broker configures schedule choices and plan limits; clients choose instruments, percentage allocations and investment amounts. The back end schedules purchases and handles fractional positions. Clients can pause, change or cancel plans, and the feature is available through mobile apps or a custom Client API interface. This is scheduled portfolio execution rather than an AI system choosing investments on the client’s behalf.[21]

For options, the platform adds a chain, real-time Greeks, a Position Analyzer and a Volatility Lab. A trader can model a paper portfolio and then place real orders from the same workflow. The product page names CQG and Interactive Brokers among exchange-connectivity routes. It also distinguishes multi-leg construction from exchange-supported single-order execution, which matters when a strategy involves several contracts.[20]