Deploy and buy
Your infrastructure, or a dedicated instance we run for you
Qubit is not a shared cloud service. Every deployment is single-tenant: one installation, one client, one set of databases. You can run it yourself in your data center or cloud account, or have us operate a dedicated instance for you. Either way, your orders, positions and client records live in databases that belong to you.
Two ways to run Qubit
Self-hosted
Qubit runs in your environment: your data center, your private cloud or your account with a public cloud provider. Your team operates it with our runbooks, and we ship releases and support.
Best forBanks, brokers, exchanges and funds with an infrastructure team, strict data residency rules or a policy against third-party hosting.
Dedicated managed instance
A separate installation used only by you, operated by our engineers. It runs in a cloud account we manage for you or in your own account, in the region you choose.
Best forFintechs, OTC desks and smaller brokers who want the control of a dedicated system without staffing a trading operations team.
You can start on a dedicated managed instance and move to self-hosted later. The software, data model and APIs are the same.
Architecture overview
One data model, one event log
Qubit is a set of services that share one data model and one event log. The component names below are logical; the deployment guide for each release lists the exact services and versions.
Access layer
- FIX 4.4 gateway, REST API and WebSocket API for clients, front ends and strategies
- Trader and operations interface, and the admin console
- Authentication through your identity provider, with role-based permissions on every request
Trading core
- Order management: the order lifecycle and state machine, the single source of truth for every order
- Pre-trade risk: limits and checks that every order passes before it reaches a venue
- Execution gateway: venue adapters that turn orders into venue calls and venue events back into order state
- Smart order routing, execution algorithms, RFQ and pricing services, where licensed
Books and records
- Position and balance ledger, updated on every fill
- Append-only event log and audit trail
- Post-trade services: reconciliation, treasury and settlement, reporting
Data
- Market data service: normalized prices, trades and depth from your venues
- Transactional database for orders, positions and reference data
- Time-series storage for market data and analytics
Edges
- Outbound connections to the venues, liquidity providers, custodians, data vendors and compliance partners you configure. Nothing else.
Compare
Same software, two operating models
| Item | Self-hosted | Dedicated managed instance |
|---|---|---|
| Where it runs | Your data center, your private cloud or your account with a public cloud provider | A cloud account we manage for you or your own account, in the region you choose |
| Who operates it | Your team, with our runbooks. We ship releases and support. | Our engineers, per your support tier |
| Tenancy | Single-tenant: one installation, one client, one set of databases | Single-tenant: a separate installation used only by you |
| Where data lives | All Qubit data stays in your environment | In the region you choose, in a cloud account dedicated to you |
| Upgrades | You run the upgrade in your own change window | We run the upgrade in a window agreed with you |
| Access to your systems | Support cases carry only what you choose to send us | Our engineers access it through audited, role-based access for operations and support |
| Network | Outbound traffic only to the venues, liquidity providers, custodians, data vendors and compliance partners you configure | Outbound traffic only to the venues, liquidity providers, custodians, data vendors and compliance partners you configure |
| Support model | Releases, runbooks and support at the tier you choose | Managed hosting requires the Extended or Critical support tier |
| Best for | Banks, brokers, exchanges and funds with an infrastructure team, strict data residency rules or a policy against third-party hosting | Fintechs, OTC desks and smaller brokers who want the control of a dedicated system without staffing a trading operations team |
Packaging
How it is packaged
- a.Container images for every service, signed and published with a software bill of materials
- b.A Helm chart for Kubernetes deployments, and a Docker Compose setup for evaluation and test environments
- c.Configuration as files and environment variables you keep in your own version control
- d.Database migrations shipped with each release and run as part of the upgrade
- e.A license key that validates offline. Qubit does not need to contact us to run.
Responsibilities
Who does what
| Area | Self-hosted: you | Self-hosted: Qubit | Managed instance: you | Managed instance: Qubit |
|---|---|---|---|---|
| Infrastructure (compute, network, storage) | Provide and operate | Publish sizing guidance | Choose region and account | Provision and operate |
| Installing and upgrading Qubit | Run the upgrade in your window | Ship releases, notes and migrations | Approve the upgrade window | Run the upgrade |
| Monitoring and alerting | Operate, using our dashboards and alert rules | Provide dashboards, alert rules and runbooks | Receive incident notices | Operate around the clock, per your support tier |
| Backups and disaster recovery | Operate and test | Document procedures | Agree recovery targets | Operate and test |
| Identity, SSO and user access | Own | Support integration | Own | Configure for you |
| Venue, LP and custodian accounts and API keys | Own | None | Own | None |
| Configuration of limits, fees and routing | Own | Advise | Own | Advise |
| Application defects | Report | Fix and ship | Report | Fix and ship |
In both models, you hold the venue accounts and the client relationships. Qubit never holds client assets.
Rollout
From scoping to go-live
Scope, delivery stages and acceptance criteria go into the contract, not into a slide. Dates are agreed per deployment.
- 01
Scoping
Architecture, security and integration with your engineers and risk team.
- 02
Environment
We send the sizing guide and walk through an installation plan with your team.
- 03
Connectivity
Venue connectivity confirmation and configuration of limits, fees and routing.
- 04
UAT
Testing against the acceptance criteria in your written proposal.
- 05
Go-live
Training, then production in the change window you choose.
Resilience
High availability and disaster recovery
- No single point of failure in the trading path. Services in the order path run with redundant instances, and the order management service fails over to a standby that rebuilds state from the event log.
- State you can rebuild. Every order, fill and position change is written to an append-only event log before it is acknowledged. After a restart, Qubit replays the log, then queries each venue for open orders, fills and balances to close any gap from the time it was down.
- Venue disconnects are routine, not exceptional. Adapters reconnect, resubscribe and resynchronize order state. Orders whose status is uncertain are flagged for review rather than guessed.
- Idempotent order entry. A client order ID or idempotency key means a retried request never creates a second order.
- Backups and a second site. Databases and the event log are backed up on a schedule you set, and the deployment can be replicated to a second region or data center. Recovery point and recovery time objectives are agreed per deployment and tested, not quoted from a brochure.
Upgrades
- Releases are versioned. Each one ships with release notes, a list of changes to APIs and configuration, database migrations and a rollback procedure.
- You choose when to upgrade. Self-hosted clients run upgrades in their own change window; for managed instances we agree the window with you.
- Our standard position is to support the current release and the one before it. Your support agreement states the exact policy.
- API changes follow the versioning rules on our Developers page, so an upgrade does not break your integrations without notice.
- Security fixes are released separately from feature releases when urgency requires it, with a clear severity rating.
Data residency
- Self-hosted: all Qubit data stays in your environment. The only outbound traffic is to the venues, liquidity providers, custodians, data vendors and compliance partners you configure. Support cases carry only what you choose to send us.
- Managed instance: your instance runs in the region you choose, in a cloud account dedicated to you. Our engineers access it through audited, role-based access for operations and support.
- Usage reporting: where your contract includes it, usage reporting sends aggregate counts per module. It never includes orders, client data or positions, and your team can inspect each report before it leaves your network.
In both models, you hold the venue accounts and the client relationships. Qubit never holds client assets.
FAQ
Questions we get asked
Can we run Qubit on our own infrastructure?
Yes. Self-hosting is the default model. Qubit installs in your data center or cloud account, and your data and venue keys stay there. If you would rather not operate it, we can run a dedicated single-tenant instance for you.
Can we start on a managed instance and move to self-hosted later?
Yes. You can start on a dedicated managed instance and move to self-hosted later. The software, data model and APIs are the same.
Does Qubit need to contact you to run?
No. The license key validates offline. Qubit does not need to contact us to run.
What leaves our network in a self-hosted deployment?
All Qubit data stays in your environment. The only outbound traffic is to the venues, liquidity providers, custodians, data vendors and compliance partners you configure. Support cases carry only what you choose to send us.
Who operates the system in the managed model?
Our engineers operate a separate installation used only by you, in a cloud account we manage for you or in your own account, in the region you choose. In both models, you hold the venue accounts and the client relationships.
Talk to an engineer about your environment
Tell us where Qubit would run and what your network and security rules are. We will send the sizing guide and walk through an installation plan with your team.