What Is Quazar, and Why FIX Connectivity Teams Are Looking at It

The short answer

Quazar is a FIX connectivity platform built by Quod Financial. It sits between FIX-enabled systems and handles three things: routing messages between them, translating between different FIX dialects and versions, and managing the sessions themselves. Counterparties running incompatible FIX implementations can connect through it without custom integration work on either side. Access is free for buy-side firms up to 10 connections, and sell-side deployments run on a fixed price, managed for the client either on-premise or cloud-hosted.

Why the FIX layer is being looked at again

For most of the last decade, FIX connectivity was the part of the stack nobody touched. It worked, it was paid for, and the person who understood it was still in the building.

That is changing for a scheduling reason. The UK moves to a T+1 settlement cycle on 11 October 2027, and the UK Accelerated Settlement Taskforce’s Q1 2026 market readiness survey, reported in June 2026, found 83% of firms actively involved in T+1 preparations, up from 66% in Q3 2025. On the buy side, 57% of respondents were yet to begin development work.

Those programmes touch allocation and confirmation flows, which means they touch the messaging layer. A bridge that has run untouched for years gets opened properly, usually for the first time since it was installed, and the questions that surface are the ones nobody had to answer while it was quietly working: how many bilateral integrations are we actually maintaining, what happens when a counterparty changes its dialect, and what does adding the next connection cost us.

That is the context in which teams start reading up on fix engine vendors. Quazar is one of the newer names in that conversation.

What Quazar actually does

Quazar describes itself as an AI-native FIX Fabric: “a high-performance platform for routing, transforming, and managing FIX connectivity”, positioned as “the FIX fabric that works for every counterparty”.

Architecturally it is a hub. Internal systems connect to the hub, and the hub holds the sessions with counterparties. That is what removes the need for bilateral integration work on both sides of every link.

Published throughput figures are 2,500 messages per second with persistence and 20,000 messages per second for market data, on a core built in C++.

Three of those lines carry most of the practical weight.

The transformation layer addresses what actually consumes migration timelines. Counterparties implement FIX with their own tag choices, their own repeating group conventions and their own leftovers from earlier versions, and those differences are usually documented nowhere except in the behaviour of the system being replaced. A configurable mapping layer and a codebase extended by hand produce the same result for very different amounts of work.

The absence of a hard session limit matters commercially as much as technically. Where session ceilings or session-tiered licensing exist, they shape architecture: teams batch connections or avoid opening them, and a technical design ends up driven by a pricing table. Designing the ceiling out removes that constraint from the conversation.

Fault isolation is the line operations teams read first. Self-contained hubs mean one counterparty sending something malformed stays one counterparty’s problem, rather than becoming a desk-wide incident. Route tracing in the runtime dashboards is the other half of that: the team living with the platform day to day needs to see where a message went, not just that it left.

How access works

This is where Quazar departs most clearly from convention in FIX connectivity.

Buy-side firms get the platform free to 10 connections, and the stated scope is the full platform: routing, transformation, session management, monitoring and templates, rather than a feature-limited trial. A pilot on real traffic does not need a procurement cycle behind it.

Sell-side and broker deployments run on a fixed price with no plug-in cost, and the platform states that it does not charge for FIX-to-FIX connections. Operationally it is run for you either way: upgrades, fixes and template updates are handled by the vendor, on-premise or cloud-hosted, with routing managed in the cloud across parts of the network. Pricing structure deserves attention here, because per-connection models compound: they turn every new broker, venue or internal system into a commercial conversation rather than a configuration change, and five years of that behaviour costs more than the licence line ever suggests.

There is also a knock-on effect worth understanding. In the company’s own words, “free buy-side access means firms on both sides of a flow can connect Quazar to Quazar directly, removing fixed-network fees entirely”.

Who built it

Quazar is a Quod Financial product. Quod describes itself as an owner-managed trading technology company with over two decades of FIX connectivity and trading systems experience. Its history dates to an innovation lab opened in 2004, and in 2008 it launched what it describes as the first data-driven smart order routing and algo trading solution. It has worked with banks, brokers, exchanges and hedge funds for over 15 years, from offices in London, Paris, Lille, Gdansk, Toronto, New York, Hong Kong, Dubai, Singapore and India.

Its core business is multi-asset OMS and EMS technology across equities, derivatives, FX, fixed income and digital assets. The FIX connectivity experience behind Quazar therefore comes from running that layer in production for other people’s order flow, rather than from a standing start. Quazar itself is proprietary software, built and maintained by Quod Financial, and is not open source.

Who it is for

Two profiles fit clearly.

A buy-side firm running a multi broker trading platform setup holds the sessions rather than the broker. Ten brokers means ten sessions, ten certifications, ten sets of dialect quirks and ten upgrade calendars that do not align. Add a prime, a custodian and an OMS vendor, and connectivity stops being a project and becomes a permanent maintenance function. A hub turns adding a broker into configuration.

A sell-side firm or broker with counterparties at scale has the mirror image of that problem, plus a cost base that grows with connection count under most pricing models. Fixed pricing changes the shape of that curve.

Is there a best FIX engine?

Not in the abstract. FIX products are built for different jobs, and the honest way to read Quazar is against the constraints it targets: many counterparties, incompatible dialects, session counts that keep growing, and a cost base that should not scale with the number of connections.

If the requirement is instead a library embedded inside your own application, with a latency budget measured in microseconds and no additional network hop tolerated, that is a different category of product entirely. Being clear about which of the two problems you actually have is worth more than any feature comparison.

Frequently asked questions

What is Quazar?

Quazar is a FIX connectivity platform built by Quod Financial, described as an AI-native FIX Fabric for routing, transforming and managing FIX connectivity. It provides FIX-to-FIX routing with merge and split, a multi-session engine with no hard session limit by design, and a transformation and mapping layer for dialect and version differences. It is deployed as a hub, or several hubs interconnected over native FIX, on-premise or cloud-hosted. Buy-side access is free to 10 connections; sell-side runs on a fixed price.

Who is Quazar built by?

Quod Financial, which describes itself as an owner-managed trading technology company with over two decades of FIX connectivity and trading systems experience. Its history dates to an innovation lab opened in 2004 and, in 2008, what it describes as the first data-driven smart order routing and algo trading solution. Its core business is multi-asset OMS and EMS technology across equities, derivatives, FX, fixed income and digital assets. It operates from offices including London, Paris, New York, Hong Kong and Singapore.

Is Quazar free?

Free to 10 connections for buy-side firms, with the full platform included: routing, transformation, session management, monitoring and templates. Sell-side and broker deployments run on a fixed price with no plug-in cost, and the platform states that it does not charge for FIX-to-FIX connections. Because buy-side access is free, firms on both sides of a flow can also connect Quazar to Quazar directly.

Is Quazar open source?

No. It is proprietary software, built and maintained by Quod Financial.

What is a FIX fabric, as opposed to a FIX engine?

An engine is a library linked into an application, which then owns sessions, sequencing and recovery itself. A fabric or hub is a separate layer sitting between systems and counterparties, holding the sessions and translating between dialects and versions on their behalf. Quazar is the second of those: internal systems connect once, and counterparty differences are handled in the mapping layer rather than in application code.

How fast is Quazar?

Published figures are 2,500 messages per second with persistence and 20,000 messages per second for market data, on a core built in C++. Throughput is rarely the deciding factor in a FIX platform choice, though, because it is easy to verify. Failure behaviour is the harder question: what happens on session recovery mid-sequence, and whether one misbehaving counterparty can affect the others.

What should be tested before committing to a FIX platform?

Replay real production traffic, including the malformed and non-standard messages, rather than synthetic tests. Check behaviour on session recovery mid-sequence, confirm what happens to the other connections when one counterparty misbehaves, and run dialect transformation against your two most awkward counterparties first rather than the two easiest. The easy ones tell you nothing about whether the migration is a quarter or a year.