Rapid Addition: FIX connectivity, trading workflows and operational control

Rapid Addition provides the messaging and workflow layer through which banks, brokers and trading venues connect counterparties, route orders and automate trading processes. Customers can place their own pricing, execution and risk logic on the framework. The service is particularly relevant where a business must coordinate several existing systems or FIX connections without rebuilding the entire trading application.[1][2]

The distinction between a FIX engine and the whole platform matters commercially and operationally. The engine handles the protocol connection; RA Platform adds configurable workflows and operational controls, including order cancellation and kill-switch functions. A project needs to specify which components and controls are actually deployed.[2]

RA FIX Engine is offered in Java and .NET. The documented repository editor accommodates custom fields and message/session parameters, while FIXT supports application-layer versioning. Native TLS/SSL is specified for Java; TLS/SSL proxies are supported for both versions. Asynchronous I/O allows an application to isolate slow consumers and apply measures such as quote conflation.[5]

The catalogue establishes available adapter routes; the selected venue protocol, message dictionary and counterparty rules still define the production connection. Rapid Addition also offers bespoke adapter development through its Open API.[7]

Counterparty onboarding uses a web interface to configure routing and client rules of engagement. Several FIX versions and custom tags can coexist, with transformations between the counterparty and the OMS or execution system. The monitoring workflow distinguishes rejects, partial fills and child-order states. These are useful operational distinctions when an order traverses more than one processing system.[8]

Customer-defined functionality can be built through the web interface or Java API. The documented use cases include routing rules, proprietary algorithms and pre-trade risk parameters. Rapid Addition describes customers as retaining control of this business logic and their intellectual property; the framework supplies integration and deployment tools around it.[10]

The reviewed public pages supply no standard monetary tariff, minimum subscription or universal per-message fee. Rapid Addition’s own discussion of FIX-engine cost explicitly avoids a dollar price and distinguishes licence cost from implementation, support, upgrades and later changes. A commercial proposal must therefore identify the selected products and service scope before the total cost can be established.[13]

The public website terms govern browsing and website materials. They are not the production software agreement. Renewal notice, termination rights, source-code or configuration handover, retained message history and paid exit assistance remain matters for the signed licence and service schedules; the reviewed public terms do not set those customer entitlements.[15]

RA Hub can add a discrete function or replace legacy components in stages. Its published resilience design includes high-availability configuration and message persistence, while virtual mode, automated testing and version control support changes before production use. These are architectural capabilities; recovery objectives and topology need to match the actual deployment.[3]

The browser-based RA Web UI removes the need for a separate desktop installation for configuration and monitoring. Its launch documentation describes visual workflows, code assistance, integrated Git and a Kubernetes backend, with several regional platforms manageable from one interface. This is an administrative frontend; the underlying messaging and execution deployment remains a separate architectural choice.[20]

FastLane places selected calculations in FPGA hardware while offloading functions outside the latency-critical path to software. Operators can change price limits and restricted-instrument lists intraday through its web configuration. Asynchronous replication to RA Hub provides a software continuity route if hardware fails. Because replication is asynchronous, the publication is not a promise of synchronous, zero-loss failover.[6]

The support team is the central route for non-commercial questions, incident handling and technical documentation. Each customer has an account manager; the Statement of Service specifies the detailed support model. Public business-hours coverage does not identify a universal timezone or severity-based response clock.[12]

RA Monitor supports investigation from a consolidated activity view into child-order message trees and full FIX logs. It can store and search trade messages, calculate custom fields and send configurable alerts. Network agents add infrastructure and latency visibility, while connections to external databases or visualisation tools extend analysis of live and historical records. This helps separate a trading-state issue from a connectivity or performance problem.[4]

The supplied technology can apply customer-defined rules to orders and messages. Configuration therefore carries active operating authority: routing, algorithms and risk parameters can change trading behaviour. The customer determines those policies and remains the operator of its financial workflow. This profile covers software and services supplied to financial institutions, rather than a Rapid Addition execution counterparty or custody account.[10]

The interoperability page describes standardised, enriched data as a foundation for AI-driven insights and analytics. That establishes a data-enablement role. It does not document a general-purpose autonomous AI agent with authority to place orders or alter risk limits; any customer-built model would need its own integration and control specification.[9]

The privacy notice, last updated 1 April 2024, explicitly defines its service as the Rapid Addition website. It covers website personal and usage data. Production-message access, customer-data processing, hosting location, operational retention and deletion at contract end need to be addressed in the customer agreement and any applicable processing schedule. Website privacy language cannot resolve those deployment-specific terms.[16]

Rapid Addition dates its founding to 2003 and names Kevin Houstoun as founder and executive chairman and Mike Powell as chief executive. Its history records the 2016 acquisition of DET Tech and an FPGA collaboration with Fraunhofer HHI, explaining how the business expanded from FIX connectivity into a broader middleware platform.[19]

Companies House lists Rapid Addition Limited, number 04942863, as active, incorporated on 24 October 2003. Its current registered office is 20–22 Wenlock Road, London. The website terms still show Hyde Park House, while the current contact footer uses 95 Chancery Lane; these addresses should be reconciled in contractual notices.[17][15][14]

The active corporate control entry names Rapid Addition Holdings Limited, number 09640186, with at least 75% of shares and voting rights and the right to appoint or remove directors. This identifies the immediate controlling company, rather than a complete account of ultimate ownership.[18]

Operator

Rapid Addition Limited

Service scope

Institutional messaging, order-routing, customer-defined workflows and trading-system monitoring.

Customer types

Banks; Brokers; Trading venues

Delivery

On premises; Hosted; Hybrid; API

Pricing publication

Quote only

Platforms

RA Platform; RA Hub; RA Monitor; RA FIX Engine; RA FastLane

Integrations

FIX; Java / .NET; Kafka; JDBC; Bloomberg B-PIPE; LSEG Elektron

Pricing scope

Product subscriptions and separately scoped professional services; monetary rates require a proposal.

Implementation

Modular deployment with virtual testing, replay, repository controls and staged migration.

Support

Business-hours support Monday–Friday; detailed coverage is in the customer Statement of Service.

Permissions and regulatory scope

Technology supplier; financial institutions operate the configured trading and risk workflows.

Provider metadata checked 20 Oct 2026Source 1Source 15Source 17Source 3Source 2Source 7Source 5Source 13Source 11Source 12Source 10

A named deployment provides a more concrete migration example. Rapid Addition reports that LSEG completed an Azure migration of Autex Trade Route using RA technology, and subsequently established a Singapore hub in four weeks. These are customer-project results reported by the supplier, rather than a standard implementation deadline. They illustrate the use of RA as infrastructure beneath another company’s connectivity service.[21]

Wedbush’s 26 June 2025 announcement describes adoption of RA technology across trading, risk management and post-trade processes, connecting front and middle-office workflows. Further expansion into additional asset classes and workflows was described as a potential next step. The distinction preserves the documented deployment scope while showing how the middleware can extend beyond order entry.[22]

Long-term portability involves more than an API connection. RA Monitor exposes messages and logs for investigation, and the migration tooling provides repository-based configuration history and rollback. Those functions support technical handover planning, but a documented forensic view or rollback mechanism is not itself a contractual export format, post-termination access period or assistance entitlement.[4][11]