ONIX documentation¶
ONIX is a multi-venue market-data, research and trading platform. It combines a NautilusTrader-backed backend that owns market data, catalogs, aggregation, backtesting and execution with a web product for charting, screening and strategy work, plus native clients and Model Context Protocol surfaces.
This site documents that system as it actually exists at a set of recorded source commits. It is not a product brochure and it is not a roadmap. Where something is built and confirmed, this site says so and names the evidence. Where something is private, test-stage, recorded but unobserved, or merely a declared target, it says that instead.
Read this before anything else
ONIX is a private, pre-general-availability system. Nothing on this site is an offer of a service, a guarantee of availability, or investment advice.
- This documentation does not claim live real-money order execution. Execution capability is described strictly within the boundary the execution runtime page sets out.
- Multi-user identity and access control are not documented as complete. See support and scope.
- The native clients are private and test-stage, not publicly listed. See native clients.
Start here¶
Getting started¶
What ONIX is made of, how the pieces fit together, and the shortest path to understanding a given surface.
Documentation and status model¶
The status vocabulary every page uses, what each token promises, and how evidence is recorded and checked.
System boundaries¶
Which component owns which fact, where the seams are, and what deliberately does not exist.
Product surfaces¶
Charting and datafeed, dashboard and workspaces, screener, strategy and backtesting workflows, and the gateway that serves them.
Backend and platform¶
Data plane, catalog and aggregation, runtime envelope, venues, trading subsystems, the screener engine and the schema surface.
Native clients¶
The macOS client and its local MCP host, the iOS client, and the honest support boundary for both.
MCP surfaces¶
The two Model Context Protocol surfaces in ONIX, how they differ in trust and scope, and what each will refuse to do.
Reference¶
Glossary, capability register, health and status contract, and the venue capability matrix.
How to read a page on this site¶
Every published page opens with a status strip and closes with an evidence block. Both are generated from the page's own metadata during the build, so they cannot drift away from what the page claims.
The strip tells you four things at a glance:
| Element | Meaning |
|---|---|
| Status badge | How much weight the page's claims carry. Defined in full on the status model page. |
| Owner | Which part of the system is accountable for the content. |
| Last verified | The date the claims were last checked against source. |
| Pins | The exact commits the page was written against. |
The evidence block at the foot of each page lists the specific files those claims were read from. A reader with access to the source repositories can check any claim directly. A reader without that access can at least see precisely what the claim rests on, and how old it is.
What this documentation deliberately does not do¶
- It does not describe an abandoned TypeScript trading and data engine. That runtime is retired; NautilusTrader through the ONIX backend is authoritative for market data, catalogs, aggregation, backtesting and execution.
- It does not reproduce upstream NautilusTrader documentation. Upstream behaviour is linked, not copied. See the NautilusTrader boundary.
- It does not publish operational runbooks, alerting configuration, incident history, private topology, or security and administration internals. Those are recorded and deliberately withheld; see documentation model.
- It does not present development intent as deployed reality. Where the only
evidence is a tracked production record that was never observed on a live host,
the page is marked
Production recordand says so.
Provenance¶
The source commits this entire site was written against, along with the documentation build's own identity, are listed on versions and source pins.
Evidence and source pins for this page
Verified. Current behaviour, confirmed in source at the pinned commit.
Verified on against the following immutable sources:
frontend@99f49dae:scripts/engine-pin.mjsbackend@efa38e04:feature-state/rc3-data-plane-frozen-current-production.yamlbackend@efa38e04:docs/handoff/contract-manifest.jsonmacos@984bdf6c:MCPSecurityTests
Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.