Support and scope¶
This page exists so that no reader has to infer a limit from silence.
What ONIX is¶
A private, multi-venue market-data, research and trading platform, built on NautilusTrader, in active development and not generally available. There is no public sign-up, no public API, and no publicly listed client application.
What this documentation does not claim¶
These are commitments, not disclaimers. The publication-safety scan enforces them mechanically, and a build that violates one does not ship.
Real-money execution¶
This documentation does not claim live real-money order execution.
The backend has an execution subsystem, and it is documented — but strictly within the boundary the execution runtime page sets out, which distinguishes backtesting, sandbox operation on live data, and anything beyond. Where the evidence at the pinned commits does not establish a capability, the page says so rather than implying it.
If you are trying to determine whether ONIX can place a real order with real money on your behalf today, this documentation is not the answer, and no page here should be read as one.
Identity and access control¶
Multi-user identity and access control are not documented as complete.
Authentication surfaces exist. An authorization model exists. Neither is published, because the security and administration material is quarantined pending both implementation review and disclosure review — see the documentation model.
The practical consequence: do not assume that any documented capability is scoped, isolated or permissioned in the way a multi-tenant system would be. That question is open, and it is recorded as open.
Availability¶
Nothing here is an availability commitment. There is no SLA, no uptime target, no support tier and no incident-response promise attached to this documentation. Health surfaces describe an instant, not a guarantee; see health and status contract.
Deployment¶
Statements about what is deployed rest on a tracked record in the repository, not
on observation of a running host. Pages that depend on it carry the Production
record badge. See runtime and deployment.
Client availability¶
| Client | Availability | Documented at |
|---|---|---|
| Web product | Private | Product |
| macOS client | Private, test-stage distribution | macOS client |
| iOS client | Private, test-stage distribution | iOS client |
Neither native client is publicly listed. Both are pre-general-availability, and their interfaces are expected to change. The full boundary is at native support boundary.
Agent and MCP scope¶
ONIX exposes Model Context Protocol surfaces. They are bounded: operations are enumerated, mutating operations are distinguished from read-only ones, and anything that can change state defaults to refusal.
An agent connected to an ONIX MCP surface is not thereby authorised to trade, deploy, or reach outside the enumerated operation set. See MCP safety and scope.
Reporting a problem with this documentation¶
A wrong page is worse than a missing one, so corrections are welcome.
If you have source access, the correction path is in
how to contribute. A correction needs evidence: a
repository@commit:path anchor a reviewer can open. Downgrading an overstated
claim to Unverified is a legitimate and valuable contribution.
If you do not have source access, the most useful report names the page, the sentence, and what you observed that contradicts it. The page's status strip carries the date and pins the claim was made against, which is usually the fastest way to establish whether a claim is wrong or merely stale.
Not investment advice¶
Nothing on this site is investment, financial, legal or tax advice, an offer, or a solicitation. Documentation of a trading system describes machinery, not strategy, and no page here should be read as a recommendation to trade anything.
Evidence and source pins for this page
Private / test stage. Exists, but is private, internal or test-stage only. Not generally available.
Verified on against the following immutable sources:
backend@efa38e04:feature-state/rc3-data-plane-frozen-current-production.yamlfrontend@99f49dae:scripts/engine-pin.mjs
Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.