Feature And Provider Status
This page describes support boundaries for trading, connection, and market-data features. Use the documentation version map to distinguish the public download version, signed release records, and reviewed 1.1.27 source. Match version-specific instructions to Help > About; a source feature does not automatically become a supported public workflow.
Installer and provider certification
The project's Signed release record is not an independent certification by this documentation audit. Verify the downloaded installer's Windows signature and the version in Help > About. Current also does not mean that every provider, region, entitlement, account type, or live workflow has completed certification. Validate the exact provider and account in a non-live environment before risking capital.
Status Definitions
| Status | Meaning |
|---|---|
| Current | Implemented and available in the current build, subject to provider permissions and the limitations documented here. |
| Preview | Available for evaluation, but not approved as a production live-trading dependency. |
| Beta | Functional but still undergoing safety, compatibility, or operational validation. |
| Internal | Present in development code but not part of the supported public release surface. |
| Unavailable | A visible name or placeholder may exist, but the integration is not usable. |
Provider Status
| Provider surface | Status | Market data | Local simulation | Provider account and routing |
|---|---|---|---|---|
| KuCoin | Current; live certification still required | Historical and live data for enabled Spot and Futures markets; market depth | Yes | Account access and live routing require valid permissions. Manual API-key and linked-account capabilities can differ. Release-enabled Local Agent routing requires a separate default-off setting and matching Spot or Futures account scope. |
| Rithmic | Current; live certification still required | Historical data, live updates, and market depth | Yes | Broker accounts and order routing are available with valid Rithmic credentials, the exact System/Gateway specified by the broker or prop firm, and the required entitlements. HyperionX uses a direct session; it does not require a Rithmic plug-in. See Connect Rithmic. |
| Hyperliquid data | Current | Historical data, live updates, and market depth | Yes | Market-data use does not by itself enable live wallet trading. |
| Hyperliquid wallet trading | Preview; not approved for general live use | Uses the Hyperliquid connection | N/A | Requires wallet approval, a locally generated agent key, and builder-fee approval. Local Agent live routing adds separate capability, setting, entitlement, active-context, and provider checks when the installed release exposes it. See Hyperliquid Wallet and Local Agent Live Trading API. |
| Binance | Unavailable / Coming Soon | Clean setup is locked in the supported connection picker. Legacy preconfigured state is not release-certified. | No supported clean-setup path | No supported public account or routing path. |
| Jupiter Exchange | Unavailable | No supported public integration | No | The current surface is a placeholder and cannot be used. |
| o1.exchange | Unavailable | No supported public integration | No | The current surface is a placeholder and cannot be used. |
| Tradovate | Unavailable | No supported public integration | No | The current surface is a placeholder and cannot be used. |
DxFeed, Interactive Brokers, and CQG adapters are not enabled in the supported connection picker. They are internal or legacy development areas and are not public-release providers.
Trading And Market-Data Features
| Feature | Status | Release note |
|---|---|---|
| Chart Trader | Current | Buttons submit directly to the selected account after local validation. There is no general manual-order confirmation dialog or platform-wide manual max-order/daily-loss guard. |
| Accounts, orders, and positions | Current | Provider behavior varies by account type, order type, and provider capability. |
| MegaDOM | Current | MegaDOM is the public DOM product name. It can route orders to the selected connected account. |
| Level II window | Preview | When provider depth is unavailable, the current window can display generated fallback rows. Do not use those rows for trading decisions. |
| Chart-linked Time and Sales | Current | Receives prints from the active chart data stream. |
| Standalone or restored Time and Sales | Preview | Can open with seeded sample rows when it is not linked to an active chart. Do not treat those rows as live prints. |
Hyperion Sim / LocalPaper | Current, simplified | Uses a local full-fill simulator. It does not model order-book liquidity, partial order fills, configurable slippage, buying-power rejection, or liquidation. |
| Playback | Current | Replays historical data without changing the selected account. Select and verify LocalPaper for replay trading; do not rely on build-specific external-account guards to correct an unintended account selection. |
| Trade Copier | Beta | Available for all supported account types at the user's own risk. Begin with LocalPaper; live and prop-firm use can create real orders and losses, and some advanced controls are not effective enforcement boundaries in the current build. See Trade Copier. |
| Connection recovery | Current, provider-dependent | Rithmic requires manual retry after failed login or unexpected disconnect from the recorded 1.1.19 release onward. Other providers can have different retry behavior. Provider orders can remain live while the desktop is disconnected. See Connection Recovery. |
Platform Feature Status
| Platform area | Status | Public release boundary |
|---|---|---|
| Desktop charts, drawings, Data Box, tabs, and layouts | Current | Verify each chart's provider, instrument, and data provenance. See Charts And Drawings. |
| Workspaces | Current | Saves supported window/layout configuration, not live orders, positions, provider sessions, in-memory bars, AI chat, or executing strategy objects. |
Code Lab generated HyperionX.Custom model | Current | Established compatibility path for indicators and strategies. V2 starts in 1.1.12; later corrections and unreleased migration notes are versioned in the V2 Script API. Custom code runs inside the desktop process. |
| Add-ons | Current, narrow | Load/unload and dispatcher context are documented; desktop internals are not a public API. |
| Custom bars and research extension modules | Preview | Product-owned runtime/default work is recorded in signed release 1.1.11 and later. Verify first-launch discovery in the exact installed build; do not import untrusted modules to replace anything missing. |
HyperionX.SDK runtime adapter | Preview | Runtime bridges are recorded in signed release 1.1.11, but the adapter is not a stable general public contract. Use only documented HyperionX.Custom and versioned V2 surfaces for release-compatible extensions. |
| Validator backtesting | Preview | Product-owned defaults and historical live-account isolation are recorded in signed release 1.1.11 and later. Verify the installer signature, version, first-launch discovery, and a small known test before relying on results. |
| Optimizer | Preview | Product-owned optimizer, fitness, commission, and money-management defaults are recorded in signed release 1.1.11 and later. Verify the exact installed build and module discovery before a full run. |
| Research Lab | Preview | Signed release records include the Python Research Runtime. Verify module discovery in the installed package; data retention, reproducibility, and cloud-upload boundaries still apply. |
| Performance Database | Current, limited | Stores selected results but not every input required to reproduce a run. |
| Rion chart chat | Current | Provider-dependent cloud/local processing; AI output requires verification. |
| Structured Rion desktop actions | Preview; simulation-first | Hyperion Sim remains the safest first-use path. Installed builds with the required release capability can expose guarded Hyperliquid and KuCoin actions; availability is capability-discovered and enforcement varies by surface. |
| Rion Autopilot and Strategy Discovery | Preview; legacy route limitations | Legacy Discovery routes can upload a research CSV and metadata through their default ML stage without a dedicated consent prompt. The reviewed 1.1.27 default Cloud conversation does not expose those research tools. Check the selected route and the workflow and privacy guidance before use. |
| Agent Builder | Preview; entitlement-gated | Some context/action filters are enforced; numeric risk and allowlist fields are advisory in the reviewed build. |
| Local Desktop HTTP API | Preview | Loopback and token protected, with no stable schema contract. Hyperliquid and KuCoin live actions are release-gated, default-off, and capability-discovered; do not infer live availability from the API route alone. |
| Marketplace publishing/install/following | Internal / public availability not established | Reviewed 1.1.27 source has publisher controls, but a supported public package, publisher, follower, and routing contract must be verified for the installed release. See Marketplace. |
| Application language packs | Current, partial | Nine language choices exist; some text remains English. The recorded 1.1.20 release adds MDY/DMY date ordering under General Preferences, with a restart prompt when changed. |
| Updates | Version-dependent | Older builds can open a download page. Reviewed 1.1.27 source downloads and verifies an installer and blocks startup below the policy's minimum supported version. See Install And Update. |
Developer compatibility details are centralized in API Status And Compatibility and Platform API Contract. AI and automation boundaries are documented in AI Data And Privacy, Rion Autopilot And Strategy Discovery, Agent Builder, and Local Desktop API.
Before Using A Live Account
- Confirm the provider and feature are listed as Current for the required capability.
- Confirm the selected account is the intended Broker, Server Paper, or
LocalPaperaccount. - Verify order types, change/cancel behavior, and bracket behavior for that provider.
- Complete provider-specific certification with the exact credentials, environment, and entitlement set.
- Test reconnect and unknown-order-outcome recovery.
- Start with controlled size only after simulation and non-live validation.
Related guidance: