OnixS: FIX engines and venue-specific market-access SDKs

The company addresses proprietary trading groups, commodity and energy firms, investment banks, exchanges and independent software vendors. Its role is to supply reusable connectivity components for trading strategies and order or execution management systems. The customer still builds the application and determines how received data and trading messages affect its business workflow.[2]

The general FIX Engine supplies protocol parsing, validation and session functions in C++, Java and the .NET family. Its parser can also be used without the network/session layer, for example inside middleware that consumes or generates FIX messages. Distribution packages include working examples for initiators, acceptors, dialects, repeating groups and storage.[3]

directConnect adds venue-specific protocol implementations. Some use FIX; others use the venue’s binary interface. The catalogue separates market-data handling, order routing, drop copy and trade capture, so a single venue name can represent several separately required components. OnixS describes maintenance against changes in those venue APIs as part of the service.[4]

FIX Analyser is a separate diagnostic tool for log files. It supports text and regular-expression searches, filtering, validation against standard or custom dictionaries, and monitoring of changing logs. It can read FIX messages produced by other engines. This makes it useful for investigating message content and sequence problems across an existing infrastructure.[9]

Platform support is product-specific. The general FIX Engine page lists modern .NET on Linux, Windows and macOS, a distinct Windows .NET Framework 4.8 edition, C++ builds across the main desktop/server operating systems, and Java 1.8 or later. These broad engine options should not be read as a promise that every venue handler exists in every language.[3]

For EDCI, the published lifecycle includes invalidating the local order book and rebuilding it when synchronization or reset events require it. That behaviour matters to downstream risk and surveillance applications: the receiving system needs to distinguish a restored connection from a restored, coherent book.[8]

The downloadable evaluation has a separate contract. It allows internal, non-commercial evaluation for 30 days from availability, unless OnixS agrees an extension in writing. It excludes live production data and services for third parties. Use must stop and copies must be deleted at expiry unless a commercial agreement is in force. The development-cost statement above therefore does not turn the trial into an unrestricted production licence.[11]

The evaluation request asks for the target product or venue, operating system and codebase, business contact details and specific requirements. That selection process helps match a distribution to the intended environment. In the C++ engine, execution requires a valid licence key; the programming guide explains how to set its location and inspect the expiry date.[11][12]

Session recovery needs application decisions as well as a working network connection. The C++ FIX guide explains that a resend request can result in retransmission or a gap-fill message, depending on callbacks and retention settings. Its default gap-recovery mode waits for the missing range; an alternative buffers newer messages until the gap is filled. Integration tests should cover the chosen mode and the application’s treatment of stale orders.[13]

CME requires client systems using Globex iLink order routing or its market-data interfaces to complete AutoCert+ certification. Its testing process requires the appropriate network connection, environment-specific session identifiers and configuration. A handler described as pre-certified can reduce development work, but the customer’s assembled client system still has its own validation and access process.[22]

Supported customers and development partners receive access to OnixS’s issue-tracking system. The public support page directs them to log and follow issues there, with email and telephone alternatives. Product-specific release alerts and issue watch lists provide updates; these channels help teams track fixes and protocol changes against their deployed versions.[16]

Support obligations are set by priority in the Software Services Agreement and matched to customers’ trading windows. The published licensing page also offers contractually defined availability, incident-response and escalation provisions for relevant ICT arrangements. Numerical response commitments need the actual agreement.[10]

CME’s vendor directory lists 24/7 support as included in service terms. That directory description should be read alongside the contracted scope and priorities, rather than used as a universal response-time promise.[21]

The SDK is one part of access to a trading venue. CME’s iLink instructions separately govern registered entities, session permissions and clearing-firm associations. Self-service creation can be enabled by the clearing firm; otherwise individual approval is required, and route-through requests involving several Globex Firm IDs require all affected clearing firms to approve. Buying a library does not itself supply these relationships.[23]

OnixS’s privacy notice states that it does not process customers’ business-level transactions on their behalf. It describes personal-data handling for licensing, invoicing, product development and support. The notice identifies Onix Solutions Limited and its UK data-protection registration; that registration is distinct from a permission to execute or custody investments. This profile concerns the software service.[18]

Companies House records Onix Solutions Limited, number 05416802, as an active private company incorporated on 7 April 2005, with software publishing as its stated business activity. The registered office is in London.[19]

The significant-control register names Wayne Meikle with at least 75% of shares and voting rights and the right to appoint or remove directors. This is the register’s control disclosure; it is not a complete shareholder list.[20]

OnixS’s company history traces its initial FIX engines to 2005, later expansion into non-FIX protocols from 2007, and the directConnect venue packages from 2009. This development explains the current split between general protocol libraries and venue-specific implementations maintained as the venues change.[2]

Operator

Onix Solutions Limited

Service scope

Protocol SDKs for market data, order entry, drop copy and trade capture inside customer trading systems.

Customer types

Proprietary trading firms; Commodity and energy firms; Investment banks; Exchanges; Independent software vendors

Delivery

On premises; API

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

OnixS FIX Engine; directConnect; FIX Analyser

Integrations

CME iLink 3 handler; CME EBS MDP and drop-copy handlers; ICE Binary Order Entry handler; Eurex/Xetra T7 EDCI handler

Pricing scope

Production-deployment subscriptions; a separate restricted 30-day evaluation is available.

Implementation

Product-specific libraries, sample applications and documentation; customer system integration and venue onboarding remain necessary.

Support

Authenticated issue tracking, email and telephone, with service priorities governed by contract.

Permissions and regulatory scope

Software-provider scope. Venue and clearing access permissions are separate from the SDK licence; no financial-services permission is asserted here.

Provider metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 16Source 18Source 19Source 21Source 22Source 23

The ICE Trade Capture Java 3.0.1 release note dated 21 October 2026 records an update for ICE Trade Capture 4.22. Version-specific release notes are useful during maintenance because the commercial product family alone does not identify which protocol update a deployed binary contains.[24]

Older product pages need to be checked for lifecycle status. OnixS explicitly marks the Deutsche Börse Regulatory Reporting Hub FIX handler as end of life. It is therefore excluded from the active integration examples above, even though its information page remains accessible.[25]