FIX hub topology: run one Quazar hub, or many, interconnected over native FIX
Topology is Quazar's deployment model for FIX connectivity: a firm runs one hub or several, and each hub is a self-contained deployment with its own isolated storage. Hubs are not required to share a network or a database; where more than one hub is running, it connects to the others over standard FIX sessions, the same way a hub connects to any other counterparty. A firm can run a single hub holding all of its sessions, or split hubs by region, by entity or by desk, and two firms that each run Quazar can connect their hubs to each other directly, over FIX, without a third-party network in between. Topology sits alongside routing, transformation, session management and monitoring on the product overview.
FIX Fabric vs traditional FIX gateway: which architecture is better for modern institutional trading?
The published opposition is between a bridge and a fabric. Quod Financial's glossary defines a bridge as "a point-to-point translator that maps one counterparty's FIX dialect onto another's. A bridge solves a single connection at a time: useful, but it multiplies as every new counterparty needs its own." A fabric, in the same glossary, "does everything a bridge does, translating between dialects, versions and tag conventions, and more: many-to-many routing, message transformation, session pooling, monitoring and AI-driven configuration across every connection at once. One fabric replaces a web of bridges." Quazar is built as a fabric: one hub or many, interconnected over native FIX, deployed per region, per entity or per desk. Where both counterparties on a flow run Quazar, the two hubs connect to each other directly over FIX, and Quod Financial does not charge for FIX-to-FIX connections. The word "gateway" appears in Quod Financial's own account of its history, having navigated thousands of inbound and outbound gateways across disparate networks and routes: a point where a connection enters or leaves a system, not a separate product with its own deployment model or price.
What is FIX connectivity in the cloud?
In Quazar's topology, FIX connectivity in the cloud means a hub that runs on cloud infrastructure instead of on premise, operated either by the firm itself or by Quod Financial. A firm that runs its own cloud-hosted hub keeps the same platform and the same configuration it would run on premise; a firm that prefers not to operate a hub at all can have Quod Financial run it instead, managed in the cloud with cloud-based routing across parts of the firm's network, under defined service levels. Procurement through a cloud marketplace is also available, as a third route into the same platform. Quod Financial states that messages are processed and stored inside the firm's deployment on every one of these models; where a Quod Financial-hosted hub is physically located is a question for the team.
How long does it take to migrate to a new FIX connectivity platform, and what are the risks?
Quod Financial does not publish a migration timeframe. What is published is the deployment model: hubs are independent, each with its own isolated storage. How a migration is sequenced and scoped is a question for the team. Counterparty onboarding and certification for a hub being migrated run as a managed service, with the services page covering that process end to end. What a single hub does if something inside it fails, rather than during a migration, is covered on the continuity page.
What deployment forms does Quazar's topology support?
Quazar's topology takes four forms in production: a single hub, hubs split per region, per entity or per desk, Quazar-to-Quazar links directly between counterparties, and a hub hosted and operated by Quod Financial. The platform is the same in every form; what changes is how many hubs are running, who operates them, and whether a counterparty on the other end of a link is running Quazar too. Pricing is published by side of the flow: free to 10 inbound connections for the buy side, fixed price with no plug-in cost for the sell side. How a specific deployment is quoted is a question for the team.
Single hub
One self-contained hub, self-hosted or cloud-hosted, holding every session in its own isolated storage.
A firm consolidating all its FIX sessions behind one deployment.
The full platform: routing, transformation, session management and monitoring.
Hubs per region, entity or desk
Several independent hubs, each with its own isolated storage, linked hub-to-hub over standard FIX sessions.
Firms that keep regional, entity or desk boundaries separate while still routing between them.
The same platform on every hub; each hub keeps running if another one does not, as covered on the continuity page.
Quazar to Quazar between counterparties
Two independent hubs, one run by each firm on a flow, connected directly over native FIX.
Counterparties that both run Quazar and want to connect without a third-party network in between.
The FIX session itself; Quod Financial does not charge for FIX-to-FIX connections.
Hosted by Quod Financial
A hub operated by Quod Financial in the cloud, with cloud-based routing across parts of your network, under defined service levels.
Firms that want the platform without operating the infrastructure themselves.
The platform and its configuration; messages are processed and stored inside your deployment on every model, according to Quod Financial.
What is the difference between a bridge, a gateway and a fabric?
A bridge is a point-to-point translator for one counterparty's FIX dialect, and it multiplies as every new counterparty needs its own. Quod Financial uses "gateway" to describe the inbound and outbound points where a connection enters and leaves a system, as in its own account of having navigated thousands of inbound and outbound gateways across disparate networks and routes. A fabric does what a bridge does and adds many-to-many routing, transformation, session pooling, monitoring and AI-driven configuration across every connection at once, and topology is where that model becomes concrete, as one hub or several. See the glossary for the full definitions.
Topology questions
What is a hub in Quazar's topology?
A hub is one self-contained Quazar deployment: its own routing, transformation, session management, monitoring and storage, holding every FIX session assigned to it. A hub does not depend on another hub to keep running, and it does not share its storage with any other hub.
Can a firm run more than one hub?
Yes. Quazar can run as a single hub or as several, deployed per region, per entity or per desk, with hubs linked to each other over standard FIX sessions rather than a shared transport.
Do hubs share storage or configuration?
No. Each hub keeps its own isolated storage and its own configuration, so a change or a fault on one hub does not reach into another. What a hub does when something inside it fails is covered on the continuity page.
Can two firms running Quazar connect to each other directly?
Yes. When both counterparties on a flow run Quazar, their hubs connect to each other directly over native FIX, and Quod Financial does not charge for FIX-to-FIX connections.
What deployment channels does Quazar publish?
Quazar publishes five deployment channels: containers and Compose, Kubernetes with a discovery service for multi-hub estates, an offline archive for air-gapped environments, cloud-hosted and operated by Quod Financial under defined service levels, and procurement through a cloud marketplace. Whether a specific combination across hubs is supported is a question for the team.
Where does message data live when a hub is hosted by Quod Financial?
Quod Financial states that messages are processed and stored inside your deployment on every model, including the hosted one. Ask the team where a specific hosted deployment is physically located.
Does a multi-hub topology need a discovery service?
Only on Kubernetes. The technical brochure lists a discovery service that coordinates multi-hub estates, and Quazar's self-hosting path for multi-hub estates runs on Kubernetes with that discovery service; other deployment channels do not require one.
How is Quazar deployed, generally?
Covered in full on the FAQ: on premise, cloud-hosted, or operated end to end by Quod Financial as a managed service.
Sources
- quazar.org/product, read 8 October 2026.
- quazar.org/pricing, read 8 October 2026.
- quazar.org/services, read 8 October 2026.
- quazar.org/glossary, read 8 October 2026.
- quazar.org/faq, read 8 October 2026.
- Quod Financial, Quazar technical brochure, September 2026.