Managed infrastructure. A separate line of business from our platform, and it does not require you to adopt it.
oneZero hosting
We host and operate your oneZero deployment — Hub, bridge and the sessions around it — including the routing configuration and the day-to-day upkeep.
Who this is for
Brokers who have chosen oneZero for aggregation and routing and want it run by someone who has configured it before, rather than learning it during a live incident.
Licence position
Your oneZero agreement is yours. We operate the deployment under it and hold no licence of our own over it.
What is included.
- 01
Provisioning and configuration of the oneZero components your agreement covers.
- 02
Colocated hosting, chosen for proximity to your liquidity providers rather than for our convenience.
- 03
FIX session setup and maintenance to each provider, including credential rotation.
- 04
Routing and aggregation configuration, changed on your instruction and recorded.
- 05
Monitoring of sessions, price continuity and rejects, alerting to us.
- 06
Backups of configuration, with the ability to restore a known-good routing state.
The useful half. Anyone can list what is included.
What is not included.
Stated up front so you are not finding it out during an incident. If something you need is on this list, say so before you sign rather than after.
- The oneZero licence and your commercial relationship with them.
- Liquidity provider agreements and credit relationships.
- Your risk decisions. We implement the routing you specify; which flow goes where is yours.
Structure, not numbers. The targets are figures and none is verified yet.
How support is structured.
Response targets are numbers, and no number appears on this site until it carries its definition and its measurement. What can be stated now is the shape: what starts the clock, how severity is decided, and what counts as finished.
- What starts the clock
- A ticket raised through the support channel, or an alert from our own monitoring — whichever comes first. If we detect it before you report it, the clock started when the monitor fired, not when you noticed.
- Severity, set by impact not by opinion
- Severity is defined by what a client cannot do: trade, deposit, withdraw, or log in. It is not negotiated per ticket, and it is not lowered because a workaround exists.
- Escalation path
- One queue, and it is engineers rather than a first line reading a script. Escalation is by elapsed time against severity, automatic, and does not require you to ask.
- What counts as resolved
- Service restored and cause identified are two separate states, and the ticket does not close on the first one. You get the cause in writing.
How a migration runs.
- 01
Inventory
Providers, sessions, current routing rules and where they are documented — often nowhere, which is itself the finding.
- 02
Target configuration
Routing and aggregation written down explicitly before it is built.
- 03
Session build
FIX sessions established and validated against each provider in test.
- 04
Shadow running
The new configuration observes real prices without routing real flow.
- 05
Staged cutover
Flow moved by group, with the previous configuration one instruction away.
- 06
Handover
Configuration documented, monitoring visible to you, escalation contacts set.
Technical detail.
| Components | Hub, bridge and FIX sessions as your agreement covers. |
|---|---|
| Colocation | Chosen for proximity to your providers. |
| Configuration | Version-controlled, restorable to a known-good state. |
| Monitoring | Sessions, price continuity, reject rates. |
Pricing.
Figures not published yet. Setup and monthly pricing for this service is a commercial decision that has not been made, and inventing a “from” number would be the first thing on this page that was not true. What is settled is what you get for it — the scope above is the complete list, and the boundary section is the complete exclusion list. When figures exist they go through the same gate as every other number on this site.
Questions that come up.
- Will you change our routing without asking?
- No. Routing changes on your instruction, and every change is recorded with who asked and when. The only exception is disabling a session that is actively feeding bad prices, which we will do and tell you about immediately.
- Can you add a liquidity provider for us?
- We can build and test the session. The agreement and the credit arrangement are between you and them — we are not a party to it and would not want to be.
- Do you see our flow?
- Operating the deployment means we can see it. What we do not do is use it, aggregate it, or take a position against it — we are a software and infrastructure vendor and not a counterparty to anything.
7open items on this page
- Which oneZero components and versions we have run in production.
- Whether shadow running is available for every provider or only some.
- Response and resolution targets per severity — these are figures and none is verified yet, so no number appears on the page (see /trust/execution for the rule).
- Uptime commitment, and the measurement window it is calculated over.
- Pricing: setup and monthly figures per configuration.
- A dedicated infrastructure enquiry route. The demo form is for the platform and would be the wrong intent here, so the CTA currently points at the support plans page.
- Confirmation of our current data-centre footprint, so the colocation options can be listed by name rather than described.
Next step.
The support arrangement behind this service is the thing worth reading before you talk to anyone, including us.
A dedicated enquiry form for infrastructure work is outstanding — it is on the list above. The demo form is for the platform and would be the wrong thing to send you to.